Cloud SQL for SQL Server

Cloud SQL for SQL Server is Google Cloud running Microsoft SQL Server for you. AddisDB connects over TDS on port 1433 with its SQL Server driver, so T-SQL batches, DMV-based monitoring and identity-aware mock data all work as they do against any other SQL Server.

Who it is for

It fits teams with an existing SQL Server estate moving to Google Cloud, or anyone who needs T-SQL and SQL Server semantics specifically. Licensing is bundled into the instance price, which is often the deciding factor against self-hosting.

The edition you pick at creation is not cosmetic — it sets the ceiling on cores and memory, and some features are Enterprise-only. Changing it later means rebuilding the instance.

Set up the instance

1. Create a Cloud SQL instance with the SQL Server engine and choose an edition.
2. Under Connections, add your IP to the authorized networks, or plan to use the Cloud SQL Auth Proxy.
3. Note the sqlserver user’s password — that is the administrative login Cloud SQL creates.
4. Create your own database rather than working in master; the managed instance treats the system databases as its own.

# Run the Auth Proxy and point AddisDB at 127.0.0.1:1433
cloud-sql-proxy --port 1433 PROJECT:REGION:INSTANCE

Connect from AddisDB

1. New Connection → Cloud SQL for SQL Server. Port prefills to 1433, database to master, username to sqlserver.
2. Enter the instance’s public IP, or 127.0.0.1 if the Auth Proxy is running locally.
3. Leave certificate verification on unless you have a reason not to — the password travels inside the TDS login handshake.
4. Test, then Save.

What AddisDB gives you

• Full introspection across schemas, with the foreign-key diagram and saved views.
• T-SQL batches sent whole, so DECLARE and BEGIN…END blocks behave — AddisDB does not split them on semicolons.
• The Live Monitor over the dynamic management views, plus identity-aware mock data.
• Automatic row capping on previews, the Chart view, notebooks and ⌘K search.