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 |
|
dussan
Starting Member
1 Post |
 Posted - 2011-07-11 : 06:19:12
|
| I'm migrating our SQL server from version 2000 to 2008 R2 Standard Edition. On 2000 we have 10 databases – each department have his “own” database, common data are replicated from one databases to other. Databases are not big – from 5 to 15 Gb, they are oltp databases.Question – what do you suggest?1. To “merge” all databases into one single “big” database. We have tables & views which have same name in different databases but contains different data (like Invoices). So we must rename them or use different schema and upgrade our programs.2. Use one database for common data and use views across different databases. No foreign keys, if I'm not wrong.3. Use, like now, more databases and replicate common data. Replication is “time consuming” and we must maintain all databases (backup...).What about performance, maintenance...?Any suggestions will be appreciate.With regards,Dussan |
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2011-07-12 : 14:02:17
|
| If you need long term manageability ease, I would go with 1. As you already noted, it requires database code rewrite and/or application code re-write, data migration etc. which can be a considerable effort and management may or may not likely buy off the "ease of manageability" opinion as easily.. you can start with option 2 as a short term mitigation, so you have one copy of common data and not worry about replication and keeping the data in sync or worry about different apps not reading right data.. just in case you dont update the data in all databases.Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
 |
|
|
|
|
|
One database or more databases