We just switched over to 2014 with AG, from SQL 2008. So far, its wonderful, things are running along as usual, but.... (there is always a but) I have this job that calls some rather large MERGE statements to do updates and inserts and it just hangs unless the data movement to the secondary is suspended while it runs. I've already adjusted indexing and made sure the MERGE only works on the records that actually need updating or inserting, but this problem has me scratching my head a bit. In general, would it be better to scrap the existing logic and re tool it with separate update and insert statements?
↧