March 3, 2011 at 4:30 pm
My apologies if this has been previously discussed, but I have not been able to find much more about this (other than Microsoft's discussions about it a couple of years back).
Does anyone have the inside track as to whether this can only be addressed in some sort of patch from Microsoft in the .NET Framework? Or can "Denali" address this issue, specifically?
From what I have read, it appears to be more .NET related to the Framework than SQL, but the effect is obvious.
Thank you in advance...
March 4, 2011 at 8:49 am
You can alternately use the IDENT_CURRENT('your table name here')
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
March 4, 2011 at 9:00 am
I've been avoiding ident_current and scope_identity since SQL 2005 came out with the Output clause. Avoids the problem completely and has a number of other benefits as well.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
March 4, 2011 at 9:24 am
The OUTPUT clause is a great way to handle this
March 4, 2011 at 12:27 pm
Awesome! Many thanks!
😀
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply