Virtual Machines VM Tips

Our organization has decided to no longer use Windows Clustering and instead rely on the hardware redundancy inherent in a virtual environment. My problem is that I have numerous SQL Server clusters. How should I handle these clusters during the virtualization process?

Your last tip walked us through the planning stage and now I have a dozen or so virtual SQL Servers under by responsibility. As a DBA do I need to change the way I manage these servers? Is there anything I need to do differently? Check out this tip to learn about monitoring your virtual SQL Servers.

Your first tip provided a quick overview of VM terminology and your previous tip talked about why and when I should virtualize SQL server. We are now ready to begin the process of virtualizing SQL Server. What are some questions I should ask? Are there certain things I should know before hand to help with the transition? Check out this tip to get your questions answered.

Your previous tip helped define the VM environment and discussed some of the advantages and disadvantages of virtualization. What about virtualizing SQL Server? Is this always a good idea? What are some things I need to think about? Check out this tip to learn about the advantages and disadvantages of virtualizing SQL Server.

I hear the rumblings of DBA's facing the prospective of virtualizing their databases. Some have managed to stave off the inevitable while others have embraced it slowly one test or development database server at a time. I'm writing a series of tips as a guide from a DBA who has already been drowned in the virtual sea to DBAs who want to take the plunge. My team manages more than 365 virtual database servers in the healthcare field and my company has virtualized more than 3,000 servers. Still, I'm not writing from the perspective of someone who is an evangelist for virtualization, instead; I'm writing this because as a DBA you eventually won't have a choice. If your company has more than 4 people, you will virtualize your servers. It is bett

We have discussed different aspects of virtualization in previous tips and in this tip we look at additional reading and resources you can use to make the most of your virtualized SQL Server enviornment.

I'm a SQL DBA and I just attended a meeting with the storage and server teams. They told me that within the next month they will be converting all our SQL Servers to VM. They didn't even ask my opinion!? What should I do? In this tip I give some advice on how to handle the change.

Recently virtual server technologies have been getting a great deal of buzz in the industry. Is this a technology that I should have on my radar screen? What impacts does this technology have on SQL Server? What can virtual SQL Servers do for me as a DBA? I have been hearing a great deal of positive information, but is there any down side of implementing this technology for SQL Server? Where can I find more information?

I hear the rumblings of DBA's facing the prospective of virtualizing their databases. Some have managed to stave off the inevitable while others have embraced it slowly one test or development database server at a time. I'm writing a series of tips as a guide from a DBA who has already been drowned in the virtual sea to DBAs who want to take the plunge. My team manages more than 365 virtual database servers in the healthcare field and my company has virtualized more than 3,000 servers. Still, I'm not writing from the perspective of someone who is an evangelist for virtualization, instead; I'm writing this because as a DBA you eventually won't have a choice. If your company has more than 4 people, you will virtualize your servers. It is bett

Your previous tip helped define the VM environment and discussed some of the advantages and disadvantages of virtualization. What about virtualizing SQL Server? Is this always a good idea? What are some things I need to think about? Check out this tip to learn about the advantages and disadvantages of virtualizing SQL Server.

Your last tip walked us through the planning stage and now I have a dozen or so virtual SQL Servers under by responsibility. As a DBA do I need to change the way I manage these servers? Is there anything I need to do differently? Check out this tip to learn about monitoring your virtual SQL Servers.

We have discussed different aspects of virtualization in previous tips and in this tip we look at additional reading and resources you can use to make the most of your virtualized SQL Server enviornment.

Your first tip provided a quick overview of VM terminology and your previous tip talked about why and when I should virtualize SQL server. We are now ready to begin the process of virtualizing SQL Server. What are some questions I should ask? Are there certain things I should know before hand to help with the transition? Check out this tip to get your questions answered.

Our organization has decided to no longer use Windows Clustering and instead rely on the hardware redundancy inherent in a virtual environment. My problem is that I have numerous SQL Server clusters. How should I handle these clusters during the virtualization process?

I'm a SQL DBA and I just attended a meeting with the storage and server teams. They told me that within the next month they will be converting all our SQL Servers to VM. They didn't even ask my opinion!? What should I do? In this tip I give some advice on how to handle the change.

Recently virtual server technologies have been getting a great deal of buzz in the industry. Is this a technology that I should have on my radar screen? What impacts does this technology have on SQL Server? What can virtual SQL Servers do for me as a DBA? I have been hearing a great deal of positive information, but is there any down side of implementing this technology for SQL Server? Where can I find more information?

We have discussed different aspects of virtualization in previous tips and in this tip we look at additional reading and resources you can use to make the most of your virtualized SQL Server enviornment.

Your last tip walked us through the planning stage and now I have a dozen or so virtual SQL Servers under by responsibility. As a DBA do I need to change the way I manage these servers? Is there anything I need to do differently? Check out this tip to learn about monitoring your virtual SQL Servers.

Your first tip provided a quick overview of VM terminology and your previous tip talked about why and when I should virtualize SQL server. We are now ready to begin the process of virtualizing SQL Server. What are some questions I should ask? Are there certain things I should know before hand to help with the transition? Check out this tip to get your questions answered.

Your previous tip helped define the VM environment and discussed some of the advantages and disadvantages of virtualization. What about virtualizing SQL Server? Is this always a good idea? What are some things I need to think about? Check out this tip to learn about the advantages and disadvantages of virtualizing SQL Server.

I hear the rumblings of DBA's facing the prospective of virtualizing their databases. Some have managed to stave off the inevitable while others have embraced it slowly one test or development database server at a time. I'm writing a series of tips as a guide from a DBA who has already been drowned in the virtual sea to DBAs who want to take the plunge. My team manages more than 365 virtual database servers in the healthcare field and my company has virtualized more than 3,000 servers. Still, I'm not writing from the perspective of someone who is an evangelist for virtualization, instead; I'm writing this because as a DBA you eventually won't have a choice. If your company has more than 4 people, you will virtualize your servers. It is bett

Our organization has decided to no longer use Windows Clustering and instead rely on the hardware redundancy inherent in a virtual environment. My problem is that I have numerous SQL Server clusters. How should I handle these clusters during the virtualization process?

I'm a SQL DBA and I just attended a meeting with the storage and server teams. They told me that within the next month they will be converting all our SQL Servers to VM. They didn't even ask my opinion!? What should I do? In this tip I give some advice on how to handle the change.

Recently virtual server technologies have been getting a great deal of buzz in the industry. Is this a technology that I should have on my radar screen? What impacts does this technology have on SQL Server? What can virtual SQL Servers do for me as a DBA? I have been hearing a great deal of positive information, but is there any down side of implementing this technology for SQL Server? Where can I find more information?