REPLACE option impact
queriesWhen restoring a database to SQL Server 2022 (16.x) from a previous version, it is
recommended to execute
on the database, setting the proper metadata for the
statistics auto drop feature. For more information, see
statistics auto drop option.
Certain operations, including configuring server (instance level) settings, or manually adding a
database to an availability group, require a connection to the SQL Server instance. Operations
like
,
, or any DDL command in a database belonging to an
availability group require a connection to the SQL Server instance. By default, a big data cluster
does not include an endpoint that enables a connection to the instance. You must expose this
endpoint manually.
For instructions, see
Connect to databases on the primary replica.
includes backup and restore history tables that track the backup and restore activity
for each server instance. When a restore is performed, the backup history tables are also
modified. For information on these tables, see
Backup History and Header Information.
REPLACE should be used rarely and only after careful consideration. Restore normally prevents
accidentally overwriting a database with a different database. If the database specified in a
RESTORE statement already exists on the current server and the specified database family GUID
differs from the database family GUID recorded in the backup set, the database is not restored.
This is an important safeguard.
The REPLACE option overrides several important safety checks that restore normally performs.
The overridden checks are as follows:
Restoring over an existing database with a backup taken of another database.
With the REPLACE option, restore allows you to overwrite an existing database with
whatever database is in the backup set, even if the specified database name differs from
the database name recorded in the backup set. This can result in accidentally overwriting
a database by a different database.
Big Data Clusters
sp_updatestats
sp_configure
RESTORE DATABASE