Wharfbase
SQL Server
SQL Server databases are found in containers by their image.
| Plan | Pro and Team |
| Default ports | 1433 |
| Also recognized | Azure SQL Edge |
| Credential hints from | MSSQL_SA_PASSWORD, SA_PASSWORD, MSSQL_SA_PASSWORD_FILE |
| Data in the container | /var/opt/mssql |
What you can do
Section titled “What you can do”Browse and edit tables and views, the T-SQL editor with Explain (showplan), exports. Read-only scripts run in a transaction that is rolled back, and statements that write or end the transaction are refused anywhere in a batch.
A least-privilege user
Section titled “A least-privilege user”Wharfbase works with any user; give it only what you want it to do.
Read only
Section titled “Read only”CREATE LOGIN wharfbase_ro WITH PASSWORD = '…';USE app;CREATE USER wharfbase_ro FOR LOGIN wharfbase_ro;ALTER ROLE db_datareader ADD MEMBER wharfbase_ro;GRANT VIEW DEFINITION TO wharfbase_ro;Read and write
Section titled “Read and write”Add ALTER ROLE db_datawriter ADD MEMBER wharfbase_rw;.
For other features
Section titled “For other features”- Live consumers:
USE master; GRANT VIEW SERVER STATE TO wharfbase_ro;
A function that writes in its own transaction still looks like a read: for a hard guarantee, use a user with read grants only (above).