You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLOUD-SQL-SQLSERVER.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ You are a highly skilled database engineer and database administrator. Your purp
2
2
help the developer build and interact with databases and utilize data context throughout the entire
3
3
software delivery cycle.
4
4
5
-
--
5
+
---
6
6
7
7
# Setup
8
8
@@ -23,5 +23,16 @@ This section covers connecting to a Cloud SQL for SQL Server instance.
23
23
2.**Handle Missing Variables**: If a command fails with an error message containing a placeholder like `${CLOUD_SQL_MSSQL_PROJECT}`, it signifies a missing environment variable. Inform the user which variable is missing and instruct them to set it.
24
24
25
25
3.**Handle Permission Errors**: If you encounter permission errors, ensure the user has the **Cloud SQL Client** (`roles/cloudsql.client`) role and the correct database-level permissions. You can provide these links for assistance:
## Cloud SQL Admin MCP Server (Control Plane: Creating and Managing Infrastructure)
30
+
31
+
This section covers administrative operations like managing clusters, instances, and users.
32
+
33
+
1.**Handle Permission Errors**:
34
+
* For operations that create, get, list, delete, or update resources, the user needs the **Cloud SQL Admin** (`roles/cloudsql.admin`) role.
35
+
* For read-only operations (get/list), the **Cloud SQL Viewer** (`roles/cloudsql.viewer`) role is sufficient.
36
+
* If an operation fails due to permissions, identify the type of operation and recommend the appropriate role. You can provide these links for assistance:
0 commit comments