GPVConnection - AppGeo/GPV GitHub Wiki

By default, all stored procedures used by the GPV are expected to reside in the configuration database. The GPV can call stored procedures outside of the configuration database if given the appropriate database connection information. This table lets you specify these external database connections.

Columns

• ConnectionID - A unique identifier for this database connection (not null). Links to GPVSearch, GPVSearchInputField, GPVQuery, GPVDataTab and GPVLayerFunction.
• ConnectionString - A valid ADO.NET database connection string (not null). Depending on the database software, you may need to install additional software components on the GPV web server for this connection to work.
• Active - Specifies whether this connection should be available for use, 1 for yes and 0 for no. If null, defaults to 0 (no).

Deactivation

Deactivating a connection will automatically deactivate all searches, search inputs fields, queries, data tabs and layer functions that use it.