Dividing a SQL Database into Two

Hi -

I have a company with several divisions on a SQL 2000 database.  The database contains product information, sales, customers, etc. - basic e-commerce stuff.  Total size is a little under 1GB.  One of the divisions has been spun off, and I need to split the database so that the records pertaining to that division are replicated in a new database, and completely removed from the existing database.

What is the best way to accomplish this?


Who is Participating?
bwdowhanConnect With a Mentor Commented:
I would create a new database to represent the portion of the company that is being spun off. Take a backup of your production database and restore it to the newly created database. Remove the data from each database that doesn't belong and you should be set to move the new database to a server for the new company and your data will be clean. (This is assuming you can easily identify and remove the data from each database).
David ToddConnect With a Mentor Senior DBACommented:

Just as a check, I'd keep the original database, and create two new databases.

ie TotalCompany - original database
DivisionX - division that is being spun off
Others - remaining divisions.

That way TotalCompany is still there for reporting/reference/lookup/etc. Obviously want to set it to read-only. Your application may not like this. Some applications write to a loggedIn table ...

My 10 cents worth
okanaganAuthor Commented:
Thanks to both - I figured a backup was in the cards, but dtodd's idea is a good one.

Thanks again,

All Courses

From novice to tech pro — start learning today.