The first tool is the Manual Logging Mode. This tool allows easy enabling of several types of logging:
- SQL Logging – SQL Logging tracks all communication between the Microsoft Dynamics GP client and the SQL Server. The default file in which the SQL communication is stored is named DEXSQL.LOG.
When enabled, SQL Logging is on a workstation basis. On a standalone PC, this logging is easy to use and interpret, but on a terminal or Citrix server, all instances of a running client will be recorded, which can make debugging a specific issue for a single user much harder.
Other methods of communicating with the SQL Server, such as ADO (ActiveX Data Objects) which is used by Visual basic for Applications (VBA), are not logged.
- SQL Profile Tracing – SQL Profile Tracing can be used to log all activity at the SQL Server, including commands from inside Stored Procedures. The default file in which the SQL Profile Trace is stored is named Trace.trc.
SQL Profile Tracing will capture all activity at the SQL Server for the current user in the system database (typically called DYNAMICS) and the current company database; this means that, unlike SQL Logging, SQL Profile Tracing will record all communication with the SQL Server, including ADO as used by VBA.
SQL Profile Tracing is not enabled by default, but needs to be configured first; in the next post, I will cover the configuration using recommended settings.
- Dexterity Script Logging – Dexterity Script Logging tracks all Dexterity event script, procedure and function calls, including the script hierarchy. The default file in which the script log is stored is named Script.log.
Dexterity Script Profiling – Dexterity Script Profiling tracks the number of calls to each event script, procedure and function and how much time the calls have taken. It also tracks all table activity initiated by Dexterity and the time taken. The default file in which the script profile is stored is named Profile.txt.
- Macro Recording – Macro Recording captures all activity performed by the user in the application. this activity is stored in a file called Macro.mac which can be opened in Notepad, which allows for analysis of the users actions and is useful in showing steps which the user didn’t relay when reporting the problem.
Macro recording will only work foe a single user; in a shared client environment, such as on a terminal or Citrix server, this means the first instance launched.
Macro recording is only available in the desktop client.
The logging is not provided by GPPT, but is standard functionality which GPPT allows to be easily enabled; without GPPT, enabling them involves several Dex.ini switches.
UPDATE: Winthrop DC have reminded me that the SQL Profile Tracing is functionality provided by GPPT; it is the other four types of logging are standard.
Logging is a functionality which should be used sparingly, as there is a processing “overhead” which can cause speed issues; logging should only be used when investigating a specific issue.