Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
 Posted - 2012-01-06 : 08:30:22
|
| I have about a dozen dts packages that I am about to migrate to SQL Server 2008 SSIS packages. I'm not very familiar with SSIS yet and this will be the first time I have used the wizard to migrate dts packages.My question is, Are there any "gotcha's" that I should be aware of?Most of the packages involve simple connections to SQL Server or a file of some type with the odd ODBC connection thrown in for good measure. There is very little script, only one of the packages has any at all, the rest are largely SQL statements. thankssteve-----------What color do you want that database? |
|
|
Kristen
Test
22859 Posts |
Posted - 2012-01-06 : 08:33:13
|
| Unrelated to SSIS, about which I know nothing, but if you are generally in the process of migrating from SQL 2000 or SQL 2005 then this will help as a check-list:http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=138230 |
 |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2012-01-06 : 09:35:04
|
| It will probably just embed the package in an ssis package - won't do much in the way of migration.The only way to tell if you have issue is by testing - more likely to get problems from the account that it is set up to use than anything else.You should migrate to ssis at some point which sounds like it will be quite easy as it looks like you are just doing simple data movements (a good thing - keep control out of packages). Could even write something to generate the packages so that you can add all the logging typoe stuff in one place.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
mandm
Posting Yak Master
120 Posts |
Posted - 2012-01-06 : 16:54:17
|
| If you do end up having to work on any of them you'll need to get the package into Visual Studio/BIDS because the migration wizard won't do that for you. The best way I found was to export the package to disk then open a new Visual Studio/BIDS integration services project. Copy the exported dtsx package into the project and add it as an existing package. Then you can debug the package and fix issues. |
|
|
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
Posted - 2012-01-09 : 05:27:10
|
| Thanks all, much appreciated, thankfully I have VS on my machine so no major issues there (apart from it being very slow to open these packages but that is most likely just my machine).I did have to install the SQL Server 2000 DTS designer components, though in my case as there are so few of them and they are pretty simple I'm considering re-writing over the next few months when I have a spare moment.steve-----------What color do you want that database? |
|
|
|
|
|
|
General Question