Article ID: 246139 - View products that this article applies to.
This article was previously published under Q246139
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56536 (SQLBUG_70)
If the database log file has a limiting size option, such as a defined MAXSIZE or set FILEGROWTH = 0, and logged extent allocations fill the log during a nonlogged "BCP in" into a table with a TEXT column, the SQL Server process stops executing. There is be a stack dump for each spid, including system spids, written to the errorlog. The errorlog reports a 9002 error and CTRL-C does not stop the BCP command.
Summary of Events
You can use any one of the following to work around this problem:
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561For more information, contact your primary support provider.
(http://support.microsoft.com/kb/254561/ )INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
You may also encounter this bug if you use Data Transformation Services (DTS) to transfer objects if the specified conditions are met.