FIX: SQL Server 4.21a Service Pack 1 FixlistArticle ID: Q126010
The following is a list of fixes and other various improvements that have been made in SQL Server Service Pack 1. SQL Server Service Pack 1 is now available from your primary support provider. For more information, contact your primary support provider. Please note that workarounds have been provided for your information only. It is not necessary to implement these workarounds if you have the updated software. LIST OF PROBLEMS CORRECTED IN SERVICE PACK 1
FIX: Complex Query May Cause 1521 Error
SYMPTOMS
Sort failed because a table in tempdb used for the processing of the query had a bad data page count. This generally occurs when processing very complex queries that may involve any of the following: multiple tables, the use of dynamic indexes, internal sorting, or heavy use of tempdb.
WORKAROUND
NOTE: You may review your query plan by running SET SHOWPLAN ON before executing the query. For more information on interpreting SHOWPLAN output refer to "Appendix B: Understanding SHOWPLAN Output" in the "Microsoft SQL Server for NT Troubleshooting Guide."
FIX: Runtime Error in Trigger from RPC Causes Server to Hang
SYMPTOMS
CAUSE
Execution of the stored procedure locally will work properly, even if the runtime error is encountered. WORKAROUND
FIX: SELECT MAX from INT Column May Cause Access Violation
SYMPTOMS
MORE INFORMATION
Here is a brief script to demonstrate the problem: use pubs go drop table t1 go create table t1(c1 int, c2 int, c3 int, c4 int) go declare @counter int select @counter = 0 while @counter < 400 begin insert t1 values(@counter,@counter,@counter,@counter) select @counter = @counter + 1 end go select max(c4) from t1 go FIX: False Error 512 on Subqueries with Version 4.21.006
SYMPTOMS
A subquery in a select list must operate as an expression, which means it is not legal for such queries to return more than one row. Prior to version 4.21.006, SQL Server would not detect this condition as an error and would instead return the last row of the subquery result set. This was filed as bug 550, and a bugfix was supplied in 4.21.006. However, starting with this version some queries that are correctly returning one row are incorrectly generating the 512 error: Subquery returned more than 1 value. This is illegal when the subquery follows =, !=, <, <=, >, >=, or when the subquery is used as an expression. For example, if there are two tables: Emp empid name 1 Jane Doe Prod plantid process empid 1 1 1 1 2 1 The following query generates a false 512 error: select (select name from emp where emp.empid = prod.empid) from prod WORKAROUND If possible, recode the query as a join: select name from emp, prod where emp.empid = prod.empid FIX: Access Violation if Fully Qualified View Name Is Large
SYMPTOMS
WORKAROUND
|
Additional query words: Windows NT
Keywords : SSrvWinNT
Version : 4.21a 4.21a.sp1
Platform : WINDOWS
Issue type : kbref
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
©1997 Microsoft Corporation. All rights reserved. Legal Notices.