1. Conquering the Giants:Very Large Databases For audio, call the phone number in your meeting invite. Audio will not come through the computer speakers.

2. SQL Server Expertfor Quest Software Editor-in-Chief at SQLServerPedia.com Former SQL DBA Managed data warehouses,>80tb SAN storage for $7b company

3. Conquering the Giants: Agenda What’s a VLDB? Ginormous Growth Big Backups Tremendous Tables Slow SQL Statements Your Wingman: Quest Resources Photo Licensed with Creative Commons from http://www.flickr.com/photos/pagedooley/2172001078/

4. What Makes a VLDB? 1 terabyte Billion rows But Not:User Qty,Criticality,Transactions Per Second 4 Photo Licensed with Creative Commons from http://www.flickr.com/photos/tcmhitchhiker/1053095394

5. VLDB Space Challenges 5

6. Default File Growth Settings 6

7. Starts Out Small… 7

8. Ginormous Growths 8

9. Instant File Init in Secpol.msc 9

10. VLDBs = Big Backups Time Problem Nightly Load Windows Time to Recover Dev, QA, Test, DR 10

11. Giant Monstrous Backups 11

12. Cutting Them Down to Size 12

13. Next Weapon: SAN Snapshots 13

14. Post-Snapshot 14

15. Making the Snap Available 15

16. Weapon: Backup Compression 16 Photo Licensed with Creative Commons from http://www.flickr.com/photos/tcmhitchhiker/1053045338/

17. Or – Compress Everything! 17

18. VLDB Problem: Giant Tables 18

19. Hunt Down and Kill Unused Indexes 19

20. Breaking Giants Into Pieces 20

21. The New Way: Partitioning 21

22. Partitioning Basics Create filegroups Create files in the filegroups Design partition function Design partition scheme Alter table’s clustered index 22

23. Sliding Window Loads Partition by day Create newtable similarto Sales table,on same filegroup Load one day’sdata into empty table Swap out a partition for that table 23

24. Giant Drawbacks Not easy to change Requires lots of experimentation Partition elimination doesn’t always work Requires familiarity with queries, data Storage skills help Hardware-dependent 24 Photo Licensed with Creative Commons from http://www.flickr.com/photos/cellphonesusie/3224335140/

25. SQLCAT MAXDOP FAQ 25

26. The New-New Way: 2008 R2 26

27. Slow SQL Statements 27

28. Your Shovel: Resource Governor Slows zombie queries down Throttle CPU, memory Can throttle jobs, backups too Doesn’t throttle storage (yet) 28 Photo Licensed with Creative Commons from http://www.flickr.com/photos/archiemcphee/3612278108/

29. Implementing The Governator Workload groups: ETL processes Reports AdHoc Resource pool: ETL Reports Classification function based on: Login name Application name 29 Photo Licensed with Creative Commons from http://www.flickr.com/photos/shaunwong/2467881648/

30. End Results in SSMS 2008 30

31. Resource Governor Caveats Ask the network team about QoS Get manager consensus on SLAs Keep it absolutely transparent Avoid false alarms about performance problems Teach managers how to “see” it working 31

32. Your Wingman: Quest Software Capacity Manager v3.0 Capacity Planning Index Defragmentation Partitioning GUI LiteSpeed v5.1 SmartDiffs Throttled Compression 32

33. Showing the Giant Who’s Boss Use Instant File Initialization Consider Differential Backups Compress Data Drop Baggage Partitioning FTW Resource Governator Check Out QuestCapacity Manager Photo Licensed with Creative Commons from http://www.flickr.com/photos/keeg/1661401660/

34. VLDB Resources Presentation Resources:http://sqlserverpedia.com/wiki/VLDB Quest Software:http://www.quest.com/sql-server/ Upcoming Webcasts:http://www.quest.com/events