Note that there are some explanatory texts on larger screens.

The database sent an unexpected error, this is likely a bug.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server: Could not open a connection to SQL Server)

Querying!

Guidance

The root

At the root of the database, you see a list of tables with a few of their rows loaded - but presented as cards side-by-side. Some of those "rows" will have further related data already loaded for better orientation.

How much data is loaded is decided entirely by a fixed set of heuristics - SQuiL has no special logic or configuration to cater to a specific database schema. It simply recurses all table relationships and takes an educated guess at what and how much data would be appropriate.

Likewise, the names for the rows are derived from a suitable column, and the two-letter code that precedes the name (the "tag") is derived from the table name. These are not hard-coded to the specific schema you're looking at.

That's what makes SQuiL unique: As long as your database schema is well-designed, a semi-decent browsing experience just drops off without any further work.

Try navigating to a specific row by clicking on a tag or name. (This is only possible when the respective table has a primary key.)