Unfortunately this doesn't solve the problem with nested INSERT INTO ... EXEC procedures since it uses same technique.

But it is helpful to read the structure of the dataset, returned by...

Hi Brian,

I assume you are using transactional database as an example, but I would like to hear your thoughts on ROLAP structure. There is an opinion among Data Mart developers...

INSERT EXEC is not the best method by itself.

I would try to extract the code from your SP and wrap it in new function, then change the SP to call...

MyDoggieJessie (10/15/2013)

There is virtually no...

That is well-known behavior of the COUNT(), but the question I have is this: What makes you think that COUNT(1) in any way superior to CONT(*)?

Exactly my thoughts, Dirk. This solution doesn't work with rolled back transactions. The only way we have found is to use cmdshell to log errors in local txt file on...

There is a great article by the way, on dynamic SQL and the ways to avoid it here:

http://www.sommarskog.se/dynamic_sql.html

Jacob,

there is a simple solution to make < and > work with non-dynamic version, when parameter is null.

In your example:

/*

Option 1

This will not work if "@ReorderPoint" IS NULL

*/

SELECT *

FROM Production.Product

WHERE...