FIX: The schema that indicates the Identity column in the source database is not transferred to the destination database when you try to transfer objects from a source database to a destination database by using SQL Management Objects in SQL Server 2005

Extended support for SQL Server 2005 ended on April 12, 2016

If you are still running SQL Server 2005, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 412568 (SQLBUDT)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
SUMMARY
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
SYMPTOMS
In Microsoft SQL Server 2005, you try to transfer objects from a source database to a destination database by using SQL Management Objects (SMO). When you try to do this, the schema that indicates the Identity column in the source database is not transferred to the destination database.

Note The data for the column is transferred correctly.
RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

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

There are no prerequisites for this hotfix.

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 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 tool in Control Panel.
SQL Server 2005 32-bit versions
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.dtstransferprovider.dll9.0.1504.0113,36807-Dec-200504:48x86
Microsoft.sqlserver.smo.dll9.0.1504.01,559,25607-Dec-200504:48x86
Microsoft.sqlserver.tabletransfergeneratortask.dll9.0.1504.043,73607-Dec-200504:48x86
SQL Server 2005 64-bit version
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.dtstransferprovider.dll9.0.1504.0113,36807-Dec-200509:01x86
Microsoft.sqlserver.smo.dll9.0.1504.01,551,06407-Dec-200509:01x86
Microsoft.sqlserver.tabletransfergeneratortask.dll9.0.1504.043,73607-Dec-200509:01x86
SQL Server 2005 Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.dtstransferprovider.dll9.0.1504.0113,36807-Dec-200508:17x86
Microsoft.sqlserver.smo.dll9.0.1504.01,551,06407-Dec-200508:17x86
Microsoft.sqlserver.tabletransfergeneratortask.dll9.0.1504.043,73607-Dec-200508:17x86
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 1.
MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 911937 - Last Review: 01/17/2015 12:43:39 - Revision: 2.4

Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems, Microsoft SQL Server 2005 Enterprise X64 Edition, Microsoft SQL Server 2005 Standard X64 Edition, Microsoft SQL Server 2005 Standard Edition

  • kbnosurvey kbarchive kbautohotfix kbsql2005sp1fix kbsql2005tool kbprb kbqfe kbhotfixserver kbsql2005presp1fix KB911937
Feedback