August 9, 2010 at 12:45 pm
We are running SQL Server 2008 SP1, and we are starting a SharePoint 2007 project. For performance reasons, we eventually plan to implement multiple tempdb files for the instance, per Microsoft documentation. We also have several other SQL Server 2008 instances. Many of our tempdb databases are configured the same, but some are different because of application specific needs.
Out of the box, SQL Server does not allow the tempdb database to be backed up, and I have not found a way to script the tempdb database within SQL Server Management Studio in order to capture its configuration for Disaster Recovery purposes. Consequently, I am concerned that we may have end up with an issue if we ever have to bring one of the instances back from tape in a Disaster Recovery scenario because the default tempdb of the Disaster Recovery instance may not meet the application needs for the recovered instance.
We could track the various tempdb configurations manually in a spreadsheet, or something similar, but I would rather have the documentation generated by our nightly database backup script so that the documentation will always be accurate if the various tempdb configurations change over time. (Sadly, good intentions to update existing manual documentation can go awry when the phone rings with the day’s next forest fire…)
Does anyone know of a way to automate the capture of the tempdb configuration for an instance?
August 9, 2010 at 1:19 pm
Best practice is going to be making a script for each server that specifies how it is done (out of the box this will be manual) and the storing that script in a central repository. You don't back up tempdb and the scripting tools don't let you script out the DB itself. Part of DR is having good documentation, and you would keep creation scripts as part of that documentation.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply