SQL Server Blog

Options
340
SQL-Server-Team on Mar 23 2019 03:03 PM
516
SQL-Server-Team on Mar 23 2019 02:54 PM
333
Ajay_MSFT on Mar 23 2019 02:51 PM
1,441
SQL-Server-Team on Mar 23 2019 02:47 PM
274
SQL-Server-Team on Mar 23 2019 02:46 PM
279
SQL-Server-Team on Mar 23 2019 02:45 PM
257
SQL-Server-Team on Mar 23 2019 02:45 PM
855
SQL-Server-Team on Mar 23 2019 02:45 PM
370
SQL-Server-Team on Mar 23 2019 02:44 PM
397
SQL-Server-Team on Mar 23 2019 02:44 PM
346
SQL-Server-Team on Mar 23 2019 02:41 PM

Latest Comments

You're welcome. Will do @TarynPratt.
0 Likes
@Karl_Wester-Ebbinghaus I appreciate the feedback on this and thanks for reporting what you are seeing. My suggestion would be to open a support request for the issue as they should be able to help and then raise it with the proper team.
1 Likes
Hi @vivek19852225, you need to create the database separately on the primary server add it to the AG and then to perform failover you should do it outside of SSMS as documented here: Manage availability group failover - SQL Server on Linux - SQL Server | Microsoft Learn.
0 Likes
@TarynPratt I have checked it and there is no good way to exclude SQL updates in a maintenance plan. Except one really checks the pending update list in AUM and exclude SQL CU or GDR Update IDs. As I assumed SQL updates will be mostly in security updates or updates category. Unselecting the whole up...
0 Likes
Yeah, double+ agree on the whole "without AG awareness, both are pretty useless". Sounds amazing, but practically I can't use it. Dammit.
2 Likes