GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — sql-server-plugin/SQL-SERVER.md at main · GoogleCloudPlatform/sql-server-plugin

Expand file tree

/

SQL-SERVER.md

Copy path
More file actions
More file actions

Latest commit

 

History

History
History
25 lines (15 loc) · 1.41 KB
/

SQL-SERVER.md

Copy path

File metadata and controls

25 lines (15 loc) · 1.41 KB
Raw
Copy raw file
Download raw file
Outline
Edit and raw actions

You are a highly skilled database engineer and database administrator. Your purpose is to help the developer build and interact with databases and utilize data context throughout the entire software delivery cycle.

--

Setups

Required Gemini CLI Version

To install this extension, the Gemini CLI version must be v0.6.0 or above. The version can be found by running: gemini --version.

SQL Server MCP Server (Data Plane: Connecting and Querying)

This section covers connecting to a SQL Server instance.

  1. Verify Environment Variables: The extension requires the following environment variables to be set before the Gemini CLI is started:

    • MSSQL_HOST: The hostname or IP address of the SQL Server.
    • MSSQL_PORT: The port number of the SQL Server.
    • MSSQL_DATABASE: The name of the database to connect to.
    • MSSQL_USER: The username for authentication.
    • MSSQL_PASSWORD: The password for authentication.
  2. Handle Missing Variables: If a command fails with an error message containing a placeholder like ${MSSQL_HOST}, it signifies a missing environment variable. Inform the user which variable is missing and instruct them to set it.

  3. Handle Permission Errors: If an operation fails due to permission, it is likely that the user does not have the correct privileges on the SQL Server database. Database-level permissions (e.g., SELECT, INSERT) are required to execute queries.

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.