ServersConfiguring SMS Provider MaxSQLConnections

Configuring SMS Provider MaxSQLConnections





by Dana Daugherty

The SMS Provider comes with a default setting of 60 connections.
It’s a little known fact  that even though you change this
setting on the GUI setup program when you install an SMS Site server
the value stays at 60. It may even be more of a secret that you need
to change this setting again after the SP2 upgrade. This
setting needs to be adjusted based on the number of Admin Consoles
in your enterprise. In this article I’ll show you how to do
that.
The SMS Provider comes with a default setting of 60 connections. It’s a little known fact that even though you change this setting on the GUI setup program when you install an SMS Site server the value stays at 60…

Below are instructions for modifying
the MaxSQLConnections in SMSProv.mof, then instructions for
recompiling it. Each open Admin console needs 5 connections and if
you have a lot of Collections that are being updated andor
enumerated each time a console is opened that will use even more
connections.

1. Modify MaxSQLConnections=60
in SMSProv.mof file.This file is located on SMS
site server , SMSbini386 or SMSbinAlpha.

2. By using a text editor, open this
file. Then locate the following lines.

/
*************************************

// SMS_ConfigData : SMS Provider
Configuration data

//
*************************************

[singleton]

class SMS_ConfigData

{

// Number of instances returned
as a batch to CIMOM for query results

[Description(“Undocumented – do not
change”)]

uint32 QueryInstanceBatchCount = 0;

// Max number of SQL connections
allowed at one time by the provider

[Description(“Undocumented – do not
change”)]

uint32 MaxSQLConnections = 60;

};

By default, MaxSQLConnections is
equal to 60. It should be changed to a higher number depending on
how many SMS Administrator console users you have. Even if a higher
number ( Default connection= 75) is entered during the SMS
installation, it does not update the number in this file. This should be
updated manually.

After change is made, this file must
be compiled. To do that:

Stop the Windows Management service
and:

Step 1. Locate mofcomp.exe. it is
located in %windows%System32WBEM.

Step 2. Execute the following command:

Mofcomp smsprov.mof

Step 3. The output from the command
should look like the following.

Microsoft (R) 32-bit MOF Compiler
Version 1.10.698.0000

Copyright (C) Microsoft Corp. 1997.
All rights reserved.

Parsing MOF file: smsprov.mof

MOF file has been successfully parsed

Storing data in the repository…

Done!

**********************************************************

Note: this info was sent to me by a
Microsoft Support Engineer.

Latest Posts

Related Stories