The few past weeks I have done a lot planning for the SQL hotel, and discovered lack of knowledge in this area. Everybody can put a DVD in the player, and start the setup program and select most of the default provided by installation wizard – it works. But when an enterprise SQL solution shall be established, you need to make a lot of choices and preparations before you can start the installation.
My current project is special because I have been doing stuff that normally is delegated to IT-department. My employer EVRY have been in a transition and the new concept “Future Proof” shall be the new delivery template for a secure, automatic, mobile and stable platform for our customers.
A customer delivery and will in most cases consist of a shared or dedicated development, test, QA and production environments. Each of these environments will contain a set of application. I’m part of the SQL Server team that plan, design and install the SQL server infrastructure used by Citrix, Lync, Exchange, CRM and DWH, in addition to other customer systems.
I will divide this subject into 4 different parts, hopefully completed in a few weeks 🙂
- Pre-install OS preparations (Part 2)
- Pre-install SQL preparations (Part 2)
- Actual SQL Server installation (Part 3)
- Post-install configurations (Part 3)
- Maintenance (Part 4)
The first thing you need to consider is to what licenses the customer currently have available. In most cases we need SQL Server 2012 “Enterprise” edition in QA and PROD environments, but there exist a “Business Intelligence” edition as well, while the TEST/DEV environments can use “Standard” edition.
When you install SQL Server, many people might install the full package with all feature enabled. This is not neccesary. Only install the components that is acually needed. This will reduce the resource usage and complexity of the installation, configuration and maintenance.