FIX: SQL Server FixList for Version 4.20aK11Article ID: Q106503 - Microsoft SQL Server version 4.2aK11 for OS/2 The following is a list of fixes and other various improvements that have been made in SQL Server version 4.20aK11. 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. FIX: Join Between Two Tables with 1=2 in WHERE Clause ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1639 SYMPTOMS
The following query causes the trap: select t1.c1 from t1,t2 where t1.c50=t2.c51 and 1=2 CAUSE SQL Server does not handle large table joins with 1=2 in the WHERE clause correctly. WORKAROUND
STATUS
FIX: Multiple Procedures in Transaction Causes GP Fault ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1669 SYMPTOMS
Warning: OPEN OBJECTS parameter may be too low; attempt was made to free up descriptors in localdes(). Run sp_configure to increase parameter value. CAUSE SQL Server incorrectly handles the execution of stored procedures that do updates within a user-defined transaction when the value of open objects is low. WORKAROUND
STATUS
FIX: 803 Error on Select Based Insert ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1692 SYMPTOMS
Unable to place buffer 0x%ld holding logical page %ld in sdes for object '%s' - either there is no room in sdes or buffer already in requested slot. Under rare circumstances, an insert of the form: insert table803 select * from source_table on a table with two or more non-clustered indexes can result in an 803 error. This error is very dependent on the data in the indexes at the time the operation is attempted.
WORKAROUND
STATUS
FIX: Select Local Variable with for Browse Drops Connection ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1705 SYMPTOMS
Error 10008 Bad Token from SQL Server or may trap the server. This only happens when a unique index exists on the table being selected from. For example: DECLARE @ordnum int SELECT @ordnum = OrderNumber FROM SaleOrder WHERE OrderNumber = 1 FOR BROWSE WORKAROUND Do not use the FOR BROWSE clause in a Transact SQL statement when values are being selected into local variables. The FOR BROWSE clause is designed to be used with DB-Library applications, and is not designed to be used in situations like this. STATUS
FIX: Clients Hang Issuing Concurrent WRITETEXTs ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1711 (4.2) and 1712 (1.11) SYMPTOMS
CAUSE
STATUS
FIX: SELECT INTO with Outer Join can Trap Server ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1713 SYMPTOMS
A protection violation has occurred. The minimum conditions required for replication are the following:
Following is a minimal example of the table structures and query required to trap the server. You will need to have at least 580 rows of data in t1 to replicate the error. /*****************************************************/ /* Set up the two tables */ /*****************************************************/ use pubs go drop table t1 go create table t1 (c1 char(2) null, c2 varchar(10) null, c3 varchar(10) null) go drop table t2 go create table t2 (c4 char(2), c5 money) go /**************************************************/ /* The query */ /**************************************************/ /* Need to insert data or query will not crash. */ select c2, c3, c5 into #temp_snapshot from t1, t2 where t1.c1 *= t2.c4 group by c2, c3, c5 go STATUS Microsoft has confirmed this to be a problem in SQL Server version 4.2a. This problem was corrected in SQL Server version 4.2aK11. FIX: Update Trigger Fails After Upgrading to 4.20K8 ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1727 SYMPTOMS
Invalid column name ''. (Msg 207, Level 16, State 3). Invalid column name ''. (Msg 207, Level 16, State 3). Invalid column name ''. (Msg 207, Level 16, State 3). The column names contain indecipherable characters. This can also happen if a dump made on a server running a version earlier than 4.20k8 is loaded into a server running 4.20k8.
WORKAROUND
STATUS
FIX: Insert into View Causes GP Fault ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1729 SYMPTOMS
WORKAROUND Make sure you recreate all underlying tables before an INSERT into a view. STATUS
FIX: RPC Uses Case Sensitive Passwords ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1730 SYMPTOMS
7221, Login to site server2 failed. Other logins on the same server, however, can use the same RPC with no problems.
CAUSE
WORKAROUND
STATUS
FIX: String Functions for Char Datatype in a View ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1734 SYMPTOMS
char datatype column of a View returns the result as padded with blanks to be 256 character in length. Datalength function does return correct length. This does not happen for varchar datatype column in the view. Using the base table instead of the view also returns correct results. For example, in the following script, function RTRIM returns results padded with blanks to be 256 characters in length. create table T1 (textdat char(30)) go insert into T1 (textdat) values ('a') insert into T1 (textdat) values ('ab') go create view VT1 (textdat) as select textdat from T1 go select rtrim(textdat) from VT1 /* incorrect */ go WORKAROUND Note that the problem does not occur on the varchar datatype columns in a view. Therefore, you may modify your view creation statement as: create view VT1 (textdat) as select convert(varchar(30),textdat) from T1 This causes the results to be correctly returned for the string functions. Alternately, you can also convert the char value to a varchar before applying the rtrim or other string functions; for example: select rtrim(convert(varchar(30),textdat)) from VT1 STATUS Microsoft has confirmed this to be a problem in SQL Server version 4.2. This problem was corrected in SQL Server version 4.2aK11. FIX: Error 4305 Loading Log Dump ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1740 (v1.11), 1741 (v4.20) SYMPTOMS
Specified file <dump file> is out of sequence. Current time stamp is <date/time 1> while dump was from <date/time 2>. (Msg 4305, Level 16, State 1) CAUSE SQL Server incorrectly allows a DUMP TRANsaction command to be issued while inside a user-defined transaction. If after dumping the transaction log, the user-defined transaction is rolled back, any attempt to later load that transaction log dump will fail with the 3305 error. WORKAROUND
select @@trancount If this returns any value other than zero, your connection is inside of a transaction, and the transaction should either be committed or rolled back before issuing the DUMP TRANsaction command.
STATUS
FIX: Trap on Insert with Select Union on Same Table ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1755 SYMPTOMS
create table testtrap (cola int) go insert testtrap select * from testtrap union select * from testtrap STATUS Microsoft has confirmed this to be a problem in SQL Server version 4.2. This problem was corrected in SQL Server version 4.2aK11. FIX: SHOWPLAN ON and SELECT INTO Involving UNION ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1591 SYMPTOMS
WORKAROUND
STATUS
FIX: Dividing by Negative Money Value Causes Timeslice Error ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1574 SYMPTOMS
timeslice -1501, current process infected. SQL Server will temporarily lock up until the timeslice is detected. At that time, the process is terminated and SQL Server resumes as normal. Note: Timeslice errors may cause SQL Server version 1.11 to general protection fault (GP fault) (bug# 1574/1575).
CAUSE
STATUS
FIX: Index Incorrectly Chosen when Highest Key Value Used ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1666 SYMPTOMS
This only happens when the high value is used in a greater than comparison (>), or in the high value of a between statement. Using the highest key in an equality test (=), or a value one above or below will show the index being used correctly. CAUSE
If the highest key value is used as the high value in a between statement, the optimizer will incorrectly use an index when it should do a table scan. Using the index, in this case, causes more page I/Os to be performed than would be in a table scan, causing the query to run much longer than it should. WORKAROUND
STATUS
FIX: INSERT INTO a Temporary Table Can Cause GP Fault ARTICLE ID: \[\[..\/\|Q\]\] BUG# 1760 SYMPTOMS
CAUSE
- The INSERT INTO the temporary table must be within a stored procedure. - You must be inserting into the temporary table using a SELECT statement that returns at least part of the temporary table in question. - It will only occur with specific datasets.
STATUS
|
Additional query words: 4.20aK11
Keywords : SSrvGen kbfixlist
Version : 4.2a
Platform : OS/2
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.