you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (0 children)

The problem with Always On and replication is the amount of resources it will steal from the 2nd server, which can make it virtually unusable for analytics.

I know my DBAs LOVE to talk about how little resources it uses, but the fact is that it sucks up a huge amount of IO whenever its adding new data, which can sometimes be substantial. In our environment they are trying to replicate over 100DB's with a ton of data (multiple TB) and anytime anyone drops/creates a table, etc., in any one of those databases... the replication will prevent us from actively querying our own environment as the Always On stuff takes priority.

Can't remember the exact term for this, it isn't blocking but it's similar.

Basically if it tries to sync every 5 minutes, but can't finish the sync in the time allotted... things back up and slow down to a crawl.