Most everyone I know have been in some kind of consolidation discussion, but as technical professionals many of us are not used to thinking about the business side of things. This session is aimed at the technical people involved in both deciding on consolidation and those tasked with it and can hopefully provide some ammunition to fire back at a non-technical decision to “consolidate” something.
Technically it’s a level 100, from a business perspective it’s more like level 150-200.
This session is 60 minutes.
Database consolidation was once described to me as a bit of a mix between the holy grail and a unicorn. Not that difficult in theory, but have a way of getting very messy in practice. Consider for example the meaning of “consolidate” – the number of potential issues stemming from not adequately deciding from the get-go what is to be done in the project. Classic issues include not knowing what we’re getting into, not having a goal(!), not adequately considering what systems (and how) will be affected, or not having the proper business processes to fall back on in order to decide on what’s actually important. In many cases a lot of issues stem from not having the same vocabulary and not considering the viewpoint of the “other” side.
I will go through these issues and more, and give technical tips as well as talk about business considerations like SLAs and how they can impact the choice of high availability.
At the end of this session you will have a good understanding of the challenges and solutions available for consolidating SQL Server primarily on-premise.
Why I Want to Present This Session:
As a consultant this is one of the more common scenarios I face. They usually go the same way:
- Client want to “consolidate” and “has done their homework”.
- I review said “homework” , point out a few hundred glaring holes and offer to go back to square one with a proper consolidation plan.
- Client decides that every system should have it’s own database.
The clients that had me in for a talk like this presentation tend to behave somewhat different:
- Client wants to consolidate in order to reach a specific goal and wants help with doing a feasibility study to finding likely issues.
- The the study is concluded and most often the client moves forward with a much deeper understading of the ramifications of a consolidation project.
- An actual consolidation project is initiated with high chance for success.
2017/04/30 – This session was voted into GroupBy June 2017, but Alexander had to withdraw due to scheduling issues.
Latest posts by Alexander Arvidsson (see all)
- Azure Machine Learning for the Absolute Beginner - August 28, 2019
- The Force Awakens – Azure SQL Server for the On-premises DBA - August 28, 2019
- Boring Is Stable, Stable Is Good – SQL Server Best Practices In Practice - August 28, 2019