# Microsoft SQL Server rules

Extract Tables: When enabled, NodeGraph gathers tables and fields definitions from the system table, together with some metadata surrounding them.

Table Category: Choose from the categories created in [Categories](https://help.qlik.com/en-US/nodegraph/Content/NodeGraph/Documentation/Visualization_settings.htm#CATEGORI) or create a new category via the built-in sub-menu.

Extract Views: When enabled, NodeGraph goes through the defined views in the database, and parses the definitions.

* Create view dependencies: If enabled, NodeGraph analyzes the SQL statements in the view definitions and generates lineage on field level to other database entities.

* View Category: Choose from the categories created in [Categories](https://help.qlik.com/en-US/nodegraph/Content/NodeGraph/Documentation/Visualization_settings.htm#CATEGORI) or create a new category via the built-in sub-menu.

Extract Procedures: When enabled, NodeGraph goes through the defined procedures in the database, and parses the definitions.

* Create procedure dependencies: If enabled, NodeGraph analyzes the SQL statements in the procedure definitions and generates lineage on field level to other database entities.

* Procedure Category: Choose from the categories created in [Categories](https://help.qlik.com/en-US/nodegraph/Content/NodeGraph/Documentation/Visualization_settings.htm#CATEGORI) or create a new category via the built-in sub-menu.

Extract Functions: When enabled, NodeGraph goes through the defined functions in the database, and parses the definitions.

* Create function dependencies: If enabled, NodeGraph analyzes the SQL statements in the function definitions and generates lineage on field level to other database entities.

* Function Category: Choose from the categories created in [Categories](https://help.qlik.com/en-US/nodegraph/Content/NodeGraph/Documentation/Visualization_settings.htm#CATEGORI) or create a new category via the built-in sub-menu.

Include Databases: A semicolon separated list of databases to act upon with the above ruleset. Does not support wildcard.

Schema Filter: The schema filter is used to decide what schemas to include. For example, you could use the definition \*.dbo.\* ; AdventureWorks.Sales.\* to gather all tables from the dbo schema of all your databases, but also the tables from the Sales schema on the AdventureWorks catalog.

[](https://help.qlik.com/en-US/nodegraph/Content/NodeGraph/Documentation/Using_NodeGraph/Rules/Microsoft_SQL_Server_rules.htm)

#### Full list of rule fields

Add a Microsoft SQL Server rule

| Field | Default Input |
| --- | --- |
| SELECT RULE TYPE | Database rule |
| NAME | Enter a name for this rule |
| DESCRIPTION | Description (optional) |
| TABLE CATEGORY | Select category or add new |
| VIEW CATEGORY | Select category or add new |
| PROCEDURE CATEGORY | Select category or add new |
| FUNCTION CATEGORY | Select category or add new |
| INCLUDE DATABASES | Db1; Db2; ... |
| SCHEMA FILTER | AdventureWorks.dbo.\*; ... |
| RULE PRIORITY | Enter a processing priority for this rule |