Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
Posted - 2008-08-22 : 14:20:15
|
| One of our vendors pointed us to this patch, insisting that we apply it to our server:http://support.microsoft.com/kb/940569The KB article seems to imply this only affects database with Merge Replication enabled, and the triggers associated with Merge Replication.The vendor's app does not use Merge Replication.However, the vendor claims that this fixed an issue in their application where data was being assigned to incorrect identity values.They verified by running profiler before and after applying the patch. Before applying it, ADO was reading @@Identity, and after applying it ADO was reading scope_identity().So is the article misleading? Is this an issue any of you have come across?Boycott Beijing Olympics 2008 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-08-22 : 15:09:24
|
| I don't understand how ADO could be reading @@IDENTITY and then SCOPE_IDENTITY(). Don't you specifically code it in the application?Do the tables have triggers on them that also are inserting into a table with an identity column?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
 |
|
|
|
|
|