top of page

New WITH Clauses in SQL Server’s CREATE AVAILABILITY GROUP Command

SQL Server’s CREATE AVAILABILITY GROUP command is a crucial tool in the arsenal of database administrators. It allows the creation of Availability Groups (AGs), a key component in ensuring high availability and disaster recovery of SQL Server databases.


Data Definition Language (DDL) changes in SQL Server play a significant role in enhancing the functionality and flexibility of this command. These changes allow for more efficient management of AGs and can impact database performance and resource utilization.

New WITH Clauses in SQL Server’s CREATE AVAILABILITY GROUP Command

Understanding Availability Groups in SQL Server

Availability Groups in SQL Server are a set of user databases that fail over together. This ensures continuous data availability and minimizes data loss during a failover. An AG supports a failover environment for a discrete set of user databases, known as availability databases.


The role of DDL in managing Availability Groups is crucial. DDL commands allow administrators to define and manage data structures within the database. This includes creating, altering, and dropping database objects.


New WITH Clauses in SQL Server’s CREATE AVAILABILITY GROUP Command

The recent DDL changes in the CREATE AVAILABILITY GROUP command have introduced new options that provide more control and flexibility in managing their AGs to administrators.


CONTAINED Clause

The CONTAINED clause is used when creating a Contained Availability Group. In a Contained AG, in addition to the instance level, metadata objects such as users, logins, permissions, and SQL Agent jobs are managed at the AG level. This containment simplifies the management and failover processes.


Here’s an example of how you might use the CONTAINED clause:

CREATE AVAILABILITY GROUP [AG_Example] 
WITH (CONTAINED = ON) 
FOR DATABASE [YourDatabase] 
REPLICA ON N'Server1' WITH (ENDPOINT_URL = N'TCP://Server1:5022', 
	FAILOVER_MODE = AUTOMATIC, AVAILABILITY_MODE = SYNCHRONOUS_COMMIT, 
	BACKUP_PRIORITY = 50, SEEDING_MODE = AUTOMATIC);

In this, AG_Example is the name of the Availability Group being created. The WITH (CONTAINED = ON) clause specifies that we want to use the CONTAINED option, meaning metadata objects will be managed at the AG level.


Benefits:

  • Simplified Management: With the CONTAINED clause, metadata objects are managed at the Availability Group (AG) level, simplifying the management process. You don’t need to synchronize logins and jobs across replicas.

  • Easier Failover Process: Since the metadata objects are contained within the AG, failovers become more straightforward as there’s no need to transfer logins and jobs to the new primary replica.


Use Cases:

  • Multi-Tenant Environments: The CONTAINED clause is particularly useful in multi-tenant environments where database-level autonomy is required. Each tenant’s data and metadata can be managed independently within its AG.

  • High Availability and Disaster Recovery (HADR) Solutions: The CONTAINED clause simplifies the implementation of HADR solutions by making failovers more straightforward.


REUSE_SYSTEM_DATABASES Clause

The REUSE_SYSTEM_DATABASES clause allows the reuse of system databases during the Availability Group creation. System databases, created when SQL Server is installed, are integral to the server's functioning. Reusing them can save significant time and resources during the AG creation process.


Here’s an example of how you might use the REUSE_SYSTEM_DATABASES clause:

CREATE AVAILABILITY GROUP [AG_Example] 
WITH (REUSE_SYSTEM_DATABASES = ON) 
FOR DATABASE [YourDatabase] 
REPLICA ON N'Server1' WITH (ENDPOINT_URL = N'TCP://Server1:5022', 
	FAILOVER_MODE = AUTOMATIC, AVAILABILITY_MODE = SYNCHRONOUS_COMMIT, 
	BACKUP_PRIORITY = 50, SEEDING_MODE = AUTOMATIC);

In this example, the WITH (REUSE_SYSTEM_DATABASES = ON) clause specifies that we want to reuse system databases while creating the Availability Group.


Benefits:

  • Resource Savings: The REUSE_SYSTEM_DATABASES clause allows the reuse of system databases during the creation of the AG, which can save significant time and resources.

  • Simplified AG Creation Process: By reusing system databases, you can simplify the AG creation process, especially in large-scale environments where many AGs need to be created.


Use Cases:

  • Large-Scale Deployments: In large-scale deployments where many AGs need to be created, the REUSE_SYSTEM_DATABASES clause can simplify the AG creation process and save resources.

  • Testing and Development Environments: In testing and development environments where AGs are frequently created and dropped, the REUSE_SYSTEM_DATABASES clause can simplify the management of system databases.


Implications of the New WITH Clauses

The introduction of the CONTAINED and REUSE_SYSTEM_DATABASES clauses in SQL Server’s CREATE AVAILABILITY GROUP command has several implications:

  1. Management of Availability Groups: The management of Availability Groups (AGs) becomes more streamlined with these new clauses. The CONTAINED clause simplifies the management of metadata objects at the AG level, reducing the need for synchronization across replicas. The REUSE_SYSTEM_DATABASES clause simplifies the AG creation process by reusing system databases, which can be particularly beneficial in large-scale deployments.

  2. Performance and Resource Utilization: These changes can impact performance and resource utilization. The CONTAINED clause can improve failover performance by reducing the need to transfer logins and jobs to the new primary replica manually. The REUSE_SYSTEM_DATABASES clause can save significant resources during the AG creation process.


Conclusion

The new WITH clauses in SQL Server’s CREATE AVAILABILITY GROUP command offer enhanced functionality and flexibility. By understanding these features, database administrators can more effectively manage their SQL Server environments and ensure the high availability of their databases. These changes highlight Microsoft’s commitment to continuously improving SQL Server to meet the evolving needs of database administrators and organizations.

コメント


bottom of page