Big data’s grandpa is the Very Large DataBase (VLDB) and we’ve been doing VLDBs in SQL Server for years. Making the jump from managing 10-100GB databases to the terabyte level can be intimidating, but in this 30-minute session, Brent Ozar will share the lessons he learned along the way so you don’t have to get burned. He’ll cover the basics of why backups, restores, DBCCs, and query tuning are so different for VLDBs.
Like this? Want to see more? Check out our upcoming webcasts:
April 10 – Database Darwin Awards: T-SQL Developer Edition
Brent Ozar, Tech Triage Tuesday
Working in the SQL Server emergency room, I see a lot of self-inflicted performance wounds. That query looks good, and it looks like it’s using an index – but why does it take so long? The query runs great half the time, but the rest of the time performance is cut off at the knees, and the only fix is to restart the server. Learn the top 3 T-SQL traumas I see in consulting engagements, and find out whether they’re affecting your environment. Register now.
April 18 – Scaling SQL on Solid State: Hot & Crazy
Brent Ozar, South Florida SQL User Group (SFSSUG) (Remote)
April 24 – How to Test Availability Groups in SQL Server 2012
Kendra Little, Tech Triage Tuesday
Want a jump-start on testing the hottest scale-out feature in SQL Server 2012? Kendra Little will tell you why it’s critical that you configure your own lab, and what you need to get your test environment set up. She’ll also detail how to avoid some gotchas that could cost you hours of frustration. She’ll demonstrate the steps you need to enable the Availability Group feature in SQL Server 2012 and how to create and test your first Availability Group. This session is appropriate for DBAs with one or more years of experience with SQL Server. Register now.
Edward Allison April 9, 2012 | 12:53 pm
Loved this. Very useful and well presented.
Jeffry April 10, 2012 | 8:19 am
Great presentation about VLDB, you talked about partitioning big tables could improve performance a lot and at the same time having an archive plan for those records could reduce I/O performance cause it reading less, if the DB, most of its space is on Blob Data can we considerate it as a VLDB (3 Tb) ? what would be the best practices for it ?
besides when you talk about snapshot DB they work fantastic and the way you explained, it was what i expected, but could you tell me a case when a snapshot could not recover a database ?
thanks brent and your team for all your effort and collaboration.
Brent Ozar April 10, 2012 | 8:32 am
Jeffry – thanks, glad you liked the video! Generally any database over 1b rows or 1TB in size is considered a VLDB. Since you’ve got 3TB, that would qualify.
A database snapshot can’t be used to restore a database if there’s storage corruption that affects both the database and the snapshot, for example.