Try Free
Documentation

SQL Server Build Info

SQL Server Build Info

The DB Server Info activity is a one-page dashboard that tells you exactly what you are connected to. It reports the product name, version, JDBC driver, connection URL, feature support flags, and a per-database size table — enough to answer "which server is this?" and "what does it support?" without leaving VisuaLeaf.

Quick Start

  1. Right-click a SQL connection in the sidebar and choose DB Server Info.
  2. Review the info cards: Database Product, Version, JDBC Driver, User, Max Connections, etc.
  3. Scan the Feature Support chips for capabilities like Transactions and Stored Procedures.
  4. Inspect the Databases table for size, table counts, and per-database metadata.
DB Server Info for Verdant Market (PostgreSQL): info cards for PostgreSQL 16.14, the JDBC driver 42.7.13, 8192 max connections, the JDBC URL and user, four green Feature Support chips, and a Databases table listing three databases totalling 2.17 GB

Info Cards

A grid of nine cards summarizes the server. Each card has an icon, a label, and a value:

Top row of info cards under the PostgreSQL badge: Database Product PostgreSQL highlighted in accent color, Version 16.14 (Debian 16.14-1.pgdg13+1), and Major / Minor 16.14
CardWhat it shows
Database Producte.g. PostgreSQL, MariaDB, Microsoft SQL Server. Highlighted in accent color.
VersionFull product version string reported by the driver.
Major / MinorParsed major.minor version numbers.
JDBC DriverDriver name (e.g. PostgreSQL JDBC Driver).
Driver VersionDriver's own version string.
Max ConnectionsServer-side connection ceiling.
Max Statement LengthMaximum size of a single SQL statement the driver will accept.
JDBC URLThe exact JDBC URL VisuaLeaf used to connect.
UserThe authenticated username reported by the server.

Feature Support

Below the cards, a row of chips answers common capability questions at a glance:

Max Statement Length, JDBC URL jdbc:postgresql://localhost:55532/verdant_market and User cards, above the Feature Support chips Transactions, Batch Updates, Stored Procedures and Full Outer Joins, all green
  • Transactions — supports BEGIN/COMMIT/ROLLBACK.
  • Batch Updates — supports batched execution via addBatch()/executeBatch().
  • Stored Procedures — supports CALL / EXEC.
  • Full Outer Joins — supports FULL OUTER JOIN.

Green chips indicate supported features, red chips indicate unsupported ones.

Databases Table

The lower table enumerates every database (or schema, depending on dialect) accessible on the server. Columns are shown or hidden based on whether the driver returns data for them:

ColumnMeaning
NameDatabase identifier.
SizeHuman-readable size (B/KB/MB/GB).
TablesCount of tables in the database.
CharsetDefault character set (MySQL/MariaDB).
CollationDefault collation.
OwnerOwning role (PostgreSQL).
EncodingStorage encoding (PostgreSQL).
CommentFree-form description.

The header shows the aggregated total size across all databases.

Reading the JDBC URL

A typical JDBC URL looks like:

jdbc:postgresql://db.internal:5432/analytics?sslmode=require&ApplicationName=VisuaLeaf

Use it to confirm which host, port, and default database you are actually connected to — especially handy when juggling multiple environments with similar aliases.

Common Use Cases

  • Confirming the running server version before filing a bug against a specific patch level.
  • Answering "does this server support stored procedures?" without SELECT version().
  • Identifying the biggest databases on the server at a glance.
  • Verifying you are pointed at the intended environment before running destructive DDL.

Ready to try VisuaLeaf?

Download and start managing your MongoDB and SQL databases with ease.

Download Free Trial