ISNULL will affect performance if the ISNULL is being used in WHERE, ON or HAVING. As part of the SELECT or VALUES listing of columns, ISNULL won't be a big...

Thanks for the responses everyone.

Rod, I feel for you man. It's hard to find good places where you can learn & grow. I went through four jobs in less than...

I point to three tools for monitoring query performance (not Jobs, Johan's answer is a good one), including batches, statements and procedures. These are, in no particular order, Dynamic Management...

So just to clarify. if i have a clustered index on say contactid and invoiceid however none of the updates are on those columns then there wouldn't be a...

I like @DesNorton's answer.

However, what about just using the SEQUENCE object? It'll do the increments for you. It doesn't have to be specifically an IDENTITY column that way.

Got an email from Degreed.com giving me recommendations for virtual training and … well, apparently there are urgent SQL courses I need to take today and ...

Well, what do...

So, I work for Redgate, so any & all biases up front.

Nope.

Not for what you want. I've evaluated some of the SaaS monitoring tools that will monitor SQL Server. Frankly,...

When I run the same query multiple times why does the CPU time fluctuate between 0 and 16ms in tracer, query cost and live data explorer? Also I have...

You can use Extended Events to capture errors. This can include, if needed, the T-SQL statement or Object_ID of the query involved.

I saw you posted this over on DBA.StackExchange. I like the one answer. There were also good comments. From the bytes received, it looks like each query returns different data?...

Emphasis has to be on the fact that while this is called Profiler, it's just a front-end for Extended Events.

Nice write up.

Yeah, not a clue. Most of the time, I get very good behavior out of Azure. Obviously not the same as something running locally, but very much the same as...

Thank you! I hope the same for you and yours.

Performance is likely to improve. However, one thing, instead of putting all the code into a single query inside a procedure, create a wrapper procedure for all the IF ......

That's an odd construct. NULLIF compares two values. If they're matching, it returns null. Otherwise, it returns the first value, in this case, @parameter. ISNULL checks the first...