SQL Server architecture - they want to move my database to new instance...Why?
- by O'MALLEY
Our current production database environment contains about 10 similarily managed databases. Our agency has just purchased and is installing new blade chasses and wants to move my database to a new instance (leaving the other 9 on another). This decision is being driven by one of our IT staff, not a DBA. I am a project manager, not a DBA but I know enough to not necesarrily have a good feeling about this decision and I am urging our IT department to make a sound decision based on what is best for the database. Our IT department has stated that it is not good to have all our eggs in one basket, and has also stated that my database contains "regulatory data" so it should be on its own instance.
A couple of truths:
- None of the databases on the current instance are OLTP databases nor are any of them data warehouses
- My database currently has joins/views to a couple of the other databases in the production environment
So my questions are as follows:
Am I wrong to disregard a statement about eggs in baskets? (hello, this is why we have maintenance plans/disaster recovery plans). I'll mention that other databases also have regulatory data too.
What types of questions do I need to ask to determine if this is a sound decicion? (A DBA friend mentioned that if the service level agreement of said database does not radically differ from the others then why do they want to do this?)
I have done some research on linked servers. What arguments should I bring forth about the fact that I have views setup that rely on data from other DBs currently?
