Troubleshooting Microsoft SQL Server collector issues

The catalog collector may run in several seconds to many minutes depending on the size and complexity of the system being crawled.

If the catalog collector runs without issues, you should see no output on the terminal, but a new file that matching *.dwec.ttl should be in the directory you specified for the output.
If there was an issue connecting or running the catalog collector, there will be either a stack trace or a *.log file. Both of those can be sent to support to investigate if the errors are not clear.

A list of common issues and problems encountered when running the collectors is available here.

Issue 1: Lineage relationships do not appear in the catalog output or the logs

Cause: Permissions are not set properly.
Solution: Check that the user has permissions to retrieve view definitions.
1. Within SQL Server, run the following query:
```
select VIEW_DEFINITION from INFORMATION_SCHEMA.VIEWS 
where TABLE_SCHEMA='<schemaName>' and TABLE_NAME='<viewName>'
```
  Replace <schemaName> and <viewName> with a known View in a Schema.
2. The result set should include the expected View.
3. If not, run the following query to grant View Definition to the user that the collector authenticates with.
```
GRANT VIEW Definition TO <user>
```

Cause: The user used for running the collector cannot execute the built-in SQL Server stored procedure, sp_spaceused, to obtain the table size.
Solution: Ensure that proper permissions are set to run sp_spaceused.

In this section: