Search: Advanced search

Postgres SDE Usage

Article ID: 300

Last updated: 17 Aug, 2018

Revision: 8

Export to PDF

Email to friend

The Postgres SDE Usage monitoring point is designed to work together with the Postgres SDE List Tables check to generate the information required for SDE Usage reporting for data in a SQL Server RDBMS. 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.

It is recommended the Postgres SDE Usage check be run hourly(up interval 60). When it runs, it generates information on what SDE geodatabase feature datasets, feature classes and tables are open at that time. This information is written to the SDE Usage database.

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 Usage include:

Server Name	DNS name of server where the Postgres database is located
Database	Database name to check (must match List Tables 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 Postgres 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 *Note:* Rpt-DSN:User:Pwd should be entered as encrypted information
Opt-User Schema	Defaults to SDE. Enter User Schema if needed.

Next, configure the GeoMonCharts UI web.config file with the database information added for this monitoring porting, following the instructions in Editing the Geomonitor UI Web Config for Microsoft Usage Database.

Prev		Next
Postgres SDE List Tables		RSS Feed