Viken Data Studio freeware tool
Databases Searching Tool
D.S.T. is built for the unglamorous but expensive part of internal data work: the value is known, the location is not, and nobody should have to open every table by hand. It runs locally, searches SQL Server through controlled scopes, keeps credentials out of public output, and turns scattered database inspection into an auditable workflow.
Why it exists
A Viken Data Studio tool for cases where the answer is in the database, but the path to it is not documented.
The product is deliberately narrow: search, inspect, export, remember, and audit. It does not try to become a database admin console, a BI platform, or a place for agents to invent SQL. That boundary is the point.
User-first search
A person starts the local service, chooses one-shot credentials or a saved Search Profile, narrows the database/table/column scope, and gets structured results instead of wandering through tooling.
Backend-controlled scale
Searches run as server-side jobs with IDs, cursors, display limits, cancellation, preflight checks, and exports generated by the backend instead of by a browser trying to hold the whole dataset.
Agent-safe access
Agents can use bearer tokens and approved profiles, but they do not receive SQL credentials, connection strings, direct server configuration, or a raw SQL endpoint.
Interface preview
Search, Results, Schema, Profiles, Agent Access, Memory, and License live as separate tabs.
The screenshots use generic values and no real credentials. The image follows the site theme, so light and dark UI are both represented without faking the application.
Current build
Version 1.2.2-templates, packaged for Windows through PyInstaller and distributed as a ZIP.
Local default
Default startup binds to 127.0.0.1:8765, opens the browser, and keeps Agent API disabled unless explicitly enabled.
Generic templates
Examples use neutral names such as PrimaryDB, Contacts, Documents, Records, ReferenceNo, and ExternalId.
What is actually inside
Not just a form around a SQL login secret.
The current implementation has grown into a local service layer with profile-aware search, memory, export, diagnostics, and agent boundaries. The details matter because they are exactly where data tools usually become unsafe or painful.
Search jobs
User searches start through /search/start, run asynchronously through pyodbc, store limited job state in runtime/search_jobs/, and are paged through signed cursors.
Search Profiles
Profiles define allowed databases, tables, columns, match mode, page size, preview limit, export limit, timeout, history behavior, and agent access.
Credential sources
Profiles use an environment-backed credential source, Windows Credential Manager, or the local encrypted vault. Raw SQL login secrets are not stored in the profile JSON.
Search memory
Search runs, summaries, saved searches, search plans, and workspaces live in local SQLite memory under runtime/memory/dst.memory.sqlite3.
Server-side export
CSV and JSONL exports are written by the backend, with TTL, storage quota, export limits, CSV formula protection, and profile-backed streaming re-query for full exports.
Operational endpoints
/health, /ready, and /diagnostics expose safe runtime status without login secrets, token hashes, connection strings, or full result data.
Use cases
Built for controlled internal lookup work.
D.S.T. fits the practical cases where a team needs to find where a value appears, confirm scope before scanning, export a controlled result set, or let a local assistant continue a search without giving it database credentials.
Contact or identity lookup
Search names, emails, phone fragments, customer numbers, or external IDs across approved tables and columns.
Reference lookup
Use exact matching for invoice numbers, document references, ticket IDs, case numbers, or any value that should not be fuzzy.
Data review support
Use preflight to see how many databases, tables, and columns will be scanned before starting a broad search.
Workspace continuation
Group related searches into a workspace, save useful templates, rerun or refine previous searches, and keep investigation history readable.
Agent-assisted search
Let an approved local agent create structured search plans and execute them through profiles, with no raw SQL and no credential disclosure.
Safe remote operation
Run the service on a company host bound to localhost and reach it through an SSH tunnel instead of exposing a raw service port publicly.
Before you run it
Powerful enough to deserve a careful setup.
D.S.T. is freeware, but it is still a database inspection tool. Use it only where you are allowed to inspect the data, and configure SQL access with least privilege.
- Install Microsoft ODBC Driver 17 for SQL Server on the machine running D.S.T.
- Use SQL accounts with
SELECTpermissions only. - Keep the default bind address
127.0.0.1unless LAN exposure is deliberate and protected. - Use Search Profiles for repeatable work and one-shot credentials for temporary checks.
- Use Schema Explorer instead of blank wildcard searches when you only need metadata.
- Review Agent API status, token permissions, audit behavior, export limits, and history retention before enabling agent workflows.
D.S.T. FAQ
Common questions before downloading the SQL Server search tool.
D.S.T. is built for controlled database lookup work, so the practical questions are about safety, credentials, limits, and agent access.
What is Databases Searching Tool?
Databases Searching Tool is a local Windows search utility for SQL Server databases. It helps users search approved databases, tables, and columns without writing raw SQL.
Does D.S.T. keep SQL login secrets in plain text?
No. One-time search mode does not persist credentials, and saved profiles are designed to keep secrets behind a local credential vault reference instead of exposing raw login material in profile data.
Can an AI agent use D.S.T.?
Yes, when Agent Search API is enabled for a specific profile and token. The agent can send structured search requests, but it cannot see SQL credentials or submit raw SQL.
Is D.S.T. freeware?
Yes. D.S.T. is freeware from Viken Data Studio and is provided without warranty or liability. Paid help is available for training, setup, configuration, and workflow implementation.
License and services
Freeware tool, optional paid implementation help.
D.S.T. is freeware from Viken Data Studio and is provided without warranty or liability. Viken Data Studio can help with training, configuration, profile setup, agent-safe workflow design, and implementation into company internal workflows.
Download
Current public package: Databases Searching Tool.zip.
Documentation
The full public documentation covers startup, search modes, profiles, vault, exports, schema, agent APIs, memory, diagnostics, remote access, and release verification.
Implementation support
Viken Data Studio can help with company setup, workflow implementation, training, profile design, and agent-safe search configuration. Pricing is individual.
Contact
Need D.S.T. configured for a real internal workflow?
Contact Viken Data Studio for training, setup, profile design, safe deployment, and implementation support for company data lookup workflows.