Consider the following scenario. You create a table that has an identity column in a Microsoft SQL Server 2005 database. You configure a merge replication on the table. An application uses Microsoft ActiveX Data Objects (ADO) to insert a row in the table. Then, the application retrieves the inserted row. However, an incorrect value is returned for the identity column.

This problem occurs when the computer that runs the application has one of the following installed:

•	Windows Server 2003
•	Windows XP
•	Microsoft Data Access Components 2.8 (MDAC 2.8)

This problem does not occur in a Microsoft SQL Server 2000 database.

Back to the top

The replication process creates insert triggers in the table. When data is inserted in the table, the insert triggers use the @@IDENTITY variable instead of the SCOPE_IDENTITY function. Therefore, the @@IDENTITY variable may return an identity value that is not in the current table.

Back to the top

Hotfix information

Windows XP

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows XP Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name	File version	File size	Date	Time	Platform
Msadce.dll	2.81.1131.0	331,776	23-Aug-2007	10:09	x86

Windows Server 2003

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with Service Pack 1, x86-based versions

File name	File version	File size	Date	Time	Platform
Msadce.dll	2.82.2996.0	356,352	23-Aug-2007	02:19	x86

Windows Server 2003 with Service Pack 2, x86-based versions

File name	File version	File size	Date	Time	Platform
Msadce.dll	2.82.4137.0	356,352	23-Aug-2007	02:10	x86

Windows Server 2003 with Service Pack 1, Itanium-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Msadce.dll	2.82.2996.0	1,212,416	22-Aug-2007	13:30	IA-64	SP1	Not Applicable
Wmsadce.dll	2.82.2996.0	356,352	22-Aug-2007	13:30	x86	SP1	WOW

Windows Server 2003 with Service Pack 2, Itanium-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Msadce.dll	2.82.4137.0	1,212,416	22-Aug-2007	13:37	IA-64	SP2	Not Applicable
Wmsadce.dll	2.82.4137.0	356,352	22-Aug-2007	13:37	x86	SP2	WOW

Windows Server 2003, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Msadce.dll	2.82.2996.0	622,592	22-Aug-2007	13:30	x64	SP1	Not Applicable
Wmsadce.dll	2.82.2996.0	356,352	22-Aug-2007	13:30	x86	SP1	WOW

Windows Server 2003 with Service Pack 2, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Msadce.dll	2.82.4137.0	622,592	22-Aug-2007	13:37	x64	SP2	Not Applicable
Wmsadce.dll	2.82.4137.0	356,352	22-Aug-2007	13:37	x86	SP2	WOW

Microsoft Data Access Components 2.8

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have MDAC 2.8 Service Pack 1 installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name	File version	File size	Date	Time	Platform
Msadce.dll	2.81.1131.0	319,488	17-Aug-2007	09:58	x86
Msadco.dll	2.81.1131.0	143,360	17-Aug-2007	09:58	x86
Msado15.dll	2.81.1131.0	524,288	17-Aug-2007	09:58	x86
Msadomd.dll	2.81.1131.0	180,224	17-Aug-2007	09:58	x86
Msadox.dll	2.81.1131.0	200,704	17-Aug-2007	09:58	x86
Msdasql.dll	2.81.1131.0	307,200	17-Aug-2007	09:58	x86
Msjro.dll	2.81.1131.0	102,400	17-Aug-2007	09:58	x86
Odbcbcp.dll	2000.85.1131.0	24,576	17-Aug-2007	09:58	x86
Oledb32.dll	2.81.1131.0	471,040	17-Aug-2007	09:58	x86
Sqloledb.dll	2000.85.1131.0	520,192	17-Aug-2007	09:58	x86
Sqlsrv32.dll	2000.85.1131.0	438,272	17-Aug-2007	09:58	x86

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

The SCOPE_IDENTITY function and the @@IDENTITY variable return the last identity values that are generated in any table in the current session. However, the SCOPE_IDENTITY function returns values that are inserted only within the current scope. The @@IDENTITY variable does not limit the insertion to a specific scope.

For example, assume that the database contains a Table1 and a Table2. Both tables have identity columns. An insert trigger is defined in Table1. When a row is inserted in Table1, the trigger inserts a copy of the row in Table2. This scenario involves the following two scopes:

•	Insertion in Table1
•	Insertion in Table2 by the trigger

In this scenario, the @@IDENTITY variable and the SCOPE_IDENTITY function return different values when a row is inserted in Table1. The @@IDENTITY variable returns the last identity column value that is inserted across any scopes in the current session. In this case, the @@IDENTITY variable returns the identity value that is inserted in Table2. However, the SCOPE_IDENTITY function returns the identity value that is inserted in Table1, because the SCOPE_IDENTITY function returns the value that is last inserted in the same scope. The SCOPE_IDENTITY function returns the NULL value if the function is invoked before any INSERT statements that are made to an identity column occur in the scope.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top