Summary
Making the environment part of the project config is what stops the production accident.
The failure mode with database access is not a malicious query, it is the right query against the wrong environment. Naming the connection, the schemas and the write permission together — and switching them as one unit — means pointing at production is a deliberate act rather than a leftover setting. Automatic rollback on a failed write is the other half: a half-applied change is worse than a rejected one. If you connect a database at all, this is the shape to want.
What it is
A configurable server for Microsoft SQL Server whose central idea is the project: each one names its connection, its schemas and its permissions, and you switch between them.
What you get
- Multiple database connections, switched by project
- Schema-specific access, so a project sees only the schemas it names
- Read, write and delete permissions configured separately per project
- Environment-based setup, so development, staging and production differ by configuration
- Transaction management, with automatic rollback when a write fails
Requirements
The .NET runtime; built and run as a local executable. MIT licensed.