Performance Impact Considerations - Blackberry ENTERPRISE SERVER FOR IBM LOTUS DOMINO - - PERFORMANCE BENCHMARKING GUIDE Manual

The benchmarking was only conducted using Microsoft SQL 2000. The impacts to Microsoft SQL Server 2005
should be similar. There was also no analysis completed with Microsoft SQL Express 2005. Microsoft SQL Express
2005 is the replacement for MSDE 2000.
Because Microsoft SQL Server and MSDE handle their own memory management, the number of committed bytes
is not a reliable indicator of the amount of memory required by the system. A better measurement indicator
involves viewing the pages /sec, average disk queue length, or disk time percentage. If memory is a bottleneck,
there might be more disk activity, which might result in performance bottlenecks.
During the performance testing, the BlackBerry Manager was closed, which enabled the connection count to be
higher than if the BlackBerry Manager was open or if multiple BlackBerry Managers were open.
If auto refresh is enabled, the BlackBerry Manager queries the BlackBerry Configuration Database at a rate that
might result in a larger impact on the BlackBerry Configuration Database, depending on the rate set and the
number of BlackBerry Managers that are open.

Performance impact considerations

If you use Microsoft SQL Server 2000 with the BlackBerry Enterprise Server, perform the following actions:
• Verify that the Microsoft SQL Server can handle an increase in CPU use and input and output (I/O) activity,
particularly when the BlackBerry Synchronization Service is enabled.
• Verify that the Microsoft SQL Server has enough disks to handle additional disk I/O traffic imposed by
requests from the BlackBerry Enterprise Server on the BlackBerry Configuration Database.
Tip: To verify the disk subsystem I/O bandwidth, monitor the average disk queue length or disk time
percentage and, if using a SAN, seconds per transfer.
• Verify that no processor or I/O bottlenecks exist.
• If you use MSDE, verify that the load does not result in large hits to the MSDE workload governor. The Event
Viewer displays how many times the workload limit of eight concurrent requests is exceeded and by how
much.
• Use the DBCC CONCURRENCYVIOLATION command to determine how often the workload governor is
activated. The workload governor injects artificial delays to control the amount of work that can be done
concurrently. If the workload governor is impacted frequently, consider upgrading to Microsoft SQL Server
2000. Visit www.msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
for more information about the workload governor.
• If you use MSDE, verify that there are no warnings indicating that you are reaching the 2-GB limit. If you are
approaching the 2-GB limit, upgrade your BlackBerry Configuration Database to Microsoft SQL Server 2000.
MSDE performance is site-specific and you should monitor it consistently. There is a store procedure that
monitors the database size for the BlackBerry Configuration Database every Sunday at 5:00 AM and
generates an event in the Event Viewer if the database size exceeds 1.5 GB.
7: Microsoft SQL Server 2000 performance test results
39