Monitor SQL Server
- Last UpdatedApr 10, 2025
- 2 minute read
SQL Server hosts three components of the Server architecture:
-
AVEVA Production Management project configuration database
-
AVEVA Production Management data repository
-
AVEVA Production Management state database
The setup and configuration of the underlying SQL Server directly relates to the performance and operation of the Server.
Maintain SQL Server
This section includes information about how to configure SQL Server to use with AVEVA™ Production Management.
Set up SQL Server maintenance plans
It is important to configure a maintenance plan for SQL Server databases, particularly those that have data written to them on a daily basis such as the AVEVA™ Production Management databases.
Back up system databases
It is also important to back up the system databases such as master, msdb, and model. You will need to restore these early in the disaster recovery process so that information about users, logins, maintenance plans, DTS packages, SQL Server Agent jobs and schedules are automatically restored.
Manage backup files and log files
File management is also an important part of any disaster recovery scheme. A common occurrence is that if a database is configured for Full Recovery Mode, but backups are not scheduled, the transaction log continually grows and eventually fills the SQL Server hard drive.
Similarly, the number of backup files and transaction log files can grow out of control and fill both SQL Server local drives and waste network resources.
Use SQL Server Management Studio
Use the SQL Server Management Studio to configure and monitor SQL activity.
Open the SQL Server Management Studio
-
On the Windows Start menu, point to All Programs, then Microsft SQL Server, then SQL Server Manager Studio.
Manage SQL Server memory
Having too little SQL Server memory can be detrimental to AVEVA™ Production Management performance. Unfortunately, it can be difficult to determine when you require more memory in the system. When memory problems begin, you'll start to see an increase in disk I/O, as well as an increase in disk queuing. You'll also see a decrease in the buffer cache hit ratio and page life expectancy. Another indication of low memory resources, is that you may begin to see SQL Server event messages in the Windows Event Log.
For optimal performance of AVEVA™ Production Management, it is important to manage both SQL Server memory and Windows memory.