Thanks for your input.

Did read it, but it does not address the parameterization setting causing different behaviour.

And why it does work on a SQL Server 2017 and not on a...

As I mentioned in my previous post: they all have the same compatibility level : 130 (SQL Server 2016).

BUT ... I kept digging and looking for differences between database settings....

Thanks Lynn & Scott for your answers!

I got a SQL Server 2017 box installed: and indeed on that one it works like I expected.

On the SQL Server 2016 box I...

Could you provide the code of the stored procedure sp_PROC_NAME ?

I

Let's revive this thread to acknowledge that the bug has been fixed within SQL SERVER 2014!

(or should I open a new thread in the proper subform 🙂 )

My mistake, didn't catch that first link.

Both links cover what I need to know to...

Thanks for clarifying this!

So, it's not a bug, but rather a poor design decision 🙂

Reading the page you posted, leads me to another question: the AllowThousands entry specifies a 0...

Are there any other requirements related to that "reference number"?

If it is just an integer, then perhaps you could use a SEQUENCE, which is a new feature in SQL Server...

Possibly one or both values/columns are null.

In that case the IF NOT EXISTS will yield TRUE so the INSERT-statement will be executed.

Let's explain it a bit as well ...

OUTPUT Clause (Transact-SQL)

column_name

Is an explicit column reference. Any reference to the table being modified must be correctly qualified by either the INSERTED or...

GilaMonster (5/23/2013)

---

Like this you mean?

CREATE TABLE #test (

ID INT

)

INSERT INTO #test (ID)

VALUES (1),...

mister.magoo (5/22/2013)

---

marc.snoeys (5/17/2013)

---

That's basically my point 🙂

There is nothing wrong with the INSERT-statement at all.

But, my personal opinion is that it would be more intuitive to be able to write...

Sergiy (5/22/2013)

---

marc.snoeys (5/17/2013)

---

That's basically my point 🙂

There is nothing wrong with the INSERT-statement at all.

But, my personal opinion is that it would be more intuitive to be able to write...

That's basically my point 🙂

There is nothing wrong with the INSERT-statement at all.

But, my personal opinion is that it would be more intuitive to be able to write an INSERT-statement...

Tobar (5/15/2013)

---

still, when you have

insert (ColA, ColB, ColC, ColD, ColE, ColF, ColG, ColH, ColI) values (this, that, the, other, thing, then, one, more, thing)

my eyes just do not match them...