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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-02-23 : 09:03:13
|
| Steve writes "Here's one for you all. I'm working with a group that has no experience with SQL Server DTS or Integration Services and they consider the use of such tools to be risky and want to continue using .sql files (350+) and .vbs files executed by a vb6 application to migrate older versions of the database to newer versions. The new DTS structure uses a metatable contained in the destination database which determines which tables are to be migrated (customer or system data currently, designed to be flexible). It also builds replication based on this metatable. This metatable is maintained by the developers/business owners (uses bit fields for system and repl) and business rules are in place to ensure no columns are removed and new columns are added to the end of the tables (with defaults) for new versions of product.I have tested this vs. an in-place migration on multi GB databases with much success (5-7 mins. on average vs. 50 mins. for in-place.) since it is transferring old data into a new structure de-fragmentation occurs and the databases on average are reduced in size by about 45%. I get the feeling that they feel threatened by what they don't know. The numbers, in my eyes, back themselves up and it's a no-brainer... What am I missing that could convince them that this is the best way. BTW, also migrated the DTS2000 package to IS 2005 and it worked fine there as well.Steve" |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2006-02-23 : 10:07:07
|
Developers like this always make me chuckle..The easiest way to convince them is to take 2 copies of the database, run your DTS and then run their solution, then do a DB comparison to prove that they are the same (except for the file sizes of course..  ).. Do row counts, select random records from each and just generally make as big a fuss as possible when they turn out to be exactly the same.. Draw up a document with your results and then present it to them and see what they say..Or you could always tell them that you own the databases and you are no longer letting their solution anywhere near it.. |
 |
|
|
|
|
|
DTS