Session 2: Virtualization and the Cloud for DBAs


Presented by: Allan Hirt and Ben DeBow Running Time: 53 min We live in a world where deploying solutions on physical hardware is becoming more the exception than the rule. All DBAs need to understand about virtualization and what it means to their deployments of SQL Server in all aspects. DBAs also cannot bury their heads in the sand with regards to the cloud (public or private), either. This session will cover what SQL Server DBAs will have to consider as their jobs change to include ...

Buy This On-Demand Training Now!

This video is part of the SQL Server Foundations On Demand Training.

Are you new to SQL Server? Looking to brush up your skills? Thrust into a SQL Server DBA role or been asked to administer some databases? Are you only familiar with another RDBMS or a Windows administrator? Is your company implementing a SQL Server-based application and you are familiar only with another vendor’s RDBMS? This two-day, six-part series is designed for you.

Already purchased this? to view your content.

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) ×