How to Enable SQL Trace Logging for Reverse Engineer?
SQL Trace logging records each query and the number of results returned for each statement run by Data Modeler during the Reverse Engineering process. This information is useful for investigating errors occurring or any unexpected results returned during the Reverse Engineering process.
Steps:
To enable SQL Trace logging…..
1- In the Tools menu, select Options
2- In the resulting window, open the Diagnostics tab. Enable the SQL Trace logging and optionally specify a logging location...
3- Perform a Reverse Engineer as normal.
The resulting log will be named ERwin SQL Trace <Date> <Time>.txt This log will start with database type chosen. For example...
--This file is published using to trace the executed SQL
--ERwin RE SQL Trace for SQL Server 2016/2017/2019 started on <Date>
Subsequent logging will have a comment indicating the type of object being queried, followed by the statement run and the number of rows returned. Here is an example for SQL Server Triggers...
--[2020-07-06 12:00:09] Trigger Objects
SELECT 1075839021, 1073742126, name,
1075839021, 1075849133, object_id
FROM sys.server_triggers
--[2020-07-06 12:00:09] Return from Query - 0 rows
In the example above "SELECT 1075839021, 1073742126, name,1075839021, 1075849133, object_id FROM sys.server_triggers" was run with 0 results.
If the number of results returned does not seem correct, we recommend running the same query using the same user in another database client such as SQL Server Management Studio, SQLPlus, etc. If the results are the same, it is likely the the user running the query does not have access to the desired objects. For any questions or concerns though, please contact erwin Support.
