SQL Procedures

Geo Data Connector provides SQL procedures that you can call from a Snowflake worksheet to manage the Connector's lifecycle and check its status. These offer an alternative to the App Launcher interface.

Database Context

Before calling any procedure, set the active database to the Geo Data Connector application database:

USE DATABASE GEO_DATA_CONNECTOR;

Replace GEO_DATA_CONNECTOR with the name you chose when installing the Connector. To check the name, run SHOW APPLICATIONS; — the name column shows the application database name.

Lifecycle Management

These procedures are available to the APP_ADMIN role.

Procedure	Description
CALL setup.start_app()	Start the Connector. Creates compute resources and launches the application.
CALL setup.stop_app()	Stop the Connector. Shuts down the application and releases compute resources.
CALL setup.resume_app()	Resume the Connector after suspension. Faster than a full start.
CALL setup.suspend_app()	Suspend the Connector without fully stopping it.

Status and Access

These procedures are available to both APP_ADMIN and APP_USER roles.

Procedure	Description
CALL setup.app_state()	Returns the current status (e.g., READY, SUSPENDED, STARTING).
CALL setup.app_url()	Returns the URL for accessing the Connector in a browser.

Example

-- Check whether the Connector is running
CALL setup.app_state();

-- Get the URL to open the Connector
CALL setup.app_url();

-- Stop the Connector to save compute costs
CALL setup.stop_app();

-- Start the Connector again when needed
CALL setup.start_app();

Note: Ingestion tasks continue to run at their scheduled intervals regardless of whether the Connector is started or stopped. Starting and stopping only affects the interactive application used for discovery, task management, and settings.

Using the Connector without the Web Application

The web application is optional. After completing the installation steps in Snowsight (granting privileges, connecting to the API, assigning a warehouse, and mapping roles), you can manage the Connector entirely from SQL worksheets.

One-Time Setup

Configure the ingestion target database — the only required setting before you can create ingestion tasks:

CALL SETUP.GDC_CONFIG('set_setting', PARSE_JSON('{"key": "ingestion-database", "value": "MY_GDC_DATA"}'));

This creates the database and grants the necessary privileges to both application roles. You can verify the configuration:

CALL SETUP.GDC_CONFIG('get_setting', PARSE_JSON('{"key": "ingestion-database"}'));

Managing Ingestion

With the ingestion database configured, use the SQL Procedures API to:

• Discover data sources and datasets (GDC_DISCOVER)
• Create connections to data sources (GDC_CONNECTION)
• Create, manage, and monitor ingestion tasks (GDC_TASK)
• Configure notification and auto-suspend settings (GDC_CONFIG)

When to Start the Web Application

You only need to start the web application (CALL setup.start_app()) if you want to use the interactive browser-based interface for discovery, task management, or settings. Ingestion tasks run at their scheduled intervals regardless of whether the web application is started or stopped.

For the full SQL Procedures API reference, see SQL Procedures API.