Session 1: How to Decide if your Database is a Good Candidate for Virtualization


Running Time: 56 minutes | You'll learn about the pros and cons of moving SQL Servers into a virtual server environment. Like all problems in the database world, there are no hard set answers on whether virtualization is a good idea, but there are some times when virtualizing a SQL Server is the best option and can save money. And then there are times when you'll be shooting yourself in the foot and shouldn't virtualize. By the end of this session, you'll know how to make this decision and ...

Buy This On-Demand Training Now!

This video is part of the Vitualization Performance Tips for Your Database On Demand training.

Database  virtualization is a powerful tool for IT departments and can help prevent server sprawl and even save money. In this new training course, you will learn whether or not virtualization is right for your database and how to get the most from your virtualized SQL Servers.

Already purchased this? to view your content.

Please or Register to post comments.

From the Blogs
Sep 29, 2015

Data Breaches and Insider Threats

I’ll sound a bit like Captain Obvious for bringing this up, but it’s important to remember that security encompasses a lot more than protecting sensitive data from the specter of outsider threats like hackers. Properly implemented security policies also account for threat-models that include insiders – or people within your organization....More
Sep 15, 2015

Setting Up Additional Checks to Ensure Regular Transaction Log Backups 1

There’s simply no way to overstate the importance of regular Transaction Log Backups. Not only do they help protect from disaster, but regular execution of T-Log backups on Full (and Bulk-Logged) Recovery databases helps keep thing “fit and trim”. Most of the time, setting up a Notification for when T-Log Backup Jobs fail is enough to let you know when something goes wrong....More
Sep 1, 2015

Stop Using INFORMATION_SCHEMA and SysObjects for Exists Checks 3

Code like this isn’t optimal: IF EXISTS(SELECT * FROM sys.objects WHERE name = N'TableToDrop' AND type = 'U')         DROP TABLE TableToDrop; GO Neither is this: IF EXISTS(SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'TableToDrop')         DROP TABLE TableToDrop; GO Yet, I see both of those used all of the time – over and over again. Even though it’s 2015.  ...More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×