The MSSQL SDE List Tables monitoring point is designed to work together with the MSSQL 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 MSSQL 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 Microsoft SQL Database. This list is used to identify geodatabase feature datasets, feature classes and that are unused for SDE Usage reporting. The MSSQL SDE Usage check is generally run hourly and records what feature datasets, feature classes and tables are open. A more detailed description of the MSSQL 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 MSSQL SDE List Tables include: |
Server Name |
DNS name of server where the SQL database is located |
Database |
Database name to check (must match Usage Check) |
userID |
User ID with access to the MSSQL Table. If using Windows AD authentication, enter Domain\UserID Note: userID should be entered as encrypted information |
userPW |
User PW for access to the MSSQL 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 |
Defaults to SDE, or enter DBO.” |