Merge replication may work. Depends on how different the tables are and if they meet the requirements for merge replciation.

Otherwise, I'd go with service broker.

If you are doing large batch operations, you should optimize the operation by figuring out ways to get rid of complex criteria and joins so that you are not taking...

Transactions commit on the secondary in the exact same order as the primary. If you were using read committed isolation, it would still suffer from gaps due to transactions completing...

Did you mean to say READ UNCOMMITTED? Read Committed would have the same issue as Snapshot.

Yes, no other change, and it only ever affected those 3 installs. Have heard of others that have experienced it once and fixed by reinstalling.

Sounds like an issue I ran into with some new installs on Windows 2012 (not R2) last year. Config Manager and many other things could write to the registry but...

No, there needs to be a maintenance job to delete old backups (older than your SLA for keeping data on-hand).

If you want, there is one a script you can use...

First of all, let's get the terms right to avoid confusion. A "transaction log" or "log file" is one of the database files. You are talking about "log backups" which...

Sounds like a simple case of confusing correlation with causation. Or it didn't happen. Those ar ethe only 2 possible answers. You do not get permissions for one login path...

You're overthinking it. When the user logs in, they have a superset of all permissions for all of their login paths. They don't log in as one path or the...

Are the instances sharing the same db file and log file drives? What about tempdb files? If so, that could definitely cause contention on the other instance.

You said one of them is virtual. As in a VM on the physical machine?

It didn't unless you have something configured poorly like all the database files and the VM...

No. And don't detach the database ever unless you a good reason to (this isn't one).

The answer is, don't do large bulk processes. Delete/update in batches.

Please start a new thread. Don't piggyback. </etiquette lesson>

If I'm understanding you correctly, you can use the built-in function SUSER_SID() to verify if the account exist. If it returns NULL, it doesn't exist:

Declare @User nvarchar(256) = N'SQLMCMLap\TestUser',