SQL Server VLDB in Azure: DBA Tasks Made Simple The definition of VLDB has been shifting in recent years, but most DBAs would agree that complexities become significant starting with database size in the 3-5 TB range A few obvious examples of tasks that are more challenging with a VLDB are backup restore, consistency checking, HA DR, partitioning, etc
Quick list of VLDB maintenance best practices One evening last week I sat down with Kimberly for 5 minutes to come up with a top-of-our heads list of VLDB maintenance concerns for a company migrating a multi-TB database to SQL Server 2005 This isn't in any way based on the VLDB survey I've been doing (see previous posts) but is a common-sense list of things that everyone should do
Running SAP Applications on the Microsoft Platform VLDB Migrations require do considerable skill, attention to detail and analysis For example the net impact of Table Splitting must be measured and analyzed Splitting a large table into more than 50 parallel exports may considerably decrease the time taken to Export a table, but too many Table Splits may result in drastically increased Import
CHECKDB (Part 6): Consistency checking options for a VLDB These databases are now common on SQL Server 2000 and 2005, with more migrations happening all the time Any sensible DBA knows the value of running consistency checks, even when the system is behaving perfectly and the hardware is rock-solid The two problems that people have with running a full DBCC CHECKDB on their VLDB are:
VLDB Maintenance Practices and Problems? | Microsoft Community Hub I’ll be doing lots around VLDB maintenance in the coming months so I’d like to get more info from all of you about what’s happening in the field I’ll be working on Katmai features, strategizing about Katmai+, blogging on maintenance topics, planning lectures, including a session for TechEd – VLDB Maintenance Q A – and much more