Documentation

Browsing datasets with DBeaver

Connect DBeaver, a free GUI SQL client, to a DataNivra target environment so you can inspect provisioned test data without writing SQL in a terminal.

What is DBeaver?

DBeaver Community is a free, open-source GUI database client that runs on Windows, macOS and Linux. It supports PostgreSQL, MySQL, Oracle, MS SQL Server and dozens of other databases. If your team is not comfortable with a terminal SQL prompt, DBeaver gives you a point-and-click interface for the same queries.

Prerequisites

  • DBeaver Community Edition installed on your workstation (download)
  • A provisioned DataNivra dataset in a target environment you can reach from your workstation
  • The target's read credentials (host, port, database name, username, password)

If you are using DataNivra's credential injection, the credentials are inside the agent network, not on your workstation. Ask your administrator for a read-only direct-access set, or use a bastion/tunnel.

Connect to a PostgreSQL target

  1. Open DBeaver. In the Database menu click New Database Connection.
  2. Select PostgreSQL from the list and click Next.
  3. Fill in the connection details:
FieldValue
Host<your-target-host>
Port5432 (default)
Database<your-database-name>
Username<read-only-user>
Password<password>
  1. Click Test Connection to verify. Click Finish.

Browse provisioned test data

After connecting, expand Databases → \<your-database\> → Schemas in the left panel. Navigate to the schema DataNivra provisioned the dataset into (shown on the dataset detail page in the console under Target environment).

Right-click any table and choose View Data to see the first 200 rows. Use SQL Editor → Open SQL Script (Ctrl+]) to write arbitrary queries.

Inspect masking and synthetic quality

DBeaver makes it easy to spot-check masking:

  1. Find a column that should be masked (e.g. email, phone, ssn).
  2. Right-click the column header and choose Filter → Filter by value to scan for patterns.
  3. Confirm that original production values are absent and replaced by realistic synthetic values.

You can also compare row counts between source and provisioned dataset:

-- Count rows in a masked table
SELECT COUNT(*) FROM <schema>.<table>;

-- Check for obviously real email domains that should have been masked
SELECT COUNT(*) FROM <schema>.customers WHERE email NOT LIKE '%@example.%';

Export results to CSV or Excel

Right-click any query result or table, choose Export Data, select CSV or XLSX, and follow the wizard. All processing stays on your workstation — no data leaves to DataNivra Cloud. For scripted or automated export from the agent, see Exporting datasets to files.

Troubleshooting

SymptomLikely causeFix
Connection refusedTarget host not reachable from workstationUse an SSH tunnel or bastion; check firewall rules
Authentication failedWrong credentialsVerify with psql -h <host> -U <user> -d <db> from the terminal
SSL connection requiredServer enforces TLSIn the DBeaver connection dialog → SSL tab → check Use SSL
Schema not visibleDataset not provisioned yet, or wrong schema nameCheck the dataset status in the DataNivra console; schema name is on the dataset detail page

← All documentation