Look at the join criteria within the details of the operator and see what the likely output from that is, based on the statistics provided. Additionally, see if there are...

Probably your best bet is to export the database to flat files. You could try reading from the tables into another database too. Otherwise, you may be down to trying...

1. I'm sure with some work, I could find exceptions, but the overall rule is easy here, statistics updates are radically less resource intensive than index rebuilds. It's not even...

Rebuilding an index does two things. First, since you're literally rebuilding the index, it reorders the pages and the rows on those pages. This has a benefit in that it...

Restarting SQL Server does a whole ton of things. First, you're flushing memory. So queries coming along after the reboot have a clear memory run to load up just their...

Nope. If it's already running, you can't retroactively start collecting the data necessary for a plan with runtime statistics.

However, on SQL Server 2019 or greater and Azure SQL Database, you...

• This reply was modified 3 years, 5 months ago by Grant Fritchey.

Yeesh. Your team stacked up a bunch of jenga blocks awfully high. Have fun playing.

As to letting anyone edit them, I'd build a small app for it. No sense in exposing more than you need to.

Just that, as with anything, I'm sure there's a tipping point. "3 extended properties, no big deal, 300, 3000000, something, big deal". I honestly don't know how many zeroes you...

Total agreement, but this one that Sam will...

I assume there's a point at which extended properties will cause an issue, but I'm not aware of anyone that has hit it using the things in a standard way....

Everything Jeff said.

We've covered this in multiple posts. Capture query metrics, I'd go with batches & procedure calls, not individual statements at this point. Capture deadlocks (Extended Events, don't listen...

It can, yes. Ghost cleanup can also block you.

The vendor can't leave this with you. You can't change the code, and the code needs to be changed. You also can't,...

Yes. Its a small table.  Question is , when there is 0 rows in the table, and when we say SELECT * FROM <Tname> , why SQL Server is...

So, yeah, about what I expected. A clustered index scan and nothing else.

So, your #1 problem query is SELECT * from a table with two rows in it?

Dude, go home....