Share via

Issues after implementing MS SQL Server Always On

Srikanth Palatla 0 Reputation points
2023-12-09T09:07:05.4166667+00:00

We have implemented the MS SQL Server Always On. Further, we are now encountering the following issues.

Issue details

  1. SQL Trigger is getting disabled daily on a table.
  2. Always On databases are going in a resolving state frequently.
SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator
    2023-12-09T11:04:01.3066667+00:00

    If a DML trigger is disabled, that is because someone of something is disabling it. But that has nothing to do with an availability group.

    If you databases get into resolving state frequently, your setup of the AG may not match with the level of monitoring you are putting into the AG. Keep in mind that Availability Groups is quite an advanced feature, and if you don't have the skillset to handle, the effect of it may be the opposite of what you wanted to achieve. That is, you get more downtime, when you wanted less. Lest, you think that I'm picking on you, I don't think I'm very qualified to run an AG in production myself. (I mainly work in a developer role, and not as a DBA.)

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.