Thanks Grant,

Thanks for the help.

On thing that jumps out on the waits is LCK_M_SCH_S with with a average wait of 119 secs. I have noticed that the...

Hi Grant,

Thanks for this. Think blocking is the most probable, and have set up an XE to catch something next time..

We are using Redgate and a...

Hi Phil, Steve

I have imported everything successfully, but because of the Circular reference problem I am not able to build the solution. I have started with the biggest...

Thanks for this!

Without the log chain, only option might be to somehow get access to the corrupted database.  Can you start the corrupted database in emergency mode? You might be able to...

You can use a utility like sqlstress to simulate a workload. See brent's article (https://www.brentozar.com/archive/2015/05/how-to-fake-load-tests-with-sqlquerystress/) for more thorough description. Also, rather use extended events to capture events rather than...

Sorry, My mistake. Most of the databases have been converted to 2014 and we are in the process of moving everything over.

Hi Thom,

Thanks for this. Yes this was old legacy 2000 databases! Will explain this then. 

Thanks for the help.

May 10, 2018 at 7:17 am

#1990031

Jeff.. What I did in the end was to set the database to simple and immediately did a DBCC shrinkfile of the log files before it reverted back to...

Thom, Erikur,  Thanks for the help.. Understand a bit more how AWS works.. thanks.. The problem was that the log was growing to a few gig (log_Reuse_Wait_description = https://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html

I think the "Distinct" stinks..

Try to rewriting the query using aggregate functions instead

You need to look at the query plan..

I have a personal pet hate using the Distinct keyword....

SQL will allocate to the different files using a round robin and proportional fill algorithm, so L will be hit more.

To even them out you could do a CREATE INDEX...

There might also be a hidden update trigger on the table affecting the results?