Microsoft KB Archive/170224

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 10:05, 21 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


BUG: Access Violation When Using ANSI JOIN on a Table with View

Article ID: 170224

Article Last Modified on 10/3/2003



APPLIES TO

  • Microsoft SQL Server 6.5 Standard Edition



This article was previously published under Q170224

BUG #: 16994

SYMPTOMS

An ANSI JOIN of a table with a view that was generated without a base table may result in an access violation (AV). The following script demonstrates this problem:

   SELECT c = 0 INTO t
   GO
   CREATE VIEW v AS SELECT c = 0
   GO
   SELECT t.c, v.c
      FROM t JOIN v ON t.c = v.c
   GO
                


The following error message may be observed in the server error log, while "DB-Library Process Dead - Connection Broken" is observed in the client side.

EXCEPTION_ACCESS_VIOLATION raised, attempting to create symptom dump
Initializing symptom dump and stack dump facilities


This error message is followed by stack trace information.


WORKAROUND

To work around this problem, try to avoid using an ANSI JOIN. For example, the following script demonstrates the workaround for the above scenario:

SELECT t.c, v.c
FROM t, v
WHERE t.c = v.c
GO
                

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords: kbbug kbusage kbsqlserv650bug KB170224