Merge pull request #28595 from rwestMSFT/rw-0927-fix-9351

Refresh create database snapshot and include issue 9351

Author: prmerger-automator[bot]

docs/relational-databases/databases/create-a-database-snapshot-transact-sql.md

@@ -4,7 +4,7 @@ description: "Find out how to create a SQL Server database snapshot by using Tra
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: randolphwest
-ms.date: 07/21/2023
+ms.date: 09/28/2023
 ms.service: sql
 ms.subservice: configuration
 ms.topic: conceptual
@@ -15,21 +15,21 @@ helpviewer_keywords:
 
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-The only way to create a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database snapshot is to use [!INCLUDE[tsql](../../includes/tsql-md.md)]. [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] doesn't support the creation of database snapshots.
+The only way to create a [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] database snapshot is to use [!INCLUDE [tsql](../../includes/tsql-md.md)]. [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] doesn't support the creation of database snapshots.
 
 ## Prerequisites
 
 The source database, which can use any recovery model, must meet the following prerequisites:
 
-- The server instance must be running an edition of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that supports database snapshot. For information about support for database snapshots in [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)], see [Editions and supported features of SQL Server 2022](../../sql-server/editions-and-components-of-sql-server-2022.md).
+- The server instance must be running an edition of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] that supports database snapshot. For information about support for database snapshots in [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)], see [Editions and supported features of SQL Server 2022](../../sql-server/editions-and-components-of-sql-server-2022.md).
 
 - The source database must be online, unless the database is a mirror database within a database mirroring session.
 
 - To create a database snapshot on a mirror database, the database must be in the synchronized [mirroring state](../../database-engine/database-mirroring/mirroring-states-sql-server.md).
 
 - The source database can't be configured as a scalable shared database.
 
-- Prior to SQL Server 2019, the source database could not contain a MEMORY_OPTIMIZED_DATA filegroup. Support for in-memory database snapshots was added in SQL Server 2019.
+- Prior to [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)], the source database couldn't contain a `MEMORY_OPTIMIZED_DATA` filegroup. Support for in-memory database snapshots was added in [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)].
 
 > [!IMPORTANT]  
 > For information about other significant considerations, see [Database Snapshots (SQL Server)](database-snapshots-sql-server.md).
@@ -44,15 +44,15 @@ This section discusses the following best practices:
 
 #### <a id="naming"></a> Best practice: naming database snapshots
 
-Before creating snapshots, it is important to consider how to name them. Each database snapshot requires a unique database name. For administrative ease, the name of a snapshot can incorporate information that identifies the database, such as:
+Before creating snapshots, it's important to consider how to name them. Each database snapshot requires a unique database name. For administrative ease, the name of a snapshot can incorporate information that identifies the database, such as:
 
 - The name of the source database.
 
 - An indication that the new name is for a snapshot.
 
 - The creation date and time of the snapshot, a sequence number, or some other information, such as time of day, to distinguish sequential snapshots on a given database.
 
-For example, consider a series of snapshots for the [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)] database. Three daily snapshots are created at 6-hour intervals between 6 A.M. and 6 P.M., based on a 24-hour clock. Each daily snapshot is kept for 24 hours before being dropped and replaced by a new snapshot of the same name. Each snapshot name indicates the hour, but not the day:
+For example, consider a series of snapshots for the [!INCLUDE [ssSampleDBobject](../../includes/sssampledbobject-md.md)] database. Three daily snapshots are created at 6-hour intervals between 6 A.M. and 6 P.M., based on a 24-hour clock. Each daily snapshot is kept for 24 hours before being dropped and replaced by a new snapshot of the same name. Each snapshot name indicates the hour, but not the day:
 
 ```output
 AdventureWorks_snapshot_0600
@@ -70,14 +70,14 @@ AdventureWorks_snapshot_evening
 
 #### <a id="limiting-number"></a> Best practice: limiting the number of database snapshots
 
-Creating a series of snapshots over time captures sequential snapshots of the source database. Each snapshot persists until it is explicitly dropped. Because each snapshot will continue to grow as original pages are updated, you may want to conserve disk space by deleting an older snapshot after creating a new snapshot.
+Creating a series of snapshots over time captures sequential snapshots of the source database. Each snapshot persists until it's explicitly dropped. Because each snapshot will continue to grow as original pages are updated, you may want to conserve disk space by deleting an older snapshot after creating a new snapshot.
 
 > [!NOTE]  
 > To revert to a database snapshot, you need to delete any other snapshots from that database.
 
 #### <a id="client-connections"></a> Best practice: client connections to a database snapshot
 
-To use a database snapshot, clients need to know where to find it. Users can read from one database snapshot while another is being created or deleted. However, when you substitute a new snapshot for an existing one, you need to redirect clients to the new snapshot. Users can manually connect to a database snapshot with [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or Azure Data Studio. However, to support a production environment, you should create a programmatic solution that transparently directs report-writing clients to the latest database snapshot of the database.
+To use a database snapshot, clients need to know where to find it. Users can read from one database snapshot while another is being created or deleted. However, when you substitute a new snapshot for an existing one, you need to redirect clients to the new snapshot. Users can manually connect to a database snapshot with [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or Azure Data Studio. However, to support a production environment, you should create a programmatic solution that transparently directs report-writing clients to the latest database snapshot of the database.
 
 ## Permissions
 
@@ -96,7 +96,7 @@ Any user who can create a database can create a database snapshot; however, to c
        NAME = logical_file_name
        , FILENAME = 'os_file_name'
    ) [ , ...n ]
-  
+
    AS SNAPSHOT OF source_database_name
    [;]
    ```
@@ -113,11 +113,11 @@ Any user who can create a database can create a database snapshot; however, to c
    For a full description of this syntax, see [CREATE DATABASE (SQL Server Transact-SQL)](../../t-sql/statements/create-database-transact-sql.md#as-snapshot-of-source_database_name).
 
    > [!NOTE]  
-   > When you create a database snapshot, log files, offline files, restoring files, and defunct files are not allowed in the `CREATE DATABASE` statement.
+   > When you create a database snapshot, log files, offline files, restoring files, and defunct files aren't allowed in the `CREATE DATABASE` statement.
 
 ## Examples
 
-The `.ss` extension used in these examples is for convenience, and is not required.
+The `.ss` extension used in these examples is for convenience, and isn't required. In databases containing multiple files, all files must be specified, in conformance with the syntax. Filegroups aren't specified.
 
 #### A. Create a snapshot on the AdventureWorks database
 
@@ -164,13 +164,10 @@ CREATE DATABASE sales_snapshot1200 ON (
 GO
 ```
 
-## See also
+## Related content
 
 - [CREATE DATABASE (Transact-SQL)](../../t-sql/statements/create-database-transact-sql.md)
 - [Database Snapshots (SQL Server)](database-snapshots-sql-server.md)
-
-## Next steps
-
 - [View a Database Snapshot (SQL Server)](view-a-database-snapshot-sql-server.md)
 - [Revert a Database to a Database Snapshot](revert-a-database-to-a-database-snapshot.md)
 - [Drop a Database Snapshot (Transact-SQL)](drop-a-database-snapshot-transact-sql.md)