Just don't forget integer values run out at about 2.1 billion. We're running into that now on some primary key=integer identity columns and having to change to bigInt (...

Thanks. Now instead of the ORM-generated query looking vaguely awful, it is crystal-clear awful. It ran for 30 minutes in prod this morning before I had to leave...

thanks

Yes it's there under keys and in your query results. So apparently I can disable the unused index and the constraint ( key ) remains in force.

name ...

Here is what much of our ORM code is based off of:

[/url] The author used to work for us but apparently hasn't updated it in...

This query could run as much as 15 minutes before. I attached the plan above, I thought, but again for this post.

Regarding the modifications Lynn Pettis made to the OP query. I attached the plan.

------LYNN PETTIS CHANGE

-- 92 rows in QA in 03:29 first run 10 seconds...

You can try the attached SqlCleaner. It was written a few years ago and definitely depends on the command starting with exec sp_executesql N'SELECT yada yada...

SoHelpMeCodd and David Poole: yes yes yes, exactly.

Lots of select distincts, usually combined with TOP. IN statements with 50+ elements. Parameters declared at string length. I've...

Yes ORM-generated sql. Ours is a version called Domain Objects written by a former developer here. Others include Entity Framework and Hibernate. That sql code was...

Development is considering all options. The SSD thing was just to buy them some time.

In the meantime I may take a couple of the worst queries ( combined OLTP/OLAP...

Great article this is exactly the boat we are in now that the database is large 6 TB ....things are starting to grind to a halt so we're going to...

Thanks Lynn I'll give it a run

hijacked thread 🙂

Why would SSDs generate deadlocks?