Consolidating sql databases
Larry Ellison mentioned the Intel chips during his presentation at Oracle World 2003 in San Francisco when he noted, : If you want the world's fastest processors, you are going to be forced to pay less." There are naysayers who argue that it is not a good idea to throw everything into a single server because it introduces a single point of failure.DB Pro’s in-depth DBA knowledge has helped us extract more capacity from our existing SQL Server infrastructure.With IMS or IDMS on a mainframe, I would only need to perform an upgrade once, and I could easily gen-in the upgrades to dozens of "instances," all at my leisure.Back them there was "the" DBA, and few shops needed more than one DBA to manage all of the databases.
With these operations we achieved significant improvement in performance, thus we are very satisfied.
This is consistent in what we see in the field and marketplace; cost efficiency and new features enabling better performance, availability and management are driving our clients in the same direction.
SQL Server consolidation involves analyzing the servers in your enterprise and grouping databases onto a smaller number of servers without compromising the performance of any applications using SQL resources.
These come under various guises: the “As A Service” models: Database-as-a-Service (Daa S), Infrastructure-as-a-Service (Iaa S), Platform-as-a-Service (Paa S); the On-Demand models (e.g.
Amazon’s Relational Database Service); and the ubiquitous cloud offerings (e.g. (My first job working with On Demand services was in 2003, so I still can’t use the term “cloud” without it coming out sounding as if I’m being sarcastic…
You can see this if you read the IT press, or if you listen to the relentless procession of people queueing up to talk about the “cloud”.