Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Availability Group - Core cluster resources switch to being owned by secondary node after windows patching reboots

M
magpie QA Engineer last edited by

Some of our AG clusters (async, manual failover) shift the ownership of their core cluster resources (e.g. cluster IP) from the primary node to the secondary node, which is in a different datacenter, after both nodes are restarted after monthly Windows patching. I can easily switch the resources back to the primary node in Cluster Manager, but is this something I should be worried about, like if the secondary datacenter goes offline? The quorum will still be intact in that case, but is that core cluster IP address relevant to the cluster and AG functioning? Thanks!
Reply Quote 0
1 Reply Last reply
irl last edited by

[...] but is this something I should be worried about, like if the secondary datacenter goes offline?

That entirely depends on the design of the cluster. If there is a scenario where the core cluster resources reside in a location where a network outage between locations would lead to a potential split brain, then yes it would matter. Otherwise, it most likely would not.

The quorum will still be intact in that case, but is that core cluster IP address relevant to the cluster and AG functioning?

The ability to achieve quorum is unknown at this point. The cluster name, which acts as a common administrative endpoint for cluster operations, may be unavailable for a short period of time to regroup the cluster, assuming a whole lot. Really it entirely depends on the design and configuration of the cluster.

In terms of the AG functioning, it requires the cluster. No functioning cluster, no AG. Obviously, any nodes unable to communication will be a problem.
Reply Quote 0
1 Reply Last reply

2
Posts

0
Views

Suggested Topics

K

Availability groups taking time to change states
SQL, Database Testing • network availability groups clustering best prac languagetic lan • • Kadyn

2

0
Votes

2
Posts

0
Views

I created a 2 node AG setup as a POC today and when I tried to do an automatic failover by stopping the sql server service on the primary node ... Just as others have pointed out in the comments section, this isn't a good way of testing as you've nicely and cleanly taken the service down. I mean, it is a great test if your disaster case is "someone shutdown SQL Server nicely", however outside of that it doesn't help much. Having a two-node cluster also isn't very helpful for testing HA (or production) as there are just two possible nodes. While you can argue the usefulness of this setup one way or another based on certain factors, you won't really get to experience AGs until you have 3 or more nodes. This is mainly to do with 2-node clusters being special cases since there are so little resources. ... the one in the secondary went into resolving state and it took a long time for it to become a primary AG. Resolving, in AG terms, means it is trying to find and connect to the primary. Since you've shut it down nicely, it'll take some time (assuming the cluster has quorum and the failover policy has been met) to fail. Does it have to do with networking issues? Nope. I also want to know if it is a good practice to have a separate network interface for the heartbeat network. No such thing as a "heartbeat" network since Windows Server 2008+. The cluster will decide which route to take. What do you really want? If you want to see how long automatic failover takes then you'll first need to figure out what scenarios you'd like to test. Here are some examples: OS Disk fails Cluster partitioning Data disk fails Out of memory Bugcheck log disk fails Overwhelmed disk slow networking windows patching sql patching server power failure You can add more, but for each possible issue there will be a different amount of time it takes. The amount of time is roughly: total = Detection + Mitigation + Redo Queue drain + Undo Each of the above will have different detection and mitigation times, but the redo and undo should be roughly the same for each test. So, at the end of the day, really you're testing detection times. If you only care about how long it takes to do a failover, then run: ALTER AVAILABILIY GROUP MyAG FAILOVER on the new primary. Time it. That's how long it takes.
A

SQL 2012 Availability Group issue - The core cluster resources do not move when we initiate AG fail-over
SQL, Database Testing • availability groups clustering windows server failover • • Anderson

2

0
Votes

2
Posts

0
Views

F

There is no reason to move the cluster core resources. They are NOT part of the availability group and function entirely on their own. There is no need to even have these on the same server as any of your AG resources. The core cluster group provides the administrative point for the cluster which is completely independent from any other resources on the cluster. Leave it migrate on its' own.
K

Issues with Log Shipping in SQL Server 2019
SQL, Database Testing • sql server • • Kadyn

2

0
Votes

2
Posts

0
Views

I had the exact same issue. I installed Cumulative Update 3 for SQL Server 2019 and it went away
J

Sum of all Memory Clerks and Total Server Memory (KB)
SQL, Database Testing • sql server performance memory buffer pool performanc languagee c la • • jules

