Untitled Document

In some menu paths in Exact Macola ES it takes a very long time to get the information on the screen, what can we do about it?

When troubleshooting performance problems it is very important to identity where the problem is, since it can have several causes.

Follow the links below for a complete detail of instructions:

1. Check the Hardware...(more detail)
Performance problems can consist of one or more of the following:

Hardware problems: Hardware components could be malfunctioning. Faulty components can cause severe performance problems.

Hardware capacity: You might be exceeding the capacity of the system components. You might need post capacity planning or to reconfigure existing hardware.

Application problems: SQL statements might be inefficient, causing excessive usage of system resources.

2. Check the SQL Server and the database...(more detail)
There are several ways to improve the performance of a SQL Database and of the SQL Server, the scope of this document is to give an overview of all possibilities:

A. Switch off auto shrink in the properties of the database;

B. Make sure SQL does not use all memory of the server;

C. Make sure the statistics are up to date and that they are regularly updated via a SQL job;

D. Defragment indexes on a regular basis;

E. Switch autogrowth from percentage to megabytes for databases that grow rapidly.

3. Check slow and long running SQL queries ...(more detail)
In order to troubleshoot slow SQL Queries, it is important and necessary to first determine which SQL Query is slow. Therefore you need to run a profiler trace to determine this. Follow the steps below to set this up:

1.- Download the attached file and save it in the folder "C:\Program files\Microsoft SQL Server\80\Tools\Templates\SQL Profiler". (The assumption is made here that Microsoft SQL Server is installed in the default folder, if this was changed during installation the file needs to be stored on this location);

2.- Go to [Start, Programs, Microsoft SQL Server, Profiler];

3.- In the SQL Profiler go to [File, New, Trace] and connect to the correct SQL Server;

4.- Set the correct options for the trace:

a.- open template "performance test":
b.- enter a clear trace name:
c.- it is possible to save the trace in a SQL Table, so it can be analyzed with the Query Analyzer. This is very usefull. It is advisable to store this table in the database where the peformance issue was tested, because than the whole database can be send to Exact and all the necessary data is available.Also store the trace in a normal trace file (extension is TRC), because that is needed as well.

For more comprehensive instrustions follow the links to our website: (Hardware) - (Database) - (Queries)

Have a question reguarding the above information please feel free to contact us: info@msmpc.com