You could possibly try a row versioning isolation level but it can come with plenty of other issues. Read through the following posts which explains some of the issues and...

Not reliably, no you can't identify that based on the...

BizTalk still uses Failover Clustering and Log Shipping to provide high availability - that's stated in the most recent documentation. They just starting supporting Always On with 2016. Doesn't mean...

That information isn't available when using a database audit. This article has a decent overview of different auditing methods:

Various techniques to audit SQL Server databases

It sounds more like you...

One option is you can view the schema changes and likely easiest way would be to view the Schema Changes History report at the server level - in SSMS, right...

I don't know how much has changed with the version you are going with but you can find information on BizTalk 2016 and Always On using SQL Server 2016. From...

This documentation might give you more of the information you are looking for:

Permissions (Database Engine)

Sue

The per-service SID for the Agent account is a sysadmin. Other than the log reader agent needing sysadmin with certain sync_type options, replication agents don't need to be sysadmins. So...

In this last error, you were attempting an upgrade on the 2014 instance, not sure how that comes into play with migrating a 2008R2 instance to 2017. But in terms...

I would have no idea where you looked from the post and thought that's what you meant by where is the link as my mind reading skills have deteriorated. Try...

I'm not aware of a wizard to create any data warehouse but it sounds like you might be looking for the wizard to create the Management Data Warehouse. That wizard...

If you could find out and post back, that would be great. It helps when others find the same issue that you posted and then they can see how you...

VDI_CLIENT_WORKER is usually created when using automatic seeding. You could try disabling along the lines of:

ALTER AVAILABILITY GROUP YourAGName 
MODIFY REPLICA ON 'NameOfSecondaryReplica'  
WITH (SEEDING_MODE =...

I don't think it's all of the problem but with a scale out deployments, you need to delete all of the keys in the keys table (after backing up the...

There are way too many bugs in SSMS so I can't remember which versions have which issues and they can disappear and reappear in different versions.You can search for them...