SQL Server Deadlock While Reading Schema Metadata

Example

Failed to establish database connection: SQL Server deadlock victim while reading schema metadata.

Meaning

Textura connected to SQL Server, but the database chose the health check query as the deadlock victim while reading database schema information.

Possible Cause

The SQL Server had competing database activity at the same time.
Another process was locking metadata or schema-related resources.
The database was under heavy load.
Maintenance, reporting, or batch activity caused locking conflicts.
The issue may be temporary and resolve on retry.

Recommended Resolution

Ask your database administrator to review SQL Server locking, blocking, and deadlock activity around the time of the error.

If this happens only once, it may be safe to retry. If it happens repeatedly, contact Textura Support and your database administrator for deeper review.

Next Topic: SQL Server Connection Refused