Also, look up Ola Hollengren's scripts for backups. They'll serve you well.

Have you ever encountered some code that makes you feel that you need wine instead of coffee to fix it? Or is it just me? I'm working on a...

Since you're not at liberty to share the queries - the only input I would have is - eat the elephant one bite a t a time.  The one...

Wait. Managed instance is different. They want that to be a lift & shift location. You can run a restore there. That's different than Azure SQL Database.

Reading execution plans is fairly complicated. Follow the link below, or look it up online to find a free book I wrote on the topic. Work tables aren't bad (or...

There's going to be work for data professionals for a VERY long time to come. That work will shift and change, as it already has. So yeah, it's a fine...

Can you post the rest of the code? If it says parameter has been defined, that means you're defining a parameter, but we can't see that in what you posted.

You can't.

You can use migration to replace it. You can use Azure Sync, but you have to set that up and program it. You can use something like Redgate Data...

Ignoring them might be valid. To check the wait statistics, run a query against sys.dm_os_wait_stats. That's in all versions of SQL Server from 2005 & up (although, Azure SQL Database...

I'd lean heavily towards this being overkill. Sure, queries on the one database don't interfere directly with the queries on the other. However, the resource contention is just as large...

It is. You can use UNION ALL and then run the same count against each view.

Easier question first, sure you can ignore the peaks... with the understanding that you'll see slow behavior, blocking, locking, and resource contention when you're trying to access memory & cpu...

If you want to understand why things are slow, get the execution plan and evaluate what is happening there. If you want us to help, share the execution plan. By...

Combining views, nesting views, and taking large, large data sets without filtering through views, are very common code smells that inevitably lead to trouble. Because views act like tables within...

Hard to explain exactly what happened, but it's likely to be the network. It's good to measure some queries from the client to understand how your network behaves, but the...