Scribd
Upload
46 views2 pages

Memory Tuning

If SQL Server 7.0 and Exchange Server 5.5 Service Pack 2 are installed on the same computer running BackOffice Server 4.5 or BackOffice Small Business Server 4.5, the minimum dynamic memory setting for SQL Server must be increased from the default of zero to at least 32 megabytes to address a known memory issue when the products co-exist. The SQL Server administrator should determine an optimal memory allocation for SQL Server based on its processing load and the needs of any third-party applications, and explicitly configure the minimum memory setting accordingly.

Uploaded by

4Nisha
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
46 views2 pages

Memory Tuning

If SQL Server 7.0 and Exchange Server 5.5 Service Pack 2 are installed on the same computer running BackOffice Server 4.5 or BackOffice Small Business Server 4.5, the minimum dynamic memory setting for SQL Server must be increased from the default of zero to at least 32 megabytes to address a known memory issue when the products co-exist. The SQL Server administrator should determine an optimal memory allocation for SQL Server based on its processing load and the needs of any third-party applications, and explicitly configure the minimum memory setting accordingly.

Uploaded by

4Nisha
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Simple Memory Tuning is Required if Both SQL Server 7.

0 and
Exchange 5.5 Service Pack 2 Are Installed on BackOffice Small
Business Server 4.5
SUMMARY

If you run both SQL Server 7.0 and Exchange Server 5.5 Service Pack 2 on a computer running BackOffice

Server 4.5 or BackOffice Small Business Server 4.5, you must explicitly configure the memory used by SQL

Server in order to address a known memory issue that occurs when the products co-exist on the same

computer.

The minimum dynamic memory setting for SQL Server 7.0 must be increased from the default of zero to a

value of at least 32 megabytes (MB).

It may be necessary to set the minimum memory for SQL Server higher than 32 MB to support SQL Server's

processing load, as this setting will determine the memory used by SQL when Exchange Server is running

and under load. In this environment, the maximum dynamic memory setting for SQL Server will not be

reached. SQL Server and Exchange Server administrators should determine the amount of memory to be

allocated to SQL Server that will optimize the overall performance of both applications. The SQL Server

administrator must then set the SQL Server minimum memory option to this value. If the SQL Server

database is supporting a third-party application, you may need to consult the application's documentation or

vendor to find out how much memory SQL Server will need to support the application processing load.

MORE INFORMATION

To increase the minimum dynamic memory setting for SQL Server 7.0, follow these steps:

1. Click Start, point to Programs, point to Microsoft SQL Server 7.0, and click Service Manager.

The SQL Server Service Manager dialog box will appear.

2. Make sure that "MSSQLServer" (without the quotation marks) appears in the Services list, click

Start, and then click Continue.

3. When SQL Server has started, click Start, point to Programs, point to Microsoft SQL Server

7.0, and then click Enterprise Manager.

4. In the console tree, expand the Microsoft SQL Servers node, and then expand the SQL Server

Group node.

5. Right-click the node of your SQL Server, and click Properties.

6. Select the Memory tab.


7. Under Dynamically Configure SQL Server Memory, drag the Minimum (MB) memory slider

to the right until it says 32 MB.

8. Click OK, and then close the SQL Server 7.0 Enterprise Manager.

For the new settings to take effect, you must stop and then restart the MSSQLServer service.

This is by design. In SBS, this allocation has already been made.

You might also like