Skip to main content

Preflight checks for Microsoft SQL Server

TL;DR

Before [running the Microsoft SQL Server crawler](/apps/connectors/database/microsoft-sql-server/how-tos/crawl-microsoft-sql-server), you can run [prefli.

Connect

Before running the Microsoft SQL Server crawler, you can run preflight checks to perform the necessary technical validations. The following preflight check will be completed:

Database and schema check​

✅ Check successful

❌ Check failed for $missingObjectName

Miner​

Did you know?

Once you have crawled assets from Microsoft SQL Server, you can mine query history. The miner reads SQL Server's Query Store directly - there is no export, upload, or S3 step.

Before running the miner, verify on each database you want to mine:

  • Query Store is enabled with QUERY_CAPTURE_MODE = ALL (always on for Azure SQL Database / Managed Instance; off by default on the box product).
  • The crawler login has VIEW DATABASE STATE so it can read the Query Store catalog views.

Both are covered step by step in Mine Microsoft SQL Server.

When preflight fails before any check runs​

Preflight can also fail at the connection level - before the checks above execute. The wrapper messages are misleading; find the innermost error in the workflow logs and match it in Troubleshooting SQL Server connectivity: HYT00 (no network path), 08001 (firewall/middlebox reset - not TLS), or Login failed (grants or a network error in disguise).