You have an on-premises Microsoft SQL server that has a database named DB1. DB1 contains several tables that are stretched to Microsoft Azure.

From SQL Server Management Studio (SSMS), a junior database administrator accidentally deletes several rows from the Azure SQL database and breaks the connection to Azure.

You need to resume Stretch Database operations.

Which two stored procedures should you use? Each correct answer presents part of the solution.

NOTE:

Each correct selection is worth one point.

A. sys.sp_rda_reconcile_batch

B. sys.sp_rda_reconcile_indexes

C. sys.sp_rda_reauthorize_db

D. sys.sp_rda_reconcile_columns

E. sys.sp_rda_set_rpo_duration

sys.sp_rda_reauthorize_db restores the authenticated connection between a local database enabled for Stretch and the remote database.

If you have accidentally deleted columns from the remote table, run sp_rda_reconcile_columns to add columns to the remote table that exist in the Stretch-enabled SQL Server table but not in the remote table.

Incorrect Answers:

A: sys.sp_rda_reconcile_batch reconciles the batch ID stored in the Stretch-enabled SQL Server table with the batch ID stored in the remote Azure table.

Typically you only have to run sp_rda_reconcile_batch if you have manually deleted the most recently migrated data from the remote table. When you manually delete remote data that includes the most recent batch, the batch IDs are out of sync and migration stops.

References:

https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sys-sp-rda-reconcile-batch-transact-sql

https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sys-sp-rda-reauthorize-db-transact-sql