TheSQLGuru (10/15/2014)

---

GilaMonster (10/15/2014)

---

And an extended events session will have even...

Use extended events because they're much lower cost than trace (much, much, much lower). Capture rpc_complete and sql_batch_complete. That can show you which queries are running to completion and what...

sql-lover (10/15/2014)

---

Thanks for reply Grant.

Wow, that was useful....

There really are lots and lots of good books out there. I'd suggest getting a copy of Itzik Ben Gan's "Inside T-SQL Querying." It's a must read. You also can't...

If the transaction log was filled by these deletes, you might be better off breaking them apart and calling them separately.

While you might have seen a minor improvement with forcing an index, that's a very bad choice most of the time for tuning. Let the optimizer do it's job. If...

You can't highlight part of a procedure and run it as if you were running the procedure. You have to build the procedure and then execute it to test it.

It had to have gotten into cache the same way as all other plans. It was called and compiled that way. You'd want to look at the first operator in...

If you're out of the period, there's not really any way to know what was happening without having set up the extended events ahead of time, or turning it on...

That's one piece of functionality that didn't make the transition into the GUI for extended events. You just can't do it.

Changes to a procedure will mark it for recompile if a plan for that proc exists in cache. You can't get the old code.

There are a number of tools that allow you to mount an HTML connection as a drive, so you don't even have to use the Microsoft tool if you don't...

I also work for Red Gate. You can throw my opinion away as appropriate.

I'd also suggest looking at SQL Source Control to get your database into source control as a...

I've never seen a book just on Management Studio. Most of the books are around doing things within SQL Server Management Studio and then, by extension, teach it. For an...

UDBA (10/13/2014)

---

The table has about 1.5 billion rows, maybe that's why it's not able to correctly estimate the "Estimated Rows". Query is not timing out, it is using the execution...