SQL Server with Windows Authentication
Pick the auth mode in the SQL Server connection form and add a domain when you need one, instead of being forced onto a SQL login. Connection strings that already say `authentication=windows`, `trusted_connection` or `integrated security` fill the form in correctly, and copying one back out keeps it.
Screenshot coming soon
Why You Need This
How this feature boosts your daily productivity
On a domain-joined machine, Windows Authentication is usually the only way in that the DBA will approve — SQL logins are the exception granted grudgingly, if at all. A client that only speaks SQL logins is not a client with a missing option; it is a client you cannot use against your own company's database. Putting the auth mode in the form makes the supported path the obvious one, and honouring the domain field means the accounts that need one are not a special case you have to hand-edit a connection string to reach. The round-trip matters just as much: connection strings are shared in tickets, runbooks and chat messages, so one that arrives saying trusted_connection has to arrive as a working connection, and one you copy back out has to still say it when a colleague pastes it. Losing the auth mode in either direction turns a paste into a silent downgrade to a login that will not work.
How It Works
Get started in 4 simple steps
Open a SQL Server connection
Add or edit a SQL Server connection in the database client.
Choose the auth mode
Pick Windows Authentication instead of a SQL login in the connection form — the path a domain-joined machine usually has to take.
Add a domain if you need one
The domain field is there for accounts that require it, instead of being a special case you hand-edit a connection string to reach.
Paste a connection string instead
A string that already says `authentication=windows`, `trusted_connection` or `integrated security` fills the form in correctly, and copying one back out keeps it.
Without 1DevTool
The manual way vs. the 1DevTool way
The Hard Way
The 1DevTool Way
Key Capabilities
Everything included with SQL Server with Windows Authentication
Why It Matters
The productivity impact of having database client built into your workspace
Domain-Joined Machines Can Connect
Windows Authentication is the path the DBA approves; supporting it is the difference between using the client and not.
No Hand-Edited Connection Strings
The auth mode and domain are fields in the form, not something you work around by rewriting a string.
Pasted Strings Arrive Working
A string from a ticket or runbook saying trusted_connection parses into the right mode instead of silently downgrading.
Copies Stay Shareable
Copying a string back out keeps its auth mode, so the colleague who pastes it gets the connection you had.
More in Database Client
Other features in this category you might find useful
13 Database Engines
Connect to PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch, ClickHouse, Cassandra, SurrealDB, Weaviate, InfluxDB, Kafka, CouchDB, and MSSQL.
Query Editor & Results
SQL editor with syntax highlighting, auto-formatting, multi-tab workspace, and exportable result grids.
Schema Browser
Browse table schemas, preview data, and filter tables. Edit rows directly in the results grid.
Database Workspace Table List
Use a tabbed database workspace with a connection rail, table list sidebar, and query tabs so schema browsing and SQL editing happen in one place.
Ready to boost your workflow?
Download 1DevTool for free and experience SQL Server with Windows Authentication along with 294 other features — all in one app.