begin tran
declare @ID int
set @ID = 0
insert into T1 values(‘me’)
output @ID = Inserted.id
print @ID
rollback tran

thanks.

I suspect that we are running into this problem. But the stored proc that uses SCOPE_IDENTIFY is a very simple insert statement. We do get an invalid ID a couple of times a day.

How do I confirm that this is caused by this known bug? I am not sure when SQL server 2008 will choose generate a parallel plan.

Hope to hear from you. Thanks!

It’s working fine.

Thanx

I know this is not a long term solution. But it would allow me to move from SQL 2000 to SQL 2008 right away. Then go back and update the database along with web pages.

Regards,
Pinal Dave

How the trigger could affect the behaviour of OUTPUT clause?
The data in INSERTED table is affected nither by trigger nor
by OUTPUT clause. Both are just reading this table.

Regards,
Pinal Dave

Thanks for this wonderful peice of information.

But one thing I would like to get clarification from you here ,

as Output clause use inserted table
and also triggers written for insert and update also using inserted table.

I guess trigger on the same table will result in abnormal behaviour of output clause.

Pls. clarify this.

Kind Regards
Kuldeep

and no one has a time to change the code and deploy it again to the customers we have other things to do.

work around for the new projects but what about the one in production. Need a solution not a work around.

The bad thing is not the bug (every one make mistake). but action that was taken to fix it is not acceptable. it is almost 2 years since the bug was issued and no serious action was taken to solve it.

This is not the expected support that is supposed to be good.

I started to reconsider in other DBMS.

The scripts posted on the connect site to reproduce the problem are not downloadable.

Thanks.

SQL Server ODBC Native Client 10 just can’t grab the right Scope_Identity but the 2005 Native Client is fine connecting to a SQL Server 2008 database with our application.

so we are successful in getting the correct Scope_Identity while using the application with ODBC driver SQL Server Native Client from 2005… the following commands were issued:

INSERT INTO BinaryImage (“ImageSourceType”,”RetentionType”,”ImageSize”,”ImageDataCRC”…

SELECT SCOPE_IDENTITY()
SELECT …. FROM “BinaryImage” WHERE BinaryImageNo=2514628

But with ODBC SQL Server Native Client 2008 the same insert looks like:

exec sp_executesql N’ INSERT INTO BinaryImage (“ImageSourceType”,”RetentionType”,”ImageSize”,”ImageDataCRC”…

SELECT SCOPE_IDENTITY()
SELECT …. FROM “BinaryImage” WHERE BinaryImageNo=158731

Note: The BinaryImageNo should have been greater than 2,204,700

Thanks…

Phil S

As far as I know they have not addressed this issue in SP1.

As far as I know they will address this in next release of SQL Server.

Kind Regards,
Pinal

a) insert … values
b) insert … select (no from clause, an invariant for statement above)
c) insert … select … with MAX_DOP=1 – as noted at feedback comments forces nonparallel query plans

but I’m not sure that
insert … select top 1 … –complex query goes here
will not result in parallel execution, as query optimiser could decide to make parallel index scan, for example.

So there are only two ways to insert single row & return generated id: insert…maxdop=1 and insert…output.

The last one requires table variable, the first one supresses parallel plans. Which one will be more efficient? — I perfectly understand there are no universal recomendations:)

Thanks!

I wonder why I did not know it earlier. I have read this earlier on MS connect but I did not understand it there. Thanks for putting the same in simple words.

No wonder you are MVP. Do you work for Microsoft too.