Interesting, but I'd be wary of using it. In a multi-row update, the result is pretty much undefined, unless all the rows are updated to the same value. And in...

Yeah, using temp tables is absolutely a workable solution, as is session context. CLR functions probably not, unless they utilize some external...

I doubt that using PRINT to return information is used on a regular basis.  The only time I use PRINT for the purpose is for debugging a procedure I...

From any application (via ODBC or DB-LIBRARY) you can get the text returned from PRINT. In dblibrary you should use

int msg_handler(DBPROCESS *dbproc, DBINT msgno, int msgstate, int severity,char *msgtext,...

By that reasoning you should also include THROW, as well as modifying data in tables (particularly temp tables created by the caller).

Personally, I...

By that reasoning you should also include THROW, as well as modifying data in tables (particularly temp tables created by the caller).

Personally, I would not...

Unless my memory is completely shot, back in version 1.1a (yes, I'm that old / started that young) it really stood for "Database Consistency Check". That was pretty much all...

Good one!

Until I understood the framing context, I used to do the LAST_VALUE as FIRST_VALUE(.. ORDER BY [col] DESC), which works out the same, but is likely a worse approach...

Nice question, which required a fair amount of reading and calculating back and forth.

But there is a small issue with the "correct" answer: There is one zero missing in the...

Opinion noted... However, I can more easily do things with DATETIME that can only be dreamed of with DATETIME2.  Even Microsoft realized their mistake but, instead of fixing it,...

Possibly, but then again, we all know how much accountants love guesswork, right 😀

Anyway, I could easily dig up examples from the EU where the conversion rates between the EURO...

Well, that would depend on your country of operation, wouldn't it?

Actually, MONEY is useful if only for documentation purposes. You could use decimal but why would you want to? Being an integer makes the type faster than decimal.

DATETIME does...

Yes, because MONEY is a precise data type with 4 decimal places. It's implemented as a 64-bit integer, scaled down by 10000. That and DATETIME must be the two lamest...

I think the extra decimal digit is because if you multiply a number with 2 decimal places by a number with 1 decimal place, the result can have 3...