You maintain Microsoft SQL Server instances named SVR1 and SVR2 that are hosted on two different servers.
You configure log shipping between the two instances as follows:
– DB1 on SVR1 is configured as the primary database.
– DB1 on SVR2 is configured as the secondary database for DB1 on SVR1.
– No monitoring server is configured.
You need to monitor error log messages about the copy job.
What are two possible ways to achieve this goal? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
A . On SVR1, run the following Transact-SQL statement: SELECT * FROM msdb.dbo.log_shipping_monitor_error_detail.
B . Use the job Activity Monitor in SQL Server Management Studio by connecting to SVR1
C . View the Log Shipping Report in SQL Server Management Studio by connecting SVR1.
D . Use the Job Activity Monitor in SQL Server Management Studio by connecting to SVR2.
E . On SVR2 run the following Transact-SQL statement: SELECT * FROM msdb.dbo.log_shipping_monitor_error_detail.
Answer: C,E
Explanation:
C: The Log Shipping Report displays the status of any log shipping activity whose status is available from the server instance to which you are connected.
E: The history and status of the backup operation are stored at the primary server, and the history and status of the copy and restore operations are stored at the secondary server.
The log_shipping_monitor_error_detail table 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.
References: https://docs.microsoft.com/en-us/sql/database-engine/log-shipping/view-the-log-shipping-reportsql-server-management-studio?view=sql-server-2017 https://docs.microsoft.com/en-us/sql/database-engine/log-shipping/monitor-log-shipping-transactsql