Virtualization is one of the most rapidly growing technologies in IT today. Driving this growth is virtualization’s ability to decouple the server from the underlying hardware, letting you run multiple virtual machines (VMs) on a single hardware platform and easily move the VMs (along with their underlying guest OS and servers) to different hardware platforms. Many organizations have adopted this technology as a server consolidation method. But virtualization isn’t the only way to consolidate servers. Every release since SQL Server 2000 can support multiple SQL Server instances on the same system—unlike other Microsoft server products.

Multiple server instance support in SQL Server essentially lets you run multiple occurrences of SQL Server’s database engine on the same server. SQL Server 2005 Enterprise Edition supports up to 50 server instances. ISPs and other hosting scenarios often use multiple SQL server instances so that multiple clients can each have control of their own SQL Server database server without a dedicated hardware platform. So how do virtualization and multiple SQL server instances compare?

The first, and in many cases the most important, factor to consider is performance. Because of their nature, virtualized servers don’t provide the same level of performance as a physical machine because the virtual environment creates additional overhead that takes away from performance. Most estimates put VM overhead at about 10-15 percent. In a server consolidation environment, the impact will be even greater because of the workloads supported by the other VMs. In contrast, server instances run on the physical hardware and, aside from whatever workload might be generated by the queries running on the server instance, there is no additional overhead.

Virtualization and server instances are similar in their administrative aspects, but running multiple SQL server instances has a couple of advantages. Because there’s only one installation of the OS and the server software, server instances require less patching. With virtualization, each VM has its own guest OS and server products, which must be managed and patched. In both solutions, hands-on server management tasks are performed using Enterprise Manager or SQL Server Management Studio.

In terms of deployment and recovery, virtualization has an edge on its competition. With virtualization, you can build base images that can be deployed to a new server in a matter of minutes. Then, a VM image can be backed up or replicated to a remote site and, in the event of a failure, could be brought in-line in minutes or even seconds.

Another factor to consider is licensing. Multiple SQL server instances don’t require any additional SQL Server licenses. For virtualization, each SQL Server system that’s running in a guest VM must be licensed—unless you’re running SQL Server 2005 Enterprise Edition, which provides unlimited VM usage.

The bottom line is that both methods can be effective solutions for server consolidation. To help you decide which solution is right for you, see the resources listed in this month’s Your Savvy Assistant. But remember, just because virtualization is today’s hot technology doesn’t mean that it’s the only game in town.

End of Article




Post Your Comments Here

You must be a registered user or online subscriber to comment on this article. Please log on before posting a comment. Are you a new visitor? Register now

Reader Comments

SQL Server Licensing is socket based. So if you have 2 physical CPU (with each 4 cores), you pay 2 licenses regardless on how many VM/instances you have.

gilou28

Article Rating 3 out of 5

Useful - Great to be able to get these quick, summary assessments.

bhodgman

Article Rating 4 out of 5

This could have had comparisons between the various vendors of VM software.

dwknapp

Article Rating 3 out of 5

On a VM, SQL Server has access to one processor only so parallel query execution no longer exists. That isn'r SQL Server for large databases.

katesl@earthlink.net

Article Rating 4 out of 5

Very concise article!

vavramenko

Article Rating 4 out of 5

This was very timely as we build out a QA environment. QA instances of our various production servers is attractive compared to the VM route we are going. However I'm wondering if there are any limitations or differences in how linked servers behave between instances.

PNovelli

Article Rating 5 out of 5

N/A

rrsardinha

Article Rating 3 out of 5

Good

ludatrend

Article Rating 5 out of 5

Hi, My name is Noravia Rodriguez, Database Manager at City Of Miami. I read your article and it is pretti concise and important to me. This note below specifically is important:

> Another factor to consider is licensing. Multiple SQL server instances don’t require any additional SQL Server licenses. For virtualization, each SQL Server system that’s running in a guest VM must be licensed—unless you’re running SQL Server 2005 Enterprise Edition, which provides unlimited VM usage

My question: 1.- If I am using VMWare, running Windows Server 2003 and I have one Virtual Machine that runs SQL Server 2005 Enterprise Edition, then using this license I cna have others Virtual Machines in the same VMWare Server running SQL Server 2005 Enterprise Edition and are covered under the same license? 2.- License needs to be purchase the by processor? I appreciate your feedback. Thank you in advanced

nrodriguez64

Article Rating 5 out of 5

Thanks for all the feedback. We are planning a product comparison of the virtual server software for mid-summer. Product specifics will be covered in this comparison. Diana May

DianaMay

Article Rating 4 out of 5

 
 

ADS BY GOOGLE