Select the product you need help with
FIX: The values of the datetime column are not same for the rows that are copied when you copy data to a table by using the GETDATE() function in Microsoft SQL Server 2005Article ID: 958547 - View products that this article applies to. 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. On This PageSYMPTOMSWhen you copy data to a table that contains a column of the datetime data type in Microsoft SQL Server 2005, the values of the datetime column are not same for the rows that are copied. This issue occurs if you copy all the rows in one batch or if you copy rows in batches by specifying a batch size. Note This issue does not occur in SQL Server 2000 or in SQL Server 2008. This issue may occur in one of the following scenarios. Scenario 1You set the default value of the datetime column to the GETDATE() function. You bulk copy data between the table and a data file by using the BUIL INSERT statement or by using the Bulk Copy Program (BCP) utility. When you copy data, you do not specify values for the datetime column in the data file.Scenario 2You copy data by using a distributed query that uses the GETDATE() function to set values for the datetime column.RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:913089
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
Hotfix informationThe fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:956854 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/956854/LN/
)
Cumulative update package 10 for SQL Server 2005 Service Pack 2937137 Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONTo enable this hotfix, you must enable trace flag 4129. For more information about how to enable a trace flag in SQL Server 2005, see the "Remarks" section in the following Microsoft Developer Network (MSDN) Web site: http://msdn2.microsoft.com/en-us/library/ms188396.aspx For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
(http://msdn2.microsoft.com/en-us/library/ms188396.aspx)
956854
(http://support.microsoft.com/kb/956854/LN/
)
Cumulative update package 10 for SQL Server 2005 Service Pack 2REFERENCESFor more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137 For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/937137/LN/
)
List of the builds that are available after SQL Server 2005 Service Pack 2 was released935897 For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/935897/LN/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems913089 For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/913089/LN/
)
How to obtain the latest service pack for SQL Server 2005 http://go.microsoft.com/fwlink/?LinkId=71711 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:
(http://go.microsoft.com/fwlink/?LinkId=71711)
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/LN/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 958547 - Last Review: December 16, 2008 - Revision: 4.0 APPLIES TO
|
Back to the top
