FIX: MIPS Full Transaction Log Can Cause Access Violations
  
PSS ID Number: Q115488
Article last modified on 08-28-1995
 
4.21 4.21a
 
WINDOWS
 

----------------------------------------------------------------------
The information in this article applies to:
 
  - Microsoft SQL Server, versions 4.21 and 4.21a
----------------------------------------------------------------------
 
BUG# NT: 795 (4.21 - NTMips)
 
SYMPTOMS
========
 
On SQL Server for Windows NT MIPS, a database with a full transaction log
may cause access violations in user processes and the CHECKPOINT process.
 
STATUS
======
 
Microsoft has confirmed this to be a problem in SQL Server version 4.21 for
Windows NT MIPS. This problem was corrected in SQL Server version 4.21a.
For more information, contact your primary support provider.
 
MORE INFORMATION
================
 
If the database option TRUNCATE LOG ON CHECKPOINT is turned on, and there
are separate DATA and LOG devices when the log fills, the CHECKPOINT
process may terminate with an access violation message in the error log. If
this option is not turned on, or the DATA and LOG segments are not
separate, you may get access violations on shutdown in the user process if
the log is full.
 
Additional reference words: 4.21 4.21a Windows NT
KBCategory: kbother kbbug4.21 kbfix4.21a
KBSubcategory: SSrvWinNT SSrvRISC
 
=============================================================================
 
Copyright Microsoft Corporation 1995.
