T-SQL Tuesday #015 – Spend time now to save time later

It’s T-SQL Tuesday time again and this month I’m a little late off the starting block. This time it is being hosted by Pat Wright blog|twitter and the subject of the month is all about “Automation in SQL Server”.

So what is my favourite automation script or technique that I use in SQL Server? I had to have a think about this and my problem is that I have quite a few. I believe that the accessibility and usability of the Windows and SQL GUI (and related tools) means that SQL DBAs in particular have a tendency to automate much more than other IT Professionals.

So when should we automate? There are lots of answers to this question and here are a few possibilities :-

  • To enforce standards – for instance naming through run-time script checks.
  • For repetitive tasks – how often are you prepared to repeat a task before you bang your head against a wall?
  • For time consuming operations -if you can automate a task you can schedule it to run out of hours.
  • To simplify/ customise operations in an easy to use way -finding blocked spids is easy via querying DMVs, but doing so via executing a stored procedure or custom view could be even easier.

In my current environment one very common task is to refresh databases from adhoc backups of like databases from other environments, and scripting the restore statement every time can be a big pain. In particular I want to ensure that the file names of the database to be refreshed are overwritten (remain the same) so I have written a quick script that simplifys this exercise somewhat. I don’t pretend it is the finished article and need to make improvements, but it does enough right now. Please note that I am using the compatibility view ‘sysfiles’ for the reason of backwards compatibility at this stage (so the code can run on SQL 2000). This is how to use it…

  1. On the server that you are going to overwrite the database in question, load up the script in SSMS and change context into that database.
  2. For the @backupfilefull variable, assign the location to the full backup file of the database you wish to restore.
  3. Execute the script and it will output a T-SQL script that you can copy and execute.

Please be warned that this will OVERWRITE the database specified in the script but will at least first will backup the transaction log. Also note that I do not attempt to kill off SPIDs from the database so at least if you do make a blunder, if your database is active it gives you a chance of it failing.

-- =============================================
-- Author:            Mark Broadbent
-- Create date: 01/01/2009
-- Description: generates script to restore the current context database
-- Version: 0.1
-- =============================================

--this script generates a script to restore the current context database
--set source database to generate restore script from
DECLARE @backupfilefull SYSNAME
DECLARE @databasename SYSNAME
SET @databasename = db_name()
--set path to source database backup file
SET @backupfilefull = ''

DECLARE @@cmd VARCHAR(4000)
SET @@cmd = '--***WARNING*** this script will completely overwrite the database name that has been specified please CHECK this connection is on the correct deployment server!!!' + CHAR(10)
SET @@cmd = @@cmd + 'BACKUP LOG ' + @databasename + ' TO DISK = ''' + @backupfilefull + '_tail_of_log_prior_to_norecovery_mode.log'' WITH STATS = 1, NORECOVERY' + CHAR(10)
--generate restore statement
SET @@cmd = @@cmd + 'RESTORE DATABASE ' + @databasename + ' FROM DISK = ''' + @backupfilefull + ''' WITH STATS = 1, NORECOVERY'
SELECT @@cmd = @@cmd + CHAR(10) +',MOVE ''' + RTRIM(name) + ''' TO ''' + RTRIM(filename) + '''' FROM sysfiles

--output generated restore script
PRINT @@cmd

--ensure connection leaves context
USE MASTER
GO

Well I hope you find this script useful, and please remember to be careful with it – I take no responsibility for it’s use. 🙂

So to wrap up this post, I’ll pose the question “How do we know when is a good time to automate?” and from my experience I would suggest that the answer is usually always. Even on those occasions where your automation code is never used again for the purpose you wrote it for, nine times out of ten I bet you will refer back to it and use snippets of it for something else. Always try to… Spend time now to save time later!

Advertisements
This entry was posted in Events, SQL, SQLServerPedia Syndication, Storage and tagged , , , , . Bookmark the permalink.

4 Responses to T-SQL Tuesday #015 – Spend time now to save time later

  1. John Sansom says:

    Great post Mark and thanks for the script share. I’m always on the hunt for code snippets to add to my DBA tool kit.

    “How do we know when is a good time to automate?” – That’s easy, it’s all the time right, after all The Best Database Administrators Automate Everything 🙂

  2. retracement says:

    For anyone who has grabbed this script before this comment please note that I had left a trailing comment symbol ‘–‘ before the backup log statement. I have removed this for preciseness, however personally I would normally manually perform this step from the script (by highlight and execute) which is why I had it there to form the comment. This offered me and extra level of protection from the RESTORE statement but obviously detracted from the “automation” aspect. Therefore depending upon what side you err on you might want it in. If you do then that Backup Log line should read “SET @@cmd = @@cmd + ‘–BACKUP LOG ‘ + @databasename + ‘ TO DISK = ”’ + @backupfilefull + ‘_tail_of_log_prior_to_norecovery_mode.log” WITH STATS = 1, NORECOVERY’ + CHAR(10)” –note the dash dash before the BACKUP LOG

  3. Pingback: T-SQL Tuesday #15 Summary | Sql Server Insane Asylum

Comments are closed.