You could just use SSIS. It can connect to Azure SQL Database and you can move the data that way.

Remember, timeouts are a client-side issue. The problem, most of the time, is likely related to resource contention within SQL Server. But it isn't limited to that. I've seen network...

Uuummmm, did you go and break the thing? Sure looks like the line snapped.

Nope. No fun at all. Especially...

Wow, you guys were seriously chatty kathy while I was gone.

Curse you!

+1 to what Jeff said. It's always great to get the information of what really happened and what the issue was. Thank you!

I agree about the filter on the database id... and disagree. As much as possible you should have it interrupt sooner rather than later to take advantage of the great...

One point. I'm pretty sure duration in extended events is in microseconds. You might want to capture >2000000.

I haven't set this up, but it shouldn't be at all hard. Documentation on the Task Scheduler is here. You'll want to use SQLCMD.EXE. You can just pass in a...

There's no automated mechanism I'm aware of. You gather metrics about query behaviors and over time identify those that are causing you pain. Identify the fact that stats are causing...

Absolutely no silver bullet. That basically looks OK. You may find that statistics updates weekly might be a little light. Depending on the size of your system and the load,...

Thanks for posting back what you ultimately found. So sorry you're going through this nightmare. It can't be fun. Actual malicious actions against a server is not one I've personally...

OK. Then, the other option may be true. You had a one or more very large transactions.

No. Full backups don't control the logs, at all.

Simple recovery, the logs clear all committed transactions at checkpoint. Backups, full or differential (which are all you can do) don't affect...