2

0
Votes

2
Posts

0
Views

R

Max Server Memory for SQL Server 2019 = Buffer Pool Memory + Non-Buffer Pool Memory. No, some part of memory allocation for SQL Server 2019 can be done outside of max server memory like ( I would quote from Memory Management Architecture Guide) Memory for thread stacks1, CLR2, extended procedure .dll files, the OLE DB providers referenced by distributed queries, automation objects referenced in Transact-SQL statements, and any memory allocated by a non SQL Server DLL are not controlled by max server memory. So you can see some part of memory is allocated outside max server memory so your equation does not always holds true. Total Server Memory (KB) - The committed memory from the Buffer Pool. Yes that is the memory committed using memory manager. Data Cache Memory (KB) performance counter is equivalent to MEMORYCLERK_SQLBUFFERPOOL memory clerk and both represents data cache used size. No, buffer pool is much bigger, Data cache is subset of it. If Total Server Memeory (KB) is related to Buffer Pool memory, then why its size (32262 MB) is bigger than Total sum memory clerks altogether (23523 MB) which represents both Buffer Poll Memory and Non-Buffer Pool Memory? Total server memory includes basically memory used by SQL Server which is almost 31 GB and this will be bigger than sum of the clerks, which is basically 22 GB, because memory clerks do not capture all memory allocations within SQL Server ( They do most of it however). Let me know if you have further questions.
A

Problem reading data from secondary when reorganizing clustered index
SQL, Database Testing • sql server sql server 2014 availability groups index maintenanc language • • Amritpal

2

0
Votes

2
Posts

0
Views

So, after running out of possible solutions we opened a support case to Microsoft. They asked to run a tool to gather some info while the process was running and afterwards they analyzed it. Here is their answer: You select command is running fine if it starts before reorganize index job is initiated Select command is failing if it starts after re-organize job is initiated. Found the above behavior is expected behavior in AG. Even though the read operations do not take shared locks because of row versioning, these operations take schema stability (Sch-S) locks, which can block redo operations that are applying DDL changes. DDL operations include ALTER/DROP tables and Views but not DROP or ALTER of stored procedures. In our case while re-organize index is running on primary redo operation for the same is being performed on secondary replica and is acquiring Sch-M (Schema modification locks), when select command is trying to access the same replica it is not able to acquire Sch-S (Schema Stability) locks as it is already occupied by redo thread which is having Sch-M locks. In this scenario your application is generating errors including time out errors. To avoid this kind of situations it is recommended to schedule re-organize index task in off business hours We don't have "off business hours", we run 24/7/365. Is not a definitive answer, but at least we know the root cause of this issue. So the approach will be to temporarily change connection string so the task that is failing will read from primary AG node instead of secondary AG node the day the reindex run.
G

AlwaysOn AG: Current Host Server - Owner Node - Primary Instance
SQL, Database Testing • sql server availability groups clustering • • gionna

2

0
Votes

2
Posts

0
Views

E

Should the "Current Host Server" the same as the Owner Node of the AlwaysOn AG? That's the node that is currently hosting the core cluster resources, it isn't the same and is just another role. Different roles can be owned by different nodes. In this case, they do not need to be the same - and generally most people don't care who owns the core cluster resources in a WSFC that only has SQL Server. It does make a difference in certain situations but for the vast majority, it makes no real difference. Imagine if I want to maintain a host. Shall I first failover the AG (via SSMS or with ALTER AVAILABILITY GROUP...) to the second node/another node and at second a failover of the WSFC-Current Host? If you're going to be maintenance to a host, I'd move all roles (drain) off of that node. So, yes, everything should be moved from it.
J

Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?
SQL, Database Testing • sql server sql server 2008 • • jonetta

2

0
Votes

2
Posts

0
Views

SQL Server doesn't support a multi-column IN clause (unlike Oracle). delete from constitue where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers This can be rewritten as a EXISTS: DELETE c FROM constitue c WHERE EXISTS (SELECT 1 FROM @num_dossiers nd WHERE n.num_dossier = c.num_dossier AND n.indice = c.indice);
K

What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
SQL, Database Testing • sql server loc languageking • • Kadyn

2

0
Votes

2
Posts

0
Views

E

From what I remember about this database from your earlier questions, I'd suggest you look at these alternatives to your approach: Consider RCSI or Snapshot isolation. This will prevent your select queries being blocked during the update. Be mindful of the increased usage of tempdb this can generate but IIRC the nature of your database/data should mean this is small. Updating the points record in batches, rather than one almighty transaction for the entire table. See How to Use Batch Size to Speed Mass Updates, Inserts and Deletes for an old (but still relevant) approach.
K

Scripting a maintenance plan
SQL, Database Testing • sql server sql server 2008 r2 maintenanc languagee plan • • kalyn

2

0
Votes

2
Posts

0
Views

C

When you create job using maintenance plan, a job is automatically created in SQL Server Agent under Jobs. So now go to SQL Server Agent, expand jobs, and look for your job. Right click on it and select Script job as... Drop and recreate to... New query editor window. Edit: You can export the maintenance plans as well. You need to connect to Integration Services of the instance. Expand the stored packages then MSDB then expand Maintenance plans. Right click on MP and select a export package. Then you can move the package to another SQL Server.
A

Availability groups NIC best practices
SQL, Database Testing • sql server network availability groups configuration best prac languagetic lan • • authera

2

0
Votes

2
Posts

0
Views

can I have 2 heartbeat networks between the nodes for redundancy The whole setup will be virtualized. I'm assuming you're going to bind these directly to the hardware NICs, otherwise it's kind of a moot point. If the host already has the NICs teamed, etc., then you really shouldn't need multiple interfaces in your guest (except for management or performance reasons, but not for health check reasons). Cluster health checks go over any interface you allow cluster communication on (the public/private nomenclature died with Windows Server 2003). NetFT will take care of which interfaces are what and the metrics for each, adding additional interfaces wouldn't really be ideal. Instead use teaming or other technologies to make sure the interfaces stay up and available. Setting the client network for client and cluster communication will also do what you're asking without the need for extra interfaces. Edit: Unless you need to segregate traffic, such as the AG traffic for specific reasons such as NICs of higher speeds, network appliance between (compression/encryption), auditing needs, network protections, different virtual switches, etc., then there isn't really a need. If you meet one of these items, then it would make sense to have multiple NICs. Having a single NIC may require you to make changes to the host configs to have larger receive or send buffers.
E

Scheduling backup jobs for an Availability Group
SQL, Database Testing • backup sql server 2014 availability groups • • elysha

2

0
Votes

2
Posts

0
Views

C

In a MS SQL Server 2014 AlwaysOn AG setup, I would like to schedule backup jobs for a given availability group. The ultimate goal is to have the regular backups run on the synchronized secondary and, most importantly, not bound to the availability of a particular secondary node. This can be accomplished without issue. Just keep in mind that your systems should be spec'd to be able to take the full load of the synchronization mechanics for AlwaysOn Availability Groups, plus the redo needed, plus the backups. The last thing that you want is to overwhelm your IO system and cause outages or a large redo queue. This is assuming it's not actively being used as a readable secondary - if it is, you'll want to factor that in and watch for blocked redo threads. 1.I want to run the scheduled action on a secondary just once, but I have multiple secondaries 2.I want to ensure that it is ultimately run, regardless if there are any secondaries left at all - if no secondaries are left, it should run on the primary There is an Availability Group setting and a system function that can be used in order to accomplish this within your expected guidelines. The first is the setting, per AG, called AUTOMATED_BACKUP_PREFERENCE which has four different options. The one you're describing is called SECONDARY which will prefer any secondary node over the primary node. The secondary node chosen is by the BACKUP_PRIORITY which is set per replica ranging from 0-100, where the higher the number the more weight it has. If there is a tie in weights for secondary replicas, the replica that is sorted first given the system collation will be chosen. If all secondary replicas should fail, the primary replica will be chosen. The second part of the equation is the system function used to check if the replica that is running the job is the preferred replica based on the values in the previous paragraph. This system function is called sys.fn_hadr_backup_is_preferred_replica(). Given a database name (any database in the AG) a value of 0 will be returned if it is not the preferred replica and a value of 1 if it is preferred. When creating the agent job to accomplish this, you'll want to wrap the backup logic in an IF conditional to check for the preferred replica. That's it. Put the identical agent job on all replicas. Please be sure to test that this truly is what you want and expect.
R

MS SQL Server 2016 SP3 upgrade failing
SQL, Database Testing • sql server sql server 2016 service pack • • Raziyah00

2

0
Votes

2
Posts

0
Views

R

After trying several things, finally this worked for me: I renamed the existing C:\Temp folder to C:\Temp_old and created a new Temp folder in the C drive.
C

Zombie Sql Server DB on Secondary Replica is both in and out of an Availability Group
SQL, Database Testing • sql server 2012 availability groups • • Cleofas

2

0
Votes

2
Posts

0
Views

A

I pulled the oldest full backup I could find and was able to restore that over the Restoring db using: RESTORE DATABASE [ZOMBIEDB] FROM DISK = N'D:\ZOMBIEDB.bak' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 5 I was then able to delete the restored database.
A

SQL Cluster Resources Disappear After Removing Disk Resource
SQL, Database Testing • sql server 2008 r2 clustering • • amarantha

2

0
Votes

2
Posts

0
Views

The link below has the likely answer. Premier Support agrees that the steps to fix should fix my similar issue. I plan on going through the steps during my next outage window. http://blogs.technet.com/b/askcore/archive/2013/01/14/removing-a-mount-point-disk-from-a-cluster-group.aspx
K

Cannot remove filegroup with no files associated
SQL, Database Testing • sql server sql server 2017 filegroups • • kalyn

2

0
Votes

2
Posts

0
Views

A

Double-Checking Filegroups in Database Verify that the filegroup does not have any files left attached by issuing the following command: use [DB] go sp_helpfilegroup This will produce a list of filegroups: groupname | groupid | filecount -----------+---------+----------- PRIMARY | 1 | 1 xyz | 2 | 1 ...and then for each filegroup listed execute use [DB] go sp_helpfilegroup @filegroupname='PRIMARY' go sp_helpfilegroup @filegroupname='xyz' The output might look like this: groupname | groupid | filecount -----------+---------+------------ xyz | 2 | 1 ....and the second output might be: file_in_group | fileid | filename | size | maxsize | growth ------------------+--------+-----------------------------------+---------+-----------+--------- xyz_logical_name | 3 | X:\SQL\SQL_DATA\xyz_filegroup.ndf | 5120 KB | Unlimited | 1024 KB Deleting the Filegroup If you still have a file associated with one of your filegroups, then the complete command to delete the filegroup's logical file and the filegroup itself would be: USE [DB] GO ALTER DATABASE [DB] REMOVE FILE [xyz_logical_name] GO ALTER DATABASE [DB] REMOVE FILEGROUP [xyz] GO Filegroup 'xyz' Is Default If you receive an error message when trying to remove the filegroup's logical file that looks like this: Msg 5031, Level 16, State 1, Line 88 Cannot remove the file 'xyz_logical_name' because it is the only file in the DEFAULT filegroup. ...then you will have to set the PRIMARY filegroup as the DEFAULT filegroup: ALTER DATABASE [DB] MODIFY FILEGROUP [PRIMARY] DEFAULT Filegroup 'xyz' Is ReadOnly However, if the error message is the following: Msg 5055, Level 16, State 2, Line 88 Cannot add, remove, or modify file 'xyz_logical_name'. The file is read-only. ... then you will have to remove the READ_ONLY property on the xyz filegroup: ALTER DATABASE [DB] MODIFY FILEGROUP [xyz] READWRITE You should now be able to drop the filegroup's logical file and the filegroup itself. Open Transactions If you really don't have a file (logical_name / pyhsical_file_name) associated with the filegroup xyz you are trying to delete, then performing a transaction log backup might release any transactions hindering further deletion of the filegroup. Dial 911 If all else fails, you might want to consider opening a call with Microsoft. Metadata Mismatch Added after further research Apparently there are cases when the metadata in the database does not reflect the actual location of the objects. Reference: - FIX: Metadata inconsistency error after you switch table partitions and drop corresponding files and filegroups (Microsoft Support) - FIX: Error occurs when you try to drop or delete filegroups or partition schemes and functions in SQL Server (Microsoft Support) These two cases seem to been resolved with Cumulative Update 3 for SQL Server 2014 SP1 and Cumulative Update 1 for SQL Server 2016 respectively. They don't apply to your situation, but they show that sometimes the metadata can be wrong. The item that seems to be blocking your filegroup deletion is the index, which might be stored with wrong meta-data. Possible Solution Consider rebuilding the index Ref90159CCC which is referenced in the error message. Cannot process rowset ID 72057594712162304 of object "STORY_TRANSLATIONSCCC" (ID 120387498), index "Ref90159CCC" (ID 2), because it resides on filegroup "CCC_APPLICATION_new" (ID 8), which was not checked. The following article describes a similar situation and show how the author detected the culprit and resolved the situation. Reference: SQL Server: switch partition and metadata inconsistency issue (Blog dbi-services.com) Find Objects Related to Obsolete Filegroup I rigged up this script to check as much possible hiding places for tables/indexes/partitions/etc. that could be still relating to the dropped filegroup file: Please replace DEFAULTRO with the name of your obsolete filegroup (e.g. CCC_APPLICATION) /* ================================================================== Author......: hot2use Date........: 16.02.2018 Version.....: 0.1 Server......: LOCALHOST (first created for) Database....: StackExchange Owner.......: - Table.......: - Type........: Script Name........: ADMIN_Filegroup_Statement_All_Objects.sql Description.: Checks all objects related to filegroups based on the ............ relationship between the data_space_id ID. ............ History.....: 0.1 h2u First created ............ ............ ================================================================== */ DECLARE @nvObsoleteFG AS NVARCHAR(50) SET @nvObsoleteFG = N'DEFAULTRO' SELECT -- DISTINCT use in conjunction with sys.allocation_units table and objects '-->' AS DataSpaceNfo ,ds.name AS DataSpaceName ,ds.data_space_id AS DatSpacID_DataSpace ,'-->' AS FileGroupNfo ,f.name AS FileGrpName ,f.data_space_id AS DatSpacID_FileGrp ,f.[type] AS FileGrpType ,'-->' AS DataBaseFilesNfo ,df.data_space_id AS DatSpacID_DBFiles ,df.[type] AS DBFilesType ,df.name AS DBFilesName ,'-->' AS ObjectNfo ,o.[object_id] AS OjbID ,o.name AS ObjName4HeapsClusters ,o.type_desc AS ObjTypeDesc ,'-->' AS IndexNfo ,i.name AS ObjName4Indexes ,i.type_desc AS IndTypeDesc ,i.[object_id] AS IndObjID ,i.index_id AS IndIndID ,'-->' AS PartSchemaNfo ,ps.name AS PartSchemaName ,ps.data_space_id AS DatSpacID_PartSchema -- ,au.type_desc AS AllocUnitTypeDesc -- ,au.data_space_id AS DatSpacID_AllocUnit FROM sys.data_spaces AS ds FULL JOIN sys.filegroups AS f ON ds.data_space_id = f.data_space_id FULL JOIN sys.database_files AS df ON f.data_space_id = df.data_space_id FULL JOIN sys.indexes AS i ON f.data_space_id = i.data_space_id FULL JOIN sys.partition_schemes AS ps ON f.data_space_id = ps.data_space_id FULL JOIN sys.objects AS o ON i.[object_id] = o.[object_id] -- FULL JOIN sys.allocation_units AS au -- ON au.data_space_id = f.data_space_id -- If you omit the whole WHERE clause you get an overview of everything (incl. MS objects) WHERE o.is_ms_shipped = 0 -- if you omit the lower AND you'll get all items related to all filegroups AND ( df.data_space_id=( SELECT data_space_id FROM sys.filegroups WHERE NAME = @nvObsoleteFG ) OR f.data_space_id=( SELECT data_space_id FROM sys.filegroups WHERE NAME = @nvObsoleteFG ) OR df.data_space_id=( SELECT data_space_id FROM sys.filegroups WHERE NAME = @nvObsoleteFG ) OR ps.data_space_id=( SELECT data_space_id FROM sys.filegroups WHERE NAME = @nvObsoleteFG ) ) Reference: My personal script Run it and see if any objects are displayed containing your obsolete filegroup. Go with the data_space_id rather than with the name. The joins are intentionally FULL to catch any "orphaned" references. Alternatively use this smaller script to quick check for items in the obsolete filegroup: SELECT o.[name] ,o.[type] ,i.[name] ,i.[index_id] ,f.[name] FROM sys.indexes i INNER JOIN sys.filegroups f ON i.data_space_id = f.data_space_id INNER JOIN sys.all_objects o ON i.[object_id] = o.[object_id] WHERE i.data_space_id = f.data_space_id AND o.type = 'U' -- User Created Tables Reference: SQL SERVER – List All Objects Created on All Filegroups in Database (SQLAuthority.com)

Availability Group - Core cluster resources switch to being owned by secondary node after windows patching reboots

Suggested Topics

Availability groups taking time to change states SQL, Database Testing • network availability groups clustering best prac languagetic lan • • Kadyn

SQL 2012 Availability Group issue - The core cluster resources do not move when we initiate AG fail-over SQL, Database Testing • availability groups clustering windows server failover • • Anderson

Issues with Log Shipping in SQL Server 2019 SQL, Database Testing • sql server • • Kadyn

Sum of all Memory Clerks and Total Server Memory (KB) SQL, Database Testing • sql server performance memory buffer pool performanc languagee c la • • jules

Problem reading data from secondary when reorganizing clustered index SQL, Database Testing • sql server sql server 2014 availability groups index maintenanc language • • Amritpal

AlwaysOn AG: Current Host Server - Owner Node - Primary Instance SQL, Database Testing • sql server availability groups clustering • • gionna

Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request? SQL, Database Testing • sql server sql server 2008 • • jonetta

What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table? SQL, Database Testing • sql server loc languageking • • Kadyn

Scripting a maintenance plan SQL, Database Testing • sql server sql server 2008 r2 maintenanc languagee plan • • kalyn

Availability groups NIC best practices SQL, Database Testing • sql server network availability groups configuration best prac languagetic lan • • authera

Scheduling backup jobs for an Availability Group SQL, Database Testing • backup sql server 2014 availability groups • • elysha

MS SQL Server 2016 SP3 upgrade failing SQL, Database Testing • sql server sql server 2016 service pack • • Raziyah00

Zombie Sql Server DB on Secondary Replica is both in and out of an Availability Group SQL, Database Testing • sql server 2012 availability groups • • Cleofas

SQL Cluster Resources Disappear After Removing Disk Resource SQL, Database Testing • sql server 2008 r2 clustering • • amarantha

Cannot remove filegroup with no files associated SQL, Database Testing • sql server sql server 2017 filegroups • • kalyn

Availability groups taking time to change states
SQL, Database Testing • network availability groups clustering best prac languagetic lan • • Kadyn

SQL 2012 Availability Group issue - The core cluster resources do not move when we initiate AG fail-over
SQL, Database Testing • availability groups clustering windows server failover • • Anderson

Issues with Log Shipping in SQL Server 2019
SQL, Database Testing • sql server • • Kadyn

Sum of all Memory Clerks and Total Server Memory (KB)
SQL, Database Testing • sql server performance memory buffer pool performanc languagee c la • • jules

Problem reading data from secondary when reorganizing clustered index
SQL, Database Testing • sql server sql server 2014 availability groups index maintenanc language • • Amritpal

AlwaysOn AG: Current Host Server - Owner Node - Primary Instance
SQL, Database Testing • sql server availability groups clustering • • gionna

Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?
SQL, Database Testing • sql server sql server 2008 • • jonetta

What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
SQL, Database Testing • sql server loc languageking • • Kadyn

Scripting a maintenance plan
SQL, Database Testing • sql server sql server 2008 r2 maintenanc languagee plan • • kalyn

Availability groups NIC best practices
SQL, Database Testing • sql server network availability groups configuration best prac languagetic lan • • authera

Scheduling backup jobs for an Availability Group
SQL, Database Testing • backup sql server 2014 availability groups • • elysha

MS SQL Server 2016 SP3 upgrade failing
SQL, Database Testing • sql server sql server 2016 service pack • • Raziyah00

Zombie Sql Server DB on Secondary Replica is both in and out of an Availability Group
SQL, Database Testing • sql server 2012 availability groups • • Cleofas

SQL Cluster Resources Disappear After Removing Disk Resource
SQL, Database Testing • sql server 2008 r2 clustering • • amarantha

Cannot remove filegroup with no files associated
SQL, Database Testing • sql server sql server 2017 filegroups • • kalyn