If you're using Azure SQL Database I'd look into the COPY DATABASE command in Powershell. That's going to let you capture a quiet copy of the database and then you...

Look through the system views and you ought to be able to figure it all out. sys.dm_exec_query_stats has a number of values like sql_handle for finding statements and the plan_handle...

So, automatically killing long running queries or queries that are blocking is a very bad idea. Can it be done? Certainly. There are a number of ways you could do...

Or, since we're talking 2016, there's always:
ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE CACHE
However, same rules apply. Don't do this in production.
You can also try using...

If all the data has to be returned all the time, the only way to speed that up is to spend lots and lots of money on hardware. There is...

You have an 8gb server (half my laptop by the way) and a query that moves ALL the data. How big is this database? If you're moving all the data...

It would be a lot easier to give you detailed answers with example queries, structure, and execution plans for the existing queries you're running. Otherwise, we're making guesses here.

Are you in an Azure Virtual Machine (in which case, it's just Windows & SQL Server and should behave the same as a local instance of SQL Server) or are...

100% agreement with Joe. You should be following best practices and writing the code correctly including object ownership. However, Azure SQL Database is SQL Server. If you have a valid...

The way I'd do it is to create a copy of the production database, then export that to a BACPAC. The reason to do two steps is because the BACPAC...

Agree with everything Lynn said. Emphasizing, this:

December 13, 2018 at 2:04 am

#2016197

That's a lot of down time. Doing a side-by-side install  would allow you to set up mirroring to migrate between the servers minimizing downtime. Further, that method means that you...