+1 🙂

Nice explanation the OUTPUT clause is in: https://www.simple-talk.com/sql/learn-sql-server/implementing-the-output-clause-in-sql-server-2008/

George Vobr (9/29/2016)

---

colin.frame (9/29/2016)

---

Thanks George. That triggered a further bit of research.

The puzzle for me was where the extra decimal places came from in the AVG result....

colin.frame (9/29/2016)

---

Thanks George. That triggered a further bit of research.

The puzzle for me was where the extra decimal places came from in the AVG result. I've...

colin.frame (9/29/2016)

---

Why do we get an answer like "9.000000" instead of "9" when the length is 0 (i.e. rounded to no decimal points)? The answer here has two parts....

As the output a message of the parser in the query result window? :unsure:

(a small nit-pick...) 😉

An interesting QotD, but it was necessary to proceed slowly and cautiously to find the right answers...:hehe:

Thanks Carlo for thoughtfully prepared question and good references.

Thanks Igor for this question. It made me diligently googled and study

SQL Server Hardware e-book from Glenn Bery and more. Then I found the correct

answer in an article on...

Formulation of the question makes me a bit confused. Which transaction isolation level is NOT available to transactions running

in the master and msdb databases? For the DB administrator, all...

Practical for use is that the second parameter may have also a negative value,

thanks for this seemingly simple question Nagaraj. 🙂

Interesting question and even more interesting answer, thanks Steve 🙂

The answer "The row is not updated and no error is returned."

should rather be listed as: "No row is not...

Thanks Steve, a good opportunity to repeat the Query Hints.

I can't forgive join this beautiful article from one gentleman

who was recently as a subject in the QotD. ...

Thanks for an interesting question Steve.

The reference MSDN catalog.start_execution (SSISDB Database) gives only an example

with the parameter N'LOGGING_LEVEL'. The use of other parameters is well explained here:

http://sqlblog.com/blogs/andy_leonard/archive/2015/11/04/the-synchronized-ssis-execution-parameter.aspx

or here:

http://www.ssistalk.com/2012/07/24/quick-tip-run-ssis-2012-packages-synchronously-and-other-execution-options/

Hmm, interesting, numeric_expression 0.5 - 0.9 cannot be with the ROUND function directly rounded.

SELECT ROUND (0.4, 0);

SELECT ROUND (0.5, 0);

Results

---------------------------------------

0.0

(1 row(s) affected)

---------------------------------------

Msg 8115, Level 16, State 2, Line 9

Arithmetic overflow...

Thanks Steve for this good question. Quite it was useful to repeat

a little something from the SQL Server Security Functions.;-)

RonKyle (9/6/2016)

---

What could have thrown me was that I though ET was 5 hours off GMT. ET is five hours behind time in England and 6 in central Europe....