Database activity monitoring

Features

• Real-time monitoring - View all currently active database sessions in real-time.

• Session filtering and selection - Identify sessions by Program Name, User ID, Host Name, and AOS Session ID.

• Performance diagnostics - Analyze CPU and memory usage, I/O statistics, and row processing counts.

• Telemetry and user context - View User Telemetry ID to correlate sessions with telemetry logs.

• Batch task inspection - Use the ‘Session batch tasks’ button to review batch jobs linked to the session.

• Historical request activity - Track last request start/end times to understand session activity patterns.

Database active sessions

Form: System administration \ Inquiries \ Database \ Database active sessions

Running production system

Session ID	Internal ID for the database session. Helps identify and troubleshoot specific connections.
Program name	Context of the session – commonly axBatch, axOnline, or axSystem.
Host name	Client machine or AOS server name initiating the session.
AOS session ID	Application Object Server session ID in Dynamics.
User ID	Dynamics user ID associated with the session.
User telemetry ID	GUID used for telemetry and cross-referencing logs.
CPU time (ms)	Total CPU time consumed by the session in milliseconds.
Memory usage (MB)	RAM consumed by the session in megabytes.
Reads	Number of physical disk read operations.
Writes	Number of write operations to the disk.
Logical reads	Number of logical page reads from buffer cache.
Row count	Number of rows processed by the last executed request.
Last request start date/time	Timestamp when the most recent request began.
Last request end date/time	Timestamp when the most recent request ended.

Steps to Identify Top Database Consumers

Step 1: Sort by Logical reads Identify sessions with the highest logical reads to detect large scans or inefficient joins.

Step 2: Review CPU time Sort by CPU time to find sessions consuming the most processor resources.

Step 3: Analyze memory usage Filter sessions by memory usage to locate memory-intensive tasks.

Step 4: Correlate with Writes and Reads Compare reads and writes to classify the I/O pattern of sessions.

Step 5: Use the 'Session batch tasks' button Drill into batch jobs tied to high-resource sessions.

Step 6: Cross-check timestamps Look for sessions with old start times and missing end times to detect hanging processes.

Step 7: Investigate User/Telemetry IDs Trace sessions to users or business processes using User ID and Telemetry ID.