![]() To grant that permission you have to execute the following T-SQL statement after you have joined the Availability Group on the secondary:ĪLTER AVAILABILITY GROUP GRANT CREATE ANY DATABASE ![]() One of the biggest challenges is that the Availability Group on a newly added secondary needs appropriate permissions to be able to create the database(s) that are afterwards seeded from the primary replica. Up to now everything sounds quite interesting and promising, but there are a few possible problems that can (or even will) arise in combination with Automatic Seeding. You just watch, you relax, and you are able to enjoy a coffee in the mean time until SQL Server has done its job! Automatic Seeding – possible problems ![]() Imagine the effort you are saving when you have an Availability Group with 9 replicas, and you want to add a new database into the Availability Group: with Automatic Seeding you don’t need to do anything, because SQL Server itself automatically seeds the newly added database across each replica automatically. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |