Sfrgttk

Venezuelan girlfriend wants to travel the USA to be with me. What is the process?

What does “the session was packed” mean in this context?

How much of data wrangling is a data scientist's job?

Why didn't Boeing produce its own regional jet?

How badly should I try to prevent a user from XSSing themselves?

Can I run a new neutral wire to repair a broken circuit?

I would say: "You are another teacher", but she is a woman and I am a man

Cursor Replacement for Newbies

Could the museum Saturn V's be refitted for one more flight?

How to show a landlord what we have in savings?

How do conventional missiles fly?

Is there an expression that means doing something right before you will need it rather than doing it in case you might need it?

What are some good books on Machine Learning and AI like Krugman, Wells and Graddy's "Essentials of Economics"

Forgetting the musical notes while performing in concert

If human space travel is limited by the G force vulnerability, is there a way to counter G forces?

Ambiguity in the definition of entropy

What about the virus in 12 Monkeys?

iPad being using in wall mount battery swollen

What exploit Are these user agents trying to use?

Which is the best way to check return result?

What mechanic is there to disable a threat instead of killing it?

Expand and Contract

Do scales need to be in alphabetical order?

Are there any examples of a variable being normally distributed that is *not* due to the Central Limit Theorem?

Monitoring Maintenance Tasks in AlwaysOn Clusters

Availability Group configuration & licencingAlwaysOn AG, DTC with failoverDoes failed task considered to be run to completion in SQL Server maintenance plan terminology?Failover Cluster and AlwaysOn Availability Groups across Data CentersManual Failover with AlwaysOn availability groupScheduling index rebuild jobsAlways On Listener Behavior - DBs removed from groupAlwaysOn - Running SQL Agent Jobs on Secondary read-only node writing audit information to databaseBackups with Split Availability GroupsLoad balancing Availability groups with SQL Server Standard

0

I have an environment with multiple AGs on a single server and they encounter a split situation in which some end up on one node and some end up on the other node (in a failover event, perhaps). When maintenance tasks (the basic gamut of reindexing, update, etc.) execute on these nodes, they will only effectively perform operations on databases which are read_write on the primary side of their respective AGs. This causes the job to fail since the databases are read_only on the secondaries. Therefore, in a split AG situation, both nodes will always show failed maintenance in the job history.

Needless to say, it is difficult to monitor these clusters. I have proposed two possible solutions to management. We either script the maintenance tasks using DBCC commands for the individual databases based on their updateability properties, or we simply limit ourselves to one AG per server. They don't like either solution. Does anyone know of a way I can keep the built-in SQL Server maintenance tasks and have them target only the primary databases?

availability-groups maintenance monitoring

share

asked 5 mins ago

Aaron RheamsAaron Rheams

514

add a comment | 

0

I have an environment with multiple AGs on a single server and they encounter a split situation in which some end up on one node and some end up on the other node (in a failover event, perhaps). When maintenance tasks (the basic gamut of reindexing, update, etc.) execute on these nodes, they will only effectively perform operations on databases which are read_write on the primary side of their respective AGs. This causes the job to fail since the databases are read_only on the secondaries. Therefore, in a split AG situation, both nodes will always show failed maintenance in the job history.

Needless to say, it is difficult to monitor these clusters. I have proposed two possible solutions to management. We either script the maintenance tasks using DBCC commands for the individual databases based on their updateability properties, or we simply limit ourselves to one AG per server. They don't like either solution. Does anyone know of a way I can keep the built-in SQL Server maintenance tasks and have them target only the primary databases?

availability-groups maintenance monitoring

share

asked 5 mins ago

Aaron RheamsAaron Rheams

514

add a comment | 

I have an environment with multiple AGs on a single server and they encounter a split situation in which some end up on one node and some end up on the other node (in a failover event, perhaps). When maintenance tasks (the basic gamut of reindexing, update, etc.) execute on these nodes, they will only effectively perform operations on databases which are read_write on the primary side of their respective AGs. This causes the job to fail since the databases are read_only on the secondaries. Therefore, in a split AG situation, both nodes will always show failed maintenance in the job history.

Needless to say, it is difficult to monitor these clusters. I have proposed two possible solutions to management. We either script the maintenance tasks using DBCC commands for the individual databases based on their updateability properties, or we simply limit ourselves to one AG per server. They don't like either solution. Does anyone know of a way I can keep the built-in SQL Server maintenance tasks and have them target only the primary databases?

availability-groups maintenance monitoring

share

asked 5 mins ago

Aaron RheamsAaron Rheams

514

share

asked 5 mins ago

Aaron RheamsAaron Rheams

514

share

asked 5 mins ago

Aaron RheamsAaron Rheams

514

asked 5 mins ago

Aaron RheamsAaron Rheams

514

asked 5 mins ago

Aaron RheamsAaron Rheams

514