Kevins's answer is great (+1).

We did have a 3 second standard that all queries had to meet. However, as Kevin notes, that doesn't mean that if a query...

That's no good. You're basically talking merge replication here. It's a nightmare. You'll need to move to VMs and you'll have to completely redesign and rebuild your databases. Or, you...

Sorry I couldn't help. I just can't replicate the issue. Going to Microsoft is probably the best guess right now.

Read this overview article. The primary purpose is absolutely for failover and continuity. However:

Another key benefit is that the secondary databases are readable and can be...

If CONVERT doesn't work, then the data may not be of the type you think it is, or, it could be encrypted. Just guessing since we can't see what's going...

It's not data pools. That's a way of managing and paying for Azure SQL Database, not something like the Data Lake (completely, utterly different technology), which is distributed storage. Within...

to put a secondary in the same data center, you have to create a second server. That server is the connection string you would use. Putting a secondary in other...

Tried editing again. There are no duplicate lines in the original text it's something in the formatter.

I wouldn't say it's better. It's different. Easier for one thing. The first question is, can you work within the Platform as a Service offering of Azure SQL Database? If...

I've sent a message to someone who works for them. Hopefully you can get some help.

If it's Azure SQL Database, no, setting up VMs is a bad choice. You want to take advantage of Geo-Replication. That's designed for exactly what you're looking for. If you...

But wait. What happens when my stool only has two...

If you do a web search for Extended Events, the first or second link is usually the "Getting Started" documentation from Microsoft. That's the best way to get started.