FIX: Insert from Linked-Server Into Table with BIT Field Having a DEFAULT Constraint Causes AV

Article translations Article translations
Article ID: 240798 - View products that this article applies to.
This article was previously published under Q240798
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56233 (SQLBUG_70)
Expand all | Collapse all

Symptoms

Inserting a row into a local table that has a BIT column, which has a DEFAULT constraint, may cause an access violation (AV) if the following are true:
  • The inserted value comes from a linked server table.
  • There is no specified value for the BIT column, hence, the DEFAULT expects to be used.

Workaround

Change the BIT column to CHAR or some other datatype that satisfies the business requirement.

Status

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:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 240798 - Last Review: October 26, 2013 - Revision: 3.0
Applies to
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB240798

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com