July 20, 2011 at 8:47 am
Because of the limits of shared hosting, I had to logically divide my growing MS SQL Server 2008 database into two databases. This has worked fine on shared hosting. However, I've now outgrown shared hosting and am moving to a VPS provider. I no longer have database size limitations. Should I consolidate back to one database? I can think of good reasons to do that, but don't know if having two databases logically divided has its advantages (maybe performance?). Help!:w00t:
July 20, 2011 at 9:02 am
If you can consolidate the two databases into one that would be the way to go.
You may have some issues in doing so depending upon a number of variables.
How much code will need to be rewritten if you consolidate?
You have to examine the code, SP's, GUI, etc and make a determination of the work effort that be be needed as a result of the consolidation.
How large are the DB's? If you have a larger DB than poorly written code will become more of an issue.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply