Browse and edit SQL Server data
Implementation-neutral SQL Server browsing guidance with rowversion checked edits and no invented UI claims.
Tablyne browses SQL Server databases, schemas, tables and views while keeping the connection and relation context visible.
Browse the relation
A SQL Server client needs to discover databases, schemas, tables and views, then load a bounded page of rows. Browsing preserves the connection and relation context while the user moves between the object tree, result grid and query console.
Tablyne keeps identity information separate from display values. A primary key or another declared identity is needed to address an edit safely. Row order alone is not a write identity.
Stage the edit
The intended edit sequence is:
- Load the row and capture its
rowversion. - Change only the intended fields.
- Show the generated
UPDATEorDELETEfor review. - Commit with the identity predicate and the captured version.
- Reject the batch if the current
rowversionno longer matches.
A concurrent change is never resolved by silently replacing the current row. The write is refused and the newer server value stays available, so you can reload and decide again.
Same review as the other SQL engines
SQL Server edits follow the same review-first flow as Postgres, MySQL and SQLite. Rows are identified by their key, never by display values or row order.
Use the query console to run the current statement after reviewing its target.