Applies to version: 8.x; Author: Kamil Nędza
Using BPS Designer Studio, it is possible to easily view logs directly, without launching SQL Server Management Studio. Using the ‘View logs’ tool is the recommended method of loading and viewing logs, due to the fact that the table containing logs may store them in compressed form – which makes them unable to be viewed in SQL Server Management Studio
Click Tasks -> Administration tools. This will open the administration tools window.
Fig.1. ‘View logs’ tool main window
The query prompt can be used to enter any query which can obtain appropriate data. By default, the prompt suggests a query which is used to load all logs based on the ID of an action. In the case presented below, the query will return all logs for the workflow element with an ID of 3009:
Fig.2. Loading logs for the element with an ID of 3009
Clicking “Get data” will load and display log in table form:
Fig.3. Result of loading logs
Logs obtained this way can be further narrowed down using the additional filter. In the example below, we narrow down the logs of document ID 3009 to those created after the 24th of February 2016, 15:15:33.
Fig.4. Example of the additional filter being used
Fig.5. Result of loading logs with the additional filter in place
The final result can be saved as xls or xlsx spreadsheet by clicking “Export o Excel”,
Fig.6. Exporter window
For comparison, here is a query presented in SQL Server Management Studio.
Fig.7. Example of log view in SQL Server Management Studio
Take a look at the LOG_AdditionalMessage column, which contains information about executed actions. If the message content is long, it will be compressed and the only possibility of viewing it is through WEBCON BPS Designer Studio. The below screenshot shows that logs which show up as NULL in SQL Server Management Studio actually contain values when viewed in Designer Studio:
Fig.8. Compressed columns show up normally in WEBCON BPS Designer Studio
Compressing historical logs
If you happen to have a considerable amount of historical records, it might be worthwhile to compress them. This will free up disk space to some degree. If the system finds that it contains historical logs, it will display a message informing you that the table contains uncompressed data. Choosing to check the logs will cause the system to verify how many records are uncompressed. Clicking Compress will cause the system to begin compressing logs.
Fig.9. After verifying the number of uncompressed logs
The screenshots below show how much space can be saved on a small database after compressing 435 records:
Fig.10. Space used by the log table before compression
Fig.11. Space used by the log table after compression