Microsoft guru Kirk Haselden gives tips for a general approach you can use to build SSIS packages that automatically adjust to their environment. When you keep packages in the dark about their environment, you can take them anywhere.
SQL Server 2005 Integration Services (SSIS) still includes familiar security functions such as password encryption, but the approach has changed dramatically. Take a look at the new security features and learn how and when to use them.
SQL Server 2005 Integration Services has new features that simplify package creation and editing. Walk through the package-modification process and see how you can effectively create new packages without reinventing the wheel.
Microsoft has completely rewritten SQL Server 2005 DTS, making the DTS Import/Export Wizard an even more effective tool for quickly building packages for moving data. Follow along with this example to learn about the wizard’s new features.
Microsoft has rewritten every aspect of Data Transformation Services (DTS) in SQL Server 2005, making it a true extraction, transformation, and loading (ETL) platform and improving performance. Take a whirlwind tour of some of the most important changes.
Digital Magazine Archives
Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.
There’s simply no way to overstate the importance of regular Transaction Log Backups. Not only do they help protect from disaster, but regular execution of T-Log backups on Full (and Bulk-Logged) Recovery databases helps keep thing “fit and trim”. Most of the time, setting up a Notification for when T-Log Backup Jobs fail is enough to let you know when something goes wrong....More
Code like this isn’t optimal:
IF EXISTS(SELECT * FROM sys.objects WHERE name = N'TableToDrop' AND type = 'U')
DROP TABLE TableToDrop;
Neither is this:
IF EXISTS(SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'TableToDrop')
DROP TABLE TableToDrop;
Yet, I see both of those used all of the time – over and over again. Even though it’s 2015. ...More
This blog post is a bit of a ‘repeat’ – since I already covered much of the rationale behind this post in Part 23 of my multi-part series on AlwaysOn Availability Groups and SQL Server Agent Jobs. But, I also figured that this is enough of an important topic to merit its own blog post....More