Search: Advanced search

Postgres SDE List Tables

Article ID: 453

Last updated: 30 Dec, 2019

Revision: 2

Export to PDF

Email to friend

The Postgres SDE List Tables monitoring point is designed to work together with the Postgres SDE Usage check to generate the information required for SDE Usage reporting. It is recommended that these two checks be placed together in a GeoMonitor Server because of the fact that both are needed to generate the data required to support SDE Usage reporting.

The Postgres SDE List Tables check runs once a week based on a time stamp stored in the GeoMonitor database. The check creates a list of all of the SDE (version 10.0 and greater) geodabase feature datasets, feature classes and tables in a Postgres Database. This list is used to identify geodatabase feature datasets, feature classes and that are unused for SDE Usage reporting. The Postgres SDE Usage check is generally run hourly and records what feature datasets, feature classes and tables are open. A more detailed description of the Postgres SDE Usage check is provided in the next section.

Note: If you are using Microsoft SQL Server / SQL Server Express, follow the instructions in Setting Up Microsoft SQL Server for SDE Usage Database.

If you are not sure where your Usage information is being stored, you can consult the “About” dialog on the GeoSystems Monitor Charts UI.

The parameters that are unique to the Postgres SDE List Tables include:

Server Name	DNS name of server where the Postgres database is located
Database	Database name to check (must match Usage Check)
userID	User ID with access to the Postgres Table *Note:* userID should be entered as encrypted information
userPW	User PW for access to the Postges Table *Note:* userPW should be entered as encrypted information
Rpt-DSN:User:Pwd	Needed only if using RDBMS to store usage information – string must include YourODBC_ConnectionName:UserID:UserPW
Opt-User Schema	(Optional) Postgres SDE schema name (DBO)

Prev		Next
Postgres Database/Table		Postgres SDE Usage