This section gathers the support articles offering advice on common problems, questions, and specific errors encountered during installing, configuring, upgrading or general maintenance of the SQL Monitor infrastructure (consisting of the Web Server, Base Monitor and SQL Server data repository).
- Installation or Upgrade Failures
- SQL Monitor 'Internal' Connection Failures
- Web Server issues
- Data Repository Issues
Installation or Upgrade Failures
-- Reported problems and common questions regarding the SQL Monitor installation process.
- Verification of SQL Monitor Web failed / The installation package could not be opened
- SQL Server session hangs when you try to enable snapshot isolation in SQL Server
- Using high availability options with the SQL Monitor services and repository
- Migrating SQL Monitor to a new server
- Planning the SQL Monitor infrastructure and installation
If you're planning a fresh installation of SQL Monitor, read this section of the documentation.
- Maintaining and upgrading SQL Monitor
Advice in the documentation on performing SQL Monitor maintenance, including where to find the log file, plus what to do in order to upgrade safely.
- Getting Started with SQL Monitor
Redgate video tutorials covering simple installation and configuration, including how to install multiple base monitors and multiple dashboards.
SQL Monitor 'Internal' Connection Failures
--'Internal' connection problems, between the SQL Monitor Web UI and base monitor, or base monitor and data repository.
- Connecting to the data repository
- Locating the SQL Monitor database
- Creating a data repository database
- Unable to connect to Base Monitor
- SQL Monitor - default port settings
- SQL Monitor Base Monitor and Web Server versions are different
- The web server isn't authorized to access this base monitor
- Permissions required for the SQL Monitor Service accounts
Many reported issues with connections resolve to permission problems with the service accounts, so it's worth reviewing this page in the documentation.
- Viewing component information and log files
The SQL Monitor logs can be very revealing if you are having any connection, or other, problems.
Web Server issues
-- Reported problems with the SQL Monitor Web Server or IIS, such as port conflicts, permission failures, UI issues.
- Running SQL Monitor in an iframe
- CSS in SQL Monitor UI Not loading properly
- SSL Setup for SQL Monitor
- HTTP 503 in the SQL Monitor UI
- HTTP 500 in the SQL Monitor UI
- Changing the SQL Monitor Web Server Port
- Server Error in '/' Application - OracleWebEventProvider
- SQL Monitor browser error - Cannot display webpage, connection timed out, webpage not available, or could not locate remote server
- Moving from SQL Monitor Web server to IIS
- Problems with IIS and ASP.NET
Data Repository Issues
-- Unexpected growth of the data repository is the most reported issue.
- After changing purge settings the data repository does not immediately reduce in size
- tempdb size increases when clearing purge backlog
- SQL Monitor UI still showing data for removed entities
- SQL Monitor database requirements
General advice on setting up the data repo.