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 |
|
kakikupart
Starting Member
11 Posts |
 Posted - 2009-05-25 : 20:49:48
|
1. I have a system which user tables was created in master.mdf in SQL server 2000.My understanding this is not good practice to create any user object in Master DB because it contains the system tables.2. My system will be upgraded soon involving the database but using same SQL engine.However the new database schema is different with current databases3. I have plan to separate the user data into its own Db and will named as a TOOLS.I plan to use DTS to migrate data between old and new database which is quite similar but having several differences in field mapping.Could you guys suggest a better way of doing this..My plan steps..a) Install new instances of db under same server..b) Create DTS to define data transformation c) Run DTS to migrate datad) Backup new Data e) Fresh - Installation of new SQL Serverf) Restore the backup dataThe new system need to be deployed to 100 over location.. I might need same template for all location.hope someone can give me advice ...... |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2009-05-26 : 01:02:36
|
| I would create a new database on the old system and copy the tables into it.Would also get the old system running on this database rather than master.note - one of the reasons for not holding data in master is that if you have to restore it's a much bigger issue to restore master rather than a user database.For the migration I would restore the databases onto the new system then copy the tables using stored procedures - any conversion could be done using the SPs easily. In this way you don't need the old and new system to be available at the same time and can test/rerun without affecting the old system or even connecting to it.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
master.mdf (SQL 2000 Server)