Microsoft KB Archive/98273

{|
 * width="100%"|

FIX: SQL Server Fixlist 4.2a K4 and K5 (Part 3 of 3)
'Article ID: Q98273

Creation Date: 02-MAY-1993

Revision Date: 28-APR-1997' Fixes introduced in the SQL Server 4.20K5 Server

The following is a list of problems, and various other improvements that were discovered during internal testing, that have been fixed in SQL Server version 4.2a. Version 4.2a includes server patches K4 through K5. 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.

Query Timeout Won't Allow Infinite Time-out Period ID: Q88492

SYMPTOMS

In SQL Administrator, setting the Query Timeout to 00:00 in the Configuration option fails to set an infinite time-out period. WORKAROUND If you want to execute a query that requires a time-out period greater than 59 minutes, you can either wait for the query to time out and then select the option to continue the operation, or  execute the query from ISQL or SAF. STATUS Microsoft has confirmed this to be a problem in SQL Administrator version 4.2. This problem was corrected in SQL Administrator version 4.20.1 and SQL Server 4.2a. >>>>>>>>>>>>>>>>>>> SQL Admin Scheduled Backup: Invalid Start Time ID: Q88597

SYMPTOMS

Scheduling a backup event with a start time of 12:nn PM sets the start time to the invalid value, 24:nn. The backup does not take place at any time.

For example, entering start times such as 12:50 PM or 12:10 PM sets the start times to 24:50 and 24:10, respectively, which are illegal values. The backup will not occur. WORKAROUND Change your scheduled backup event start time to a value in a form other than 12:nn PM. STATUS Microsoft has confirmed this to be a problem in SQL Administrator version 4.2. This problem was corrected in SQL Administrator version 4.20.1 and SQL Server 4.2a. >>>>>>>>>>>>>>>>>>> ISQL Returns a Syntax Error in a Script ID: Q88601

SYMPTOMS

ISQL does not correctly parse a line containing GO if anything follows GO on that line.

For example, executing a SQL script containing a comment, a number, or a tab after GO on the same line and following a PRINT statement, as in the following example

print &quot;hello&quot; go /*hello*/ select 1 go

generates the following message:

Msg 102, Level 15, State 1: Incorrect syntax near 'go'

Similarly, if a comment or a tab follows GO on a command line, GO  is not recognized as a batch terminator. For example, the following script is executed as a single batch instead of two separate batches:

select 1 go /*help*/ select 1 go

In addition, if GO is followed by a number &quot;n&quot;, to execute the command &quot;n&quot; times, (such as &quot;GO 2&quot;), you receive the same syntax error. CAUSE ISQL does not recognize GO as a command terminator if it is  followed by a comment, a number, or a tab. WORKAROUND You can move the comment following the GO to the next line. To  execute a command multiple times, instead of specifying a number after &quot;GO&quot;, use control-of-flow language; however, doing this will print the results multiple times. >>>>>>>>>>>>>>>>>>> Setting NO EXEC in SQL Administrator Hangs Queries ID: Q88693

SYMPTOMS

When you use the Query Window of SQL Administrator to do an ad-hoc query, SQL Administrator displays an hourglass pointer and hangs. No query time-out occurs. CAUSE SQL Administrator fails to time out when you set the NO EXEC option in the Query Options dialog box and the current database is not master. WORKAROUND Do not set the NO EXEC option, either from the Query Options dialog box or by using an ad-hoc query. STATUS Microsoft has confirmed this to be a problem in SQL Administrator version 4.2. This problem was corrected in SQL Administrator version 4.20.1 and SQL Server 4.2a. >>>>>>>>>>>>>>>>>>> SQL Admin Times Out When Query Returns No Results ID: Q89242

SYMPTOMS

SQL Administrator will time out if a query returns no result. If  the user chooses OK in response to SQL Administrator's prompt to   continue the query, the processing will continue only to time out again. This behavior is seen when SQL Administrator is running on  the same OS/2 machine that SQL Server is running on. WORKAROUND The System Administration Facility (SAF) or the ISQL utility may be  used in place of SQL Administrator when queries must be run from the SQL Server machine. STATUS Microsoft has confirmed this to be a problem in SQL Administrator version 4.2. This problem was corrected in SQL Administrator version 4.20.1 and SQL Server 4.2a. >>>>>>>>>>>>>>>>>>> dbtxtsnewval Causes Error Message 7129 ID: Q89323

SYMPTOMS

An attempt to perform text or image operations using the timestamp value returned by dbtxtsnewval results in SQL Server message 7129, &quot;Synchronization time stamp does not agree with text data page value.&quot; CAUSE The dbtxtsnewval function incorrectly returns an invalid value. WORKAROUND Reselect the text or image data, and get the new timestamp with dbtxtimestamp. STATUS This problem was corrected in DB-LIBRARY version 4.20.21 and SQL Server version 4.2a. >>>>>>>>>>>>>>>>>>> dbcursorfetch FAILs with Syntax Error 102 ID: Q89324

SYMPTOMS

The dbcursorfetch function returns FAIL, also resulting in SQL Server error 102, &quot;Incorrect syntax near 'testdata'.&quot; CAUSE This problem occurs only when data in a CHAR or VARCHAR column contains embedded double-quotation mark (&quot;) characters, a unique index exists on that column, and DB-LIBRARY (db-lib) cursors use that unique index. The dbcursorfetch function formulates an  incorrect query to fetch the requested rows. WORKAROUND Do not put the unique index on a CHAR or VARCHAR column with data that contains embedded double- quotation mark (&quot;) characters. STATUS This problem was corrected in DB-LIBRARY version 4.20.21 and SQL Server version 4.2a. >>>>>>>>>>>>>>>>>>> SQL Monitor Fails to Update Event History ID: Q89654

SYMPTOMS

When examining the Event History in SQL Administrator, you might notice that transaction log dumps do not appear to be displayed. CAUSE After SQL Monitor dumps the transaction log, it attempts to insert a new row in the MSscheduled_backups_log table. This is the table that is used by SQL Administrator to determine the Event History. SQL Monitor tries to pass an incorrectly structured query to SQL Server; thus, the row will not be inserted in the proper table. STATUS Microsoft has confirmed this to be a problem in SQL Administrator version 4.2. This problem was corrected in SQL Administrator version 4.20.1 and SQL Server 4.2a. >>>>>>>>>>>>>>>>>>> BCP Causes Syntax Error 102 ID: Q89270

SYMPTOMS

The Bulk Copy Program (BCP) will stop executing and zero rows are copied when the following valid command is executed:

BCP pubs..titles out test.out /Sgator1 /Usa /P

The following message is returned from the server:

Msg 102, Level 15, State 1: Line 1: Incorrect syntax near '-'. CAUSE The BCP utility is forming an incorrect command and sending it to  the server. The server's parser detects the problem, and returns message 102. WORKAROUND To work around this problem, either use a format file (.FMT), or  choose the native or character file formats, /n and /c, respectively. The key is to prevent BCP from prompting for the column definitions. STATUS Microsoft has confirmed this to be a problem in the bulk copy program version 4.2. This problem was corrected in the bulk copy program version 4.20.21 and SQL Server 4.2a. >>>>>>>>>>>>>>>>>>> Upgrade Fails When Installing 4.2 Developer Version ID: Q89388

SYMPTOMS

When you are installing the developer version of SQL Server version 4.2 and the Setup program detects that a 1.x version of SQL Server is already installed, it will attempt to upgrade the existing software. Shortly into the upgrade process, the following errors are returned and the upgrade fails:

User connections are limited to 5. (Msg 5828, Level 16, State 2)

Error: Setup was unable to upgrade existing databases. Check the file UPGRADE.OUT in the \INSTALL directory of your \SQL path for more information.

The UPGRADE.OUT file contains the following two lines:

Starting upgrade to SQL Server 4.2.0. Checking all tables for text data. CAUSE The developer version of SQL Server 4.2 is limited to five user connections and is unable to upgrade a 1.x version of SQL Server, which allows more than five user connections. RESOLUTION Since there was not a &quot;developer version&quot; for versions 1.1 and 1.11 of SQL Server, the developer version for 4.2 is not intended to  upgrade previous versions. Rather, it should be installed as a new product. There is a separate SQL Server 4.2 Upgrade product to  upgrade existing 1.x users to version 4.2. To obtain this upgrade, contact your Network Specialist or call Microsoft Inside Sales at  (800) 227-4679.

If you want to use the 4.2 developer version with existing 1.x  databases, do the following:

1. Using the current 1.x version of SQL Server, dump all existing databases, including master, to appropriate dump devices.

2. Run the 1.x version of the Setup program and choose the option to remove SQL Server from your system.

3. Run the Setup program included with the 4.2 developer version. If you will be loading 1.x version databases into the 4.2 version, select code page 850. If your 1.x SQL Server was installed as a case-insensitive server, choose the 1.x strict compatibility sort order. If your 1.x SQL Server was installed as a case-sensitive server, choose the binary sort order.

4. Re-create your devices and databases that had been defined for the 1.x installation.

5. Use the DBCC ALLOW11LOAD command, as documented on page 174 of        the SQL Server 4.2 &quot;System Administrator's Guide,&quot; to load the 1.x database dumps for each database, with the exception of the master database. The dump of the 1.x master database is needed only if you need to return to your existing 1.x installation. >>>>>>>>>>>>>>>>>>> SQL Admin: Database Properties Report Missing Info. ID: Q89933

SYMPTOMS

If you choose Manage/Databases, Manage/Databases/Properties from the SQL Administrator menu, a window appears that lists the database properties, such as users, options set, data and log space used, and so on. This window also contains a Print button. However, when you choose the Print button, some information is not printed. >>>>>>>>>>>>>>>>>>> SUSPECT/READ ONLY Databases Cause Upgrade to Fail ID: Q90883

SYMPTOMS

If one of the databases on a versions 1.1x server is marked as  SUSPECT or READ ONLY and an attempt is made to upgrade the server to 4.2, the upgrade process will abort. CAUSE The upgrade program does not detect the presence of SUSPECT or READ ONLY databases and does not report the appropriate error so the user can correct the problem prior to proceeding with the upgrade. More Information: The upgrade fails as follows:

Several messages flash across the screen too fast to be read, beginning with the line &quot;upgrade countered fatal error.&quot; Then the following error messages are displayed:

Setup was unable to upgrade existing databases.

They must be upgraded for SQL Server to operate properly.

Check the file UPGRADE.OUT in the \INSTALL directory under the \SQL directory you choose.

In the case of SUSPECT database(s), the UPGRADE.OUT file contains the following information:

Starting Upgrade to 4.2.0 Checking all tables for text data

There is nothing in the error log to indicate a problem.

In the case of READ ONLY database(s), the UPGRADE.OUT file contains the following information:

Starting upgrade to SQL Server 4.2.0 Checking all tables for text data Adding new messages to sysmessages Adding new configuration variables to sysconfigures Adding new configuration variables to spt_values Adding new datatypes to the existing databases

The error log contains no relevant information.

SQL Server 4.2a correctly detects databases in these states and displays an appropriate error message. >>>>>>>>>>>>>>>>>>> Master w/Log Only Fragment Causing Upgrade to Fail ID: Q9088

SYMPTOMS

If sp_logdevice has inadvertently been run on an expanded master database, the second fragment is marked &quot;log only&quot; and the upgrade to SQL Server 4.2 will fail since there will be no free space for the new data. CAUSE When the master database is checked for free space during the initial stages of the upgrade, the upgrade finds enough space in  the master database even though one of the fragments is marked &quot;log only.&quot; This is because this initial check for free space does not differentiate between data and log segments. More Information: For example, suppose sp_helpdb displays the following information:

2Mb  log only 3Mb  data only

Because the initial check for free space does not differentiate between data and log segments, the upgrade fails well into the process with the following symptoms:

Setup was unable to upgrade existing databases.

They must be upgraded for SQL Server to operate properly.

Check the file UPGRADE.OUT in the \INSTALL directory under the \SQL directory you choose.

The UPGRADE.OUT file contains the following information:

Starting Upgrade to SQL Server 4.2.0 Checking all tables for text data Adding new messages to sysmessages Adding new configuration variables to sysconfigures Adding new configuration variables to spt_values Adding new datatypes to all existing databases Upgrading Sysindexes columns for each database database: .             .   Creating system table Loading file 'nocase34.850'

Found a [sortorder] section

Finished loading file 'nocase34.850' 1 sort order loaded successfully Syscharsets, and its indexes. Load the code page 850 character set into syscharsets Load the code page 437 character set into syscharsets Load the iso_1 character set into syscharsets Load the binary codepage 850 sort order into syscharsets Load the special ASCII-8 caseless sort order Adding sysservers table and indexes

No relevant information is in the error log. >>>>>>>>>>>>>>>>>>> Upgrade Fails When Databases > Number Configured ID: Q90885

SYMPTOMS

If the number of databases is greater than the configured number of  open databases, the upgrade fails. RESOLUTION Make sure that the &quot;run value&quot; for &quot;open databases&quot; in the output of sp_configure is at least equal to the number of databases on the versions 1.1x server. More Information: The upgrade fails with the following error messages:

Setup was unable to upgrade existing databases.

They must be upgraded for SQL Server to operate properly.

Check the file UPGRADE.OUT in the \INSTALL directory under the \SQL directory you choose.

The UPGRADE.OUT file contains the following information:

Starting upgrade to 4.2.0 Checking all tables for text data

The following errors are reported in the SQLSERVR.OUT file and the error log for every database in excess of the configured value:

Warning; OPEN OBJECTS or OPEN DATABASES parameter may be too low attempt was made to free up descriptors in release_dbtable. Run sp_configure to increase parameter value. Warning: OPEN OBJECTS parameter may be too low. >>>>>>>>>>>>>>>>>>> Unexpected EOF Hangs SQL Administrator ID: Q91085

SYMPTOMS

When SQL Administrator detects that the named pipe connection to a  server has been terminated before a result is returned on an   outstanding query, it displays a window with an OK button and the message &quot;Unexpected EOF from SQL Server.&quot; If you click the OK  button, the window momentarily disappears, but then returns. You cannot terminate the window and return control to either SQL Administrator or Windows. CAUSE SQL Administrator does not correctly handle the premature termination of a named pipe connection while a query is  outstanding. WORKAROUND The SQL Administrator user must reboot the PC. STATUS Microsoft has confirmed this to be a problem in SQL Administrator version 4.2. This problem was corrected in SQL Administrator version 4.20.1 and SQL Server 4.2a. >>>>>>>>>>>>>>>>>>> Errors 241 and 242 When Calling dbcursorfetch ID: Q87125

SYMPTOMS

When attempting to call dbcursorfetch on a table that has a  unique index that contains a datetime or smalldatetime column, the call returns FAIL and SQL Server returns the following error messages:

SQL Server message 241, state 3, severity 16 Syntax error converting DATETIME from character string

SQL Server message 242, state 3, severity 16 The conversion of CHAR to DATETIME resulted in a DATETIME value out of range WORKAROUND To work around this problem, avoid creating unique indexes on  datetime columns. If the index must contain a datetime value, consider using a char or varchar column to hold the date and time values, as opposed to the datetime or smalldatetime data types. STATUS Microsoft has confirmed this to be a problem in DB-LIBRARY (db-lib) version 4.20.1. This problem was corrected in db-lib version 4.20.21 and SQL Server version 4.2a. >>>>>>>>>>>>>>>>>>> bcp_init Causes GP Fault on Table with Default ID: Q89322

SYMPTOMS

Using bcp_init on a table causes DB-LIBRARY (db-lib) to generate a  general protection fault (GP fault). CAUSE This problem occurs only when a default is bound to a column of the table. The bcp_init function incorrectly handles this case. WORKAROUND Before using bcp_init, unbind any defaults with the sp_unbindefault stored procedure. After the bulk copy operation is complete, bind the defaults again with sp_bindefault. STATUS This problem was corrected in DB-LIBRARY version 4.20.21 and SQL Server version 4.2a. >>>>>>>>>>>>>>>>>>> dbretdata Returns Invalid First Two Characters ID: Q89325

SYMPTOMS

The first two characters of the string returned by dbretdata are invalid. CAUSE This problem occurs only when a stored procedure returns a CHAR or  VARCHAR output parameter. In this case, the dbretdata function incorrectly returns a string in which the first two characters are invalid. WORKAROUND Ignore the first two characters. The correct stored procedure output value begins at the third character of the string returned by dbretdata. STATUS This problem was corrected in DB-LIBRARY version 4.20.21 and SQL Server version 4.2a.
 * }

-

 Additional query words:

Keywords : SSrvGen kbfixlist

Version : 4.2a

Platform : OS/2

Issue type : kbref

"THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED &quot;AS IS&quot; 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.

''