What is DBA Tools?
A collection of modules for SQL Server DBAs. It initially started out as ‘sqlmigration’, but has now grown into a collection of various commands that help automate DBA tasks and encourage best practices.
You can read more about here and it is freely available for download on GitHub I thoroughly recommend that you watch this quick video to see just how easy it is to migrate an entire SQL instance in one command (Longer session here )
Installing it is as easy as
which will get you over 80 commands . Visit https://dbatools.io/functions/ to find out more information about them
The journey to Remove-SQLDatabaseSafely started with William Durkin b | t who presented to the SQL South West User Group (You can get his slides here)
Following that session I wrote a Powershell Script to gather information about the last used date for databases which I blogged about here and then a T-SQL script to take a final backup and create a SQL Agent Job to restore from that back up which I blogged about here The team have used this solution (updated to load the DBA Database and a report instead of using Excel) ever since and it proved invaluable when a read-only database was dropped and could quickly and easily be restored with no fuss.
I was chatting with Chrissy LeMaire who founded DBATools b | t about this process and when she asked for contributions in the SQL Server Community Slack I offered my help and she suggested I write this command. I have learnt so much. I thoroughly enjoyed and highly recommend working on projects collaboratively to improve your skills. It is amazing to work with such incredible professional PowerShell people.
I went back to the basics and thought about what was required and watched one of my favourite videos again. Grant Fritcheys Backup Rant
I decided that the process should be as follows
- Performs a DBCC CHECKDB
- Database is backed up WITH CHECKSUM
- Database is restored with VERIFY ONLY on the source
- An Agent Job is created to easily restore from that backup
- The database is dropped
- The Agent Job restores the database
- performs a DBCC CHECKDB and drops the database for a final time
This (hopefully) passes all of Grants checks. This is how I created the command
I check that the SQL Agent is running otherwise we wont be able to run the job. I use a while loop with a timeout like this
$agentservice = Get-Service -ComputerName $ipaddr -Name $serviceName
if ($agentservice.Status -ne 'Running')
$timeout = new-timespan -seconds 60
$sw = [diagnostics.stopwatch]::StartNew()
$agentstatus = (Get-Service -ComputerName $ipaddr -Name $serviceName).Status
while ($dbStatus -ne 'Running' -and $sw.elapsed -lt $timeout)
$dbStatus = (Get-Service -ComputerName $ipaddr -Name $serviceName).Status
There are a lot more checks and logic than I will describe here to make sure that the process is as robust as possible. For example, the script can exit after errors are found using DBCC CHECKDB or continue and label the database backup file and restore job appropriately. Unless the force option is used it will exit if the job name already exists. We have tried to think of everything but if something has been missed or you have suggestions let us know (details at end of post)
The only thing I didn’t add was a LARGE RED POP UP SAYING ARE YOU SURE YOU WANT TO DROP THIS DATABASE but I considered it!!
Performs a DBCC CHECKDB
Running DBCC CHECKDB with Powershell is as easy as this
$sourceserver = New-Object Microsoft.SQLServer.Management.Smo.Server "ServerName"
$db = $sourceserver.databases[$dbname]
$null = $db.CheckTables('None')
you can read more on MSDN
Database is backed up WITH CHECKSUM
Stuart Moore is my go to for doing backups and restores with SMO
I ensured that the backup was performed with checksum like this
$backup = New-Object -TypeName Microsoft.SqlServer.Management.Smo.Backup
$backup.Action = [Microsoft.SqlServer.Management.SMO.BackupActionType]::Database
$backup.BackupSetDescription = "Final Full Backup of $dbname Prior to Dropping"
$backup.Database = $dbname
$backup.Checksum = $True
Database is restored with VERIFY ONLY on the source
I used SMO all the way through this command and performed the restore verify only like this
$restoreverify = New-Object 'Microsoft.SqlServer.Management.Smo.Restore'
$restoreverify.Database = $dbname
$result = $restoreverify.SqlVerify($sourceserver)
An Agent Job is created to easily restore from that backup
First I created a category for the Agent Job
if ($Pscmdlet.ShouldProcess($sourceserver,"Creating Agent Job Category $categoryname")
Write-Output "Creating Agent Job Category $categoryname"
$category = New-Object Microsoft.SqlServer.Management.Smo.Agent.JobCategory
$category.Parent = $jobServer
$category.Name = $categoryname
Write-Output "Created Agent Job Category $categoryname"
throw "FAILED : To Create Agent Job Category $categoryname - Aborting"
and then generated the TSQL for the restore step by using the script method on the Restore SMO object
This is how to create an Agent Job
$job = New-Object Microsoft.SqlServer.Management.Smo.Agent.Job $jobServer, $jobname
$job.Name = $jobname
$job.OwnerLoginName = $jobowner
$job.Description = "This job will restore the $dbname database using the final backup located at $filename"code]</pre>
and then to add a job step to run the restore command
<pre>$jobStep = new-object Microsoft.SqlServer.Management.Smo.Agent.JobStep $job, $jobStepName
$jobStep.SubSystem = 'TransactSql' # 'PowerShell'
$jobStep.DatabaseName = 'master'
$jobStep.Command = $jobStepCommmand
$jobStep.OnSuccessAction = 'QuitWithSuccess'
$jobStep.OnFailAction = 'QuitWithFailure'
if ($Pscmdlet.ShouldProcess($destination, "Creating Agent JobStep on $destination"
$null = $jobStep.Create()
$job.StartStepID = $jobStartStepid
The database is dropped
We try 3 different methods to drop the database
$null = $server.ConnectionContext.ExecuteNonQuery("DROP DATABASE "code]</pre>
<h2>The Agent Job restores the database</h2>
To run the Agent Job I call the start method of the Job SMO Object
$job = $destserver.JobServer.Jobs[$jobname]
$status = $job.CurrentRunStatus
while ($status -ne 'Idle')
Write-Output "Restore Job for $dbname on $destination is $status"
$status = $job.CurrentRunStatus
Start-Sleep -Seconds 5
Then we drop the database for the final time with the confidence that we have a safe backup and an easy one click method to restore it from that backup (as long as the backup is in the same location)
You can install it with
You too can also become a contributor https://dbatools.io/join-us/
Come and write a command to make it easy for DBAs to (this bit is up to your imagination).