It is really surprising how slowly companies adopt database consolidation granted the pressure IT management has in every possible direction.
We can speculate for hours why so, but what I will concentrate on, are the technical aspects of Exadata consolidation.
maintenance (index rebuilds, reorgs, stats update, backup schedules) etc depending on their criticality.
When your database size and usage increases, thats the time to move out the heavy used ones out of the instance on a different VM.
Is automated server/instance provisioning truly automated? When do I even start thinking about consolidation and/or virtualization?
These are some of the questions that are answered in this session, along with key best practices and caveats learned from dozens of consolidation projects that range from a dozen to over 4,000 SQL Server databases.
Titus Maccius Plautus, a roman poet and philosopher who lived from 254 BC to 184 BC, said: “Wisdom is not attained by years, but by ability”. Corporate IT departments would not surprise anyone if they support a couple of thousand databases.
To reduce the size of the Log Database, you can stop logging requests for sites in categories that, for example, present no security risk or legal liability to your organization.
Also, refer to my answer for To answer your question simply, if you have 1 VM with several instances, you have the possibility of resource contention between the instances on that VM.
In that scenario, I would consolidate databases onto a singular instance.
This session explores key considerations in a consolidation project and common oversights that derail the project.
It also reviews notes from the field on the various solutions available today, the strengths, weaknesses and what scenarios they are most appropriate for.