Looping through the tables and running a SELECT COUNT(*) against them could be quite resource-intensive if you have large tables (and it's good to avoid using the sp_MSForEach* procedures).

I'd just...

Unless...

sql-lover (3/14/2016)

---

I wrote an Extended Events that is helping me to capture the execution plan of an store procedure that needs some tuning. The Extended Events is working, but when...

I've seen stuff about this before. The expression in the CASE isn't necessarily evaluated once and then that result used for each comparison in the CASE, as you might expect.

Instead,...

With so little detail around the announcement yet, for me it's hard to say how much it will affect my day-to-day work.

Of course, this initial marketing announcement said mid-2017, so...

If this is just a one-time ad-hoc statement you want an easy way to construct, then Hugo's way will work nicely.

If you have to do this for a bunch of...

Rich Mechaber (3/2/2016)

---

Great question, Steve, thank you for exposing this. Anyone else find BOL more than less than unhelpful here?

Return Types

Returns a value cast to the specified...

Just keep in mind that the application...

DaveGlobalOptions (3/2/2016)

---

SELECT TRY_CONVERT(NVARCHAR(1), 234523) also gave me an error but SELECT CONVERT(NVARCHAR(1), 234523) rendered the * . I'm on SQL 2014 so I'm guessing it might be different with 2012...

To get that information exactly, you'd need to have something set up to capture it. Having said that, you can get somewhat close with what SQL Server gives you.

Autogrowth events...

What is the result of this query on your server?

SELECT scheduler_id,

cpu_id,

status ...

Indeed, that is just a guess on my part, trying to make sense of as much of the situation as possible.

Based on that example it seems (mildly annoyingly) that the...

My assumption is that this line from the BOL entry for COALESCE

has the intended meaning of

If and only if...

Steve Jones - SSC Editor (2/26/2016)

---

I'll disgree with you, Tom. The reason is this, and this is what I missed at first.

The top of the chart has an * for...

The big issue is the estimate for the rows coming out of the scan of #TempMPM that is the outer input for the first nested loop join.

It's estimating only...