Trace is enabled per user on the system for all applications using the Mimer.Data.Client library. The trace configuration can be modified during runtime, making it possible to enable trace, disable trace, or modify the trace settings while the application is running. Mimer.Data.Client will automatically detect changes in the configuration file. Trace can be enabled through the Mimer SQL Data Provider Trace Control tool. When at least one trace category has been selected, and the configuration is saved, a config file will automatically be created at the correct location.

Trace can be enabled manually by doing the following:

1. If it does not already exist - create a directory called MimerSQLDataProvider in Environment.SpecialFolder.LocalApplicationData. The application data directory is located, by default, in the following locations:

   Windows	C:\Users\<user>\AppData\Local
   Linux	~home/.local/share
   Mac	/Users/<user>/.local/share

2. Create a file called MimerTrace.config in the MimerSQLDataProvider directory. For example, for the user Abc on Windows, the trace file is called: C:\Users\Abc\AppData\Local\MimerSQLDataProvider\MimerTrace.config
3. Enter your trace configuration in the MimerTrace.config file. Read more about the trace configuration in Configuring trace and Configuration file examples.
4. Optional: Modify connection string(s) using 'AllowedTraceLevel'. AllowedTraceLevel is by default set to 'safe'. It can be set to 'confidential' to trace data that may contain sensitive information such as SQL statements and parameters, or set to 'none' to disable trace on a connection. See Connection string options affecting trace for details.