In the second part of the series we discussed the way to test the log shipping status using the command “Test-DbaLogShippingStatus”.
This blog will be about how to get log shipping errors to analyze why your log shipping isn’t working.
There are several options to get the log shipping errors right out of the box. One of them is using queries and the other one is the event viewer.
In the first part of the series I described the command Invoke-DbaLogShipping.
This makes it possible to set up log shipping. This blog post will be about the command to test log shipping status. Before I describe the command, I want to discuss the options that are available in the SQL Server Management Studio (SSMS) and SQL Server.
Microsoft has made it possible to check the log shipping using SSMS. This can be done using queries or by using the “Transaction Log Shipping Status” report.
This post is the first one of a series of four describing all the different commands. We’ll discuss the commands to set up log shipping with dbatools, how to check the status, to check for errors, and to recover in case of an emergency.
Before we go into the why I want you to know what log shipping is. Log shipping dates back to the early versions of SQL Server. The first article that I could find dates back to the year 2000 and explains how to setup log shipping with SQL Server version 7.
Being a fan of automation I like to create my own PowerShell profile. It enables me to load various settings that normally take more time.
The PowerShell profile resides in your home directory and if you work in an AD environment with roaming data you’ll have the same profile on every computer. PowerShell profiles are not new and dates back to PowerShell v2.0.
Others people have written about this subject before but I wanted to share my take on it.
I’ve been working on the dbatools project for a while now and I felt like telling you why I love this project.
A little background about me, I’m not a full-time programmer. I learned to program with Java years ago and did little personal projects with PHP, C#, and a couple of other languages. I started PowerShell about 7 years ago and thought I was capable of delivering solid code. That all changed with dbatools.