Join Martin Guidry for an in-depth discussion in this video Planning a database server infrastructure, part of SQL Server 2012: Designing Database Solutions.
- When designing a Database Server Infrastructure there are several things to consider. Some of the most important include: Hardware. Virtualization. Whether or not you're going to virtualize your database servers. And also the licensing. With Server Hardware we usually group that into four characteristics: The CPU, or processor. How many are you going to have and what type? The memory. How much memory will be necessary for your servers? The disk.
How many disks? How much redundancy in the disk? And also the speed at which they can read and write data. And then also the network. How much bandwidth do we need coming in and going out? These are the four broad categories we use when planning the hardware for a database server. When planning the licensing of a database server, you need to think certainly about the licensing of SQL Server, which can be affected by decisions in the previous things we talked about.
Some licensing models of SQL Server are per processor, so the more processors you have the more money you're going to spend on licensing. So that decision about processor affects you in other ways. And then also virtualization. Virtual servers are licensed differently than physical servers, so your decision about virtualization will also affect your licensing cost. You should also consider that you're not just licensing SQL Server. At a minimum you also need to license an Operating System, which could be a significant cost.
And there may be other software you're going to run on the server also. Maybe a backup software or a security software. With all of those things the cost would typically increase the more servers you have. So you need to consider that in your cost model also.
- Planning the database infrastructure
- Designing databases vs. data warehouses
- Designing the physical database implementation
- Planning for partitioning
- Adding FileStream data
- Monitoring server health
- Managing SQL Server with PowerShell