Script Task/Component and Template Information

by Allan Mitchell 8 Dec 2009 06:46
The Script Task and Script component are often used by people developing SSIS packages because they are easy to use and now because SSIS could be perceived to be more developer friendly they are very powerful. That being said we should no be using them everywhere.  There are generally Tasks/Components already provided that will do the job it may be that we have to rethink the way we want to draw our package. I had cause last week to break out the script component in SQL Server 2008 SP1 and found that it was broken.  I don’t know when it broke as I do not use them all that often.... [More]

Building a Successful ETL Project

by Allan Mitchell 28 Oct 2008 09:00
When we are building ETL projects we need to do some planning up front to make sure we have all the things we need to make it a success. Here are some of the things we consider when embarking on an ETL Project. There are two lists. The first is around an ETL Project in general and the second is around things we think about specifically for SSIS. Review target data model Identify source systems (Owners, RDBMS types, Permissions) Analyze and profile source systems (usge patterns, Windows of opportunity) Document source data defects and anomalies (known issues, data profiling) ... [More]

Create MSDB Folders Through Code

by Darren Green 28 Oct 2008 08:58
You can create package folders through SSMS, but you may also wish to do this as part of a deployment process or installation. In this case you will want programmatic method for managing folders, so how can this be done? The short answer is, go and look at the table msdb.dbo. sysdtspackagefolders90. This where folder information is stored, using a simple parent and child hierarchy format. To add new folder directly we just insert into the table - INSERT INTO dbo.sysdtspackagefolders90 ( folderid ,parentfolderid ,foldername) VALUES ( NEWID() ... [More]

Using Parent Package Variables in Package Configurations

by Allan Mitchell 6 Dec 2004 14:00
Package configurations are now the prescribed way of being able to set values within your package from an outside source. One of the options for the source is Parent Package Variable. The name is perhaps a little misleading so this article is meant to guide you through this slight confusion and into using them. It also helps to explain a key concept in SQL Server Integration Services Setting Up Your Packages This example is very simple. We have two packages. One is called Caller and the other is named Called. In the Caller package we have an Execute Package task which calls the other packag... [More]

Easy Package Configuration

by Guest 30 Nov 2004 14:00
(By Jamie Thomson) One of the age old problems in DTS is moving packages between your development, test and production environments. Typically a series of manual edits needs to be done to all the packages to make sure that all the connection objects are pointing to the correct physical servers. This is time consuming and gives rise to the possibility of human error, particularly if the solution incorporates many DTS packages. Many companies have provided their own custom solutions for managing this problem but these are still workarounds for a problem that was inherent in DTS. Happily, Inte... [More]


Comment RSS