Get flash to fully experience Pearltrees
In the past I have advocated (and still do advocate) the use of a user variable in SSIS packages to store the path to a folder on the hard drive; I always use a variable called @[User::RootFolder] for this. Having this path available within a package variable enables you to dynamically set the location of files that your package may reference such as other packages, raw files, source files, log files etc.. Typically the value of this variable would get set by a configuration or the /SET option of dtexec however you do run the risk that someone might supply a path that does not have a backslash on the end of it and if you have expressions in your package that assume the presence of a backslash then you're going to get an error somewhere along the way.
This custom component for SSIS (SQL Server Integration Services 2008) helps you to enhance your error flows. It provides error description, column name and other useful information. You can connect many inputs to this component to create effective error flows quickly. (Created with Microsoft Visual C# 2008 Express Edition)
If you are trying to debug your SSIS package's Script Tasks by setting Breakpoints, and they don't seem to have any effect, check SSIS's progress panel. You may see the following Warning message: Warning: Cannot debug script tasks when running under the 64 bit version of the Integration Services runtime. Warning: Cannot debug script tasks when running under the 64 bit version of the Integration Services runtime. The solution is to change the Project/Debugging/Run64bitRunTime property to False :
In the current release of SQL Server Integration Services, the SQL statement in an Execute SQL task can contain a MERGE statement. This MERGE statement enables you to accomplish multiple INSERT, UPDATE, and DELETE operations in a single statement. To use the MERGE statement in a package, follow these steps: Create a Data Flow task that loads, transforms, and saves the source data to a temporary or staging table.