I'm facing a rather strange issue with Transaction Log Shipping reports in SSMS which is showing multiple red alerts of databases that have been created and deleted while performing multiple Log Shipping scenario between two servers.
I've used the following post:Remove the log shipping configuration on the secondary server, when the primary is no longer available to help clear those alerts but nothing came out of this with success. Sometimes i'm getting the following error:

Msg 32011, Level 16, State 1, Procedure sp_delete_log_shipping_primary_database, Line 51 Primary Database MyFirstDB has active log shipping secondary database(s). Drop the secondary database(s) first

Which is not true as the database is already deleted on both primary and secondary server as well as three log shipping jobs.
I have more than forty orphaned databases in this state. this is saturating SQL server log with the below error for all aforementioned databases:

Date 19/08/2017 08:30:00 Log SQL Server (Archive #3 - 19/08/2017 08:31:00)

Source spid53

The log shipping secondary database SQLTEST.MyFirstDB has restore threshold of 30 minutes and is out of sync. No restore was performed for 449177 minutes. Restored latency is 2 minutes. Check agent

Can you help please, clear these entries from wherever system database/tables holds these records.?
I really appreciate the help!


Information about databases involved in log shipping are contained in several system tables in the msdb database. Looking at these tables will help identify whether you've properly reconfigured log shipping.

This first query shows databases that are configured as primaries, where the database no longer exists on the SQL Server instance:

SELECT lspd.primary_database
    , lspd.last_backup_date
FROM msdb.dbo.log_shipping_primary_databases lspd
    SELECT 1
    FROM master.sys.databases d
    WHERE d.name = lspd.primary_database 

This query will show secondaries for the databases identified above:

SELECT lsps.secondary_server
    , lsps.secondary_database
FROM msdb.dbo.log_shipping_primary_secondaries lsps
        SELECT lspd.primary_id
        FROM msdb.dbo.log_shipping_primary_databases lspd
            SELECT 1
            FROM master.sys.databases d
            WHERE d.name = lspd.primary_database 
        ) p ON p.primary_id = lsps.primary_id;

Use sys.sp_delete_log_shipping_primary_secondary to remove primary databases from the log shipping configuration.

Use sys.sp_delete_log_shipping_secondary_database to remove affected secondaries, if desired, which should stop the alerts you're seeing.

The Microsoft Docs page on monitoring log shipping shows several useful details, including the following tables that are used by the monitor process:

  • log_shipping_monitor_alert - Stores alert job ID.

  • log_shipping_monitor_error_detail - Stores error details for log shipping jobs. You can query this table see the errors for an agent session. Optionally, you can sort the errors by the date and time at which each was logged. Each error is logged as a sequence of exceptions, and multiple errors (sequences) can per agent session.

  • log_shipping_monitor_history_detail - Contains history details for log shipping agents. You can query this table to see the history detail for an agent session.

  • log_shipping_monitor_primary - Stores one monitor record for the primary database in each log shipping configuration, including information about the last backup file and last restored file that is useful for monitoring.

  • log_shipping_monitor_secondary - Stores one monitor record for each secondary database, including information about the last backup file and last restored file that is useful for monitoring.

Querying the contents of those tables should help you narrow down the source of the alerts. The page I mentioned above also contains details about several monitoring stored procedures you can use to query the tables.

The "Transaction Log Shipping Status" report calls the sp_help_log_shipping_monitor stored procedure to get its details - looking at the T-SQL definition of that stored proc may help you resolve where the issue is.

| improve this answer | |
  • Hello @MaxVernon i'm getting the below error while running the second query against the second sql instanc: Msg 512, Level 16, State 1, Line 1 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. any advice.? Thanks again for the first shot of your the asnwer you've provided me. – Tecina Aug 22 '17 at 14:31
  • @Tecina - I've modified the second query - it should work now. – Max Vernon Aug 22 '17 at 15:47
  • sorry for the delays, i had to manually run both queries against all found databases in primary (~60 db) and secondary (~ 77 db) instance. Both queries ran successfully. However i'd like to know if i need SQL Server service restart for the changes to take effect. 'Cause re-running Transaction Log reports got me the same results as before. I even tried to run the queries you provided above and still got me the same exact number and name of databases as before. Thanks for your feedback on this. – Tecina Aug 23 '17 at 11:31
  • @Tecina - I added some details to my answer that may help – Max Vernon Aug 23 '17 at 14:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.