Microsoft KB Archive/67622

{|
 * width="100%"|

-

The information in this article applies to:


 * Microsoft SQL Server for OS/2, version 4.2

-

SYMPTOMS
SQL Server fails to start and prints a row of dots similar to the following:

  ...........................................   ...........................................   ...........................................   ...........................................   .....

In some cases after an extended period of time you may see the following message:

The SQLSERVER service could not be started. NET3062: The sub-service SQL Server failed to start. More help may be obtained by typing NET HELPMSG 3062.

CAUSE
This pattern of long dots usually indicates a problem with memory allocation. SQL Server is in fact starting up; however, instead of printing a couple of dozen dots as usual it prints a couple of hundred dots. In this state the system may run for hours without SQL Server completing its startup.

WORKAROUND
If this problem occurs please check the following items:

 ERRORLOG

Examine the SQL Server error log for any relevant messages which could indicate the reason for the failure of SQL Server to start. The SQL Server error log is usually on C:\SQL\LOG. LANMAN ERROR LOG.

Examine the Lan Manager errorlog for any relevant messages as well. You may examine the Lan Manager error log using the NET ADMIN utility. CONFIG.SYS

If any change has been made to the cache size in the CONFIG.SYS file, it can have a dramatic impact upon memory thrashing. Thrashing is a condition where memory is being constantly swapped and very little work actually gets accomplished. We recommend setting the cache to its minimum allowable value which is 256 for HPFS and 64 for FAT. We also recommend turning lazy write = off.  SQL Server configuration options

Any changes made to SQL Server configuration options using either the sp_configure stored procedure, or the Microsoft SQL Administrator can have a dramatic effect. The following are some relevant SQL Server configuration options:

     User Connections Memory Procedure Cache Open Databases Open Objects Locks Setting these parameters incorrectly can force Microsoft SQL Server for OS/2 into a state where it will not be able to run effectively. If you suspect this to be the case follow the procedure below in order to reset these values to their defaults:

 Stop SQL Server by issuing &quot;net stop sqlserver&quot; from an OS/2 command prompt. Change directories to \SQL\BINP. Enter &quot;bldmastr /d c:\sql\data\master.dat /r /C&quot;,

/d specifies the complete path to the master.dat file

/r indicates that bldmastr should reset the config block only.

/C means that this is a case-insensitive installation. Omit

this parameter if this is a case-sensitive server.</li> After bldmastr has completed shut down OS/2 and reboot the computer.</li> Restart OS/2 LAN Manager and SQL Server.</li></ol> </li></ol>

MORE INFORMATION
For more information refer to the bldmastr documentation in the Microsoft SQL Server &quot;System Administration Guide.&quot;

Keywords         : kbprint SSrvGen Version          : 4.2 Platform         : OS/2 Issue type       :
 * }