Helpful information and examples on how to use SQL Server Integration Services.
The February CTP has been out almost a month now, but just incase you hadn't checked it out yet, I thought I'd post a heads up. The February CTP introduced Visual Studio 2008 (Orcas), replacing Visual Studio 2005 as our Business Intelligence Designer Studio (BIDS).[ side note - why is it I always misspell the word "Intelligence" ] Bringing in VS2008 also changed our scripting engine from VSTA 1.0 to VSTA 2.0, which broke compatibility with earlier Katmai CTPs.
From the February CTP Readme:
In the February CTP and earlier CTP releases of SQL Server 2008, the Script task and Script component used a version of Visual Studio for Applications (VSTA) that is no longer supported. Therefore, the scripts that the Script task and Script component contain are not supported in the following cases:
If the script is not supported, SQL Server 2008 Integration Services will display an error message when you open the package. To run the package, create a new Script task or Script component and create a new VSTA script.
When you migrate a SQL Server 2005 package to SQL Server 2008, the migration process automatically converts the scripts in the package to the current version of VSTA. (The package migration feature for SQL Server 2005 packages will be available in a future release of SQL Server 2008.)
SSIS packages created in 2005 have to go through an upgrade process to run in 2008. 2008 packages created