954,560 Members — Technology Publication meets Social Media
Username:
Password:
Lost login information?
Have something to say? Contribute New Article Reply to this Article

MSSQL Database Partitioning

Hi,

My project modules are organized in such a way that I have to maintain following Database structure.

I've 5 schemas, each containing 20 to 50 tables. Each schema is accosiated with one module of the project.

All the tables that are used within more than one modules are kept in "COMMON" schema. Each module takes 2 to 5 months to finish.

So when first module is finished we are opening it for use, and continuing with the second one and so on. Meanwhile real data is being inserted into the finished module's schema. Also table definitions of the finished module's schema might change slightly depending on the bug fixes and suggestions.

I want to be able to backup/restore, synchronize database schema by schema (I think it's called vertical partitioning?)

In DB2 there was a way to put tables to different tablespaces, and backup/restore tablespaces seperately.

I'm looking for similar or better solutions for the problem in MSSQL. So Problems:

1. How to apply table definition changes to the table that's containing real data.
2. Being able to update/change/restore/backup/syncronize database schema by schema

Any kind of advices are greatly welcome.

I hope I could explain my problem.

Thanks.

NeoKyrgyz
Light Poster
38 posts since Jan 2009
Reputation Points: 48
Solved Threads: 1
 

This article has been dead for over three months

Post: Markdown Syntax: Formatting Help
You
View similar articles that have also been tagged: