INF: sp_configure Parameters Affect Memory Usage by SQL Server

Last reviewed: April 3, 1997
Article ID: Q61792

The information in this article applies to:

  - Microsoft SQL Server versions 4.2 for OS/2

There are certain parameters (for example, sp_configure parameters) that effect the minimum amount of memory required by SQL Server. You should be aware of their effects on memory, and set the values only as high as needed. This will conserve memory, making more memory available for cache, and improve performance.

Below are the relevant parameters for SQL Server version 4.2. This information is also applicable to versions 1.1 and 1.11; however, the devices parameter is not used in those versions.

   Parameter           Value
   ---------           -----

   user connections    37K per user

   locks               32 bytes per lock (1000 locks costs about 32K)

   open objects        70 bytes per object (100 objects cost about 7K)

   open databases      About 1K (908 bytes) for each

   devices             About 41,400 bytes (21 pages) per device

Additional query words: 4.20
Keywords : kbprg SSrvAdmin
Version : 4.2
Platform : OS/2

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.

Last reviewed: April 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.