This article describes the following about this hotfix release:

• The issues that are fixed by the hotfix package
• The prerequisites for installing the hotfix package
• Whether you must restart the computer after you install the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes
• The files that are contained in the hotfix package

Consider the following scenario. You have a computer that has more than one microprocessor. You run an INSERT statement against a table that has an identity column. The INSERT statement is running in parallel. In this scenario, you may receive the following error message:

Cumulative update information

To resolve this problem, obtain cumulative update package 2 for SQL Server 2005 Service Pack 2 (build 3175). For more information about how to obtain cumulative update package 2 (build 3175), click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

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 SQL Server 2005 Service Pack 1 (SP1) installed on the computer. For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build. 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.

SQL Server 2005, x86-based versions

SQL Server 2005, x64-based versions

SQL Server 2005, Itanium architecture versions

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

Steps to reproduce the problem

1. Start SQL Server Management Studio, and then create a new query.
2. Run the following statements to create the test table.

   CREATE TABLE dbo.User_Cost3
   	(
   	Id int NOT NULL IDENTITY (1, 1),
   	Cost float(53) NOT NULL,
   	Started_Date datetime NULL,
   	Ended_Date datetime NULL,
   	User_Id int NOT NULL
   	)  ON [PRIMARY]
   go
   
   BEGIN TRANSACTION tran2
   declare @i int;
   set @i = 0;
   while(@i < 100000)
   begin
   	insert into dbo.User_Cost3 values(@i, GETDATE(), GETDATE(), @i)
   	set @i = @i + 1;
   end
   COMMIT TRANSACTION
   go
   

3. Run the following statements.

   declare @i int
   set @i = 1
   while(@i > 0)
   begin
   
   BEGIN TRANSACTION tran1
   
   CREATE TABLE dbo.#Tmp_User_Cost2
   	(
   	Id int NOT NULL IDENTITY (1, 1),
   	Cost float(53) NOT NULL,
   	Started_Date datetime NULL,
   	Ended_Date datetime NULL,
   	User_Id int NOT NULL
   	)  ON [PRIMARY]
   
   ALTER TABLE [dbo].[#Tmp_User_Cost2] ADD CONSTRAINT [Tmp_IXPKCU_User_Cost2__Id] PRIMARY KEY CLUSTERED ([Id]) ON [PRIMARY]
   
   SET IDENTITY_INSERT dbo.#Tmp_User_Cost2 ON
   
   IF EXISTS(SELECT * FROM dbo.User_Cost3)
   	 EXEC('INSERT INTO dbo.#Tmp_User_Cost2 (Id, Cost, Started_Date, Ended_Date, User_Id)
   		SELECT CONVERT(int, Id), Cost, Started_Date, Ended_Date, CONVERT(int, User_Id) FROM dbo.User_Cost3 WITH (HOLDLOCK TABLOCKX);')
   
   drop table dbo.#Tmp_User_Cost2
   
   COMMIT TRANSACTION
   
   print 'ok'
   end
   go

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: