Consolidating sql databases
some renaming of tables, store procedures names too.Consolidating Databases Using Virtualization Planning Guide SQL Server Technical Paper Technical Writer: Paul Jenkins Technical Reviewers: Mark Mortimore, Nathan Johnson Published: July 2011 Applies to: SQL Server 2008 R2 and SQL Server 2008 Summary: The purpose of this guide is to provide a description of the technologies and best practices utilized to design a database consolidation solution; guidance will be appropriately defined throughout to prescribe configurations and considerations to implement for best results.Another approach for reducing DB links and materialized views is to consolidate the schemas into one database, but I want to make sure I'm not forgetting any critical disadvantages to that approach.
You either need a couple of instances on the same machine or a couple of VMs, each supporting a different version of SQL Server.
In an organization that has two applications each with its own Oracle database instance, what are the disadvantages of consolidating the two databases into one database with two schemas?
Backups and replicating the database are bigger and slower, probably. Some background: The two databases are the "gold source" for their respective data.
Each is critical to the operation of the organization and each is actually used by several appliations, tools, and reports (but each database is principally "owned" by one application).
The need to join data across the databases, to relate entities in one to entities in the other, comes up frequently.
For this reason there are DB links connecting the two and some cross-database materialized views to help with performance.