Category
Versão do produto
Tópico
Subtópico
Resolving alerts in ApexSQL Monitor (4211270)
Summary ... This article explains how to review and resolve triggered alerts and generate summaries using Reports feature. ... Description ... Occasionally, some unattended event occurs, with values above or below some metric’s preset alert threshold.
How to detect whether index maintenance affects SQL Server performance (4300997)
The article How to detect whether index fragmentation affects SQL Server performance explains how and in what cases the Index fragmentation affects SQL Server performance, and when a DBA should and should not have to deal with fragmented indexes.
The process of elimination: How to analyze SQL Server performance with baselines and wait statistics (4213413)
SQL Server’s built in abilities to track query execution via wait statistics is critical to resolving performance problems. ... Wait statistics or response time analysis are metrics that provide the ability to measure the time needed for the database to respond to executed queries.
Performance monitoring of AlwaysOn Availability Groups – Part 1 (4218245)
The AlwaysOn Availability Group was introduced as a new feature in the SQL Server 2012 Enterprise edition and is designed to ensure a more advanced and reliable option for SQL Server high availability and disaster recovery.
How to baseline SQL Server wait statistics (4211856)
Starting with SQL Server 2005, Microsoft introduced the ability of SQL Server to track executed queries executed by measuring and logging the time that executed query has to wait for various resources such as other queries, CPU, memory, I/O, etc.
Improve the performance of an ETL process (4307752)
Due to the sheer volume of data usually involved in an Extract - Transform - Load (ETL) process, performance is positioned very high on the list of requirements which need to be met in order for the process to go as smoothly as possible.
How to activate ApexSQL software manually (4216052)
To activate an ApexSQL product online, a Hardware ID and a product activation key are needed. ... To manually activate an ApexSQL product online: ... Navigate to ‘ Product activation’ web page ... Select the ApexSQL product to be activated from the ‘Product’ pick list and the appropriate product version from the ‘Version’ pick list
The ApexSQL Monitor service cannot be located from the user console installed on the remote computer (4296371)
Applies to ApexSQL Monitor Symptoms After starting the user console installed on a remote network computer, the ApexSQL Monitor service cannot be located and this warning message is displayed: Service is not located.
The "System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation" error (4211429)
Applies to ApexSQL Monitor Symptoms When a user attempts to enter the global metrics period value immediately after selecting the Metrics view, the above error will occur and the application will close Cause Due to a bug in the ApexSQL Monitor, when a user enters and applies the global metrics period value while the current view is not loaded completely, the exception will be thrown and the application will close.
Number of servers exceeds number of available server licenses. Remaining licenses: -1 (4214893)
The “Number of servers exceeds number of available server licenses. ... Remaining licenses -1” error warning message appears in the Add instance page when trying to add a new SQL Server instance to monitor.
The ApexSQL Monitor service is not running (4213609)
Description This article explains what to do when ApexSQL Monitor service is not running. ... Summary The ApexSQL Monitor service is not running, an error message is shown, and no SQL Server instance is monitored.
The “An error occurred when trying to replace existing file” error is encountered when updating ApexSQL Monitor (4213603)
Symptoms During the update of ApexSQL Monitor from version 2014 R2 to version 2014 R3, the error message appears saying that the files are in use and the update process is finished. ... Resolution In this situation, it is recommended to re-install ApexSQL Monitor in the following way:
The “Files are in use” error occurs when upgrading ApexSQL Monitor (4216267)
Summary ... When installing the ApexSQL Monitor public release over the ApexSQL Monitor alpha version, an error occurs. ... Symptoms ... During the ApexSQL Monitor 2014 installation, if ApexSQL Monitor alpha exists on the machine, the error message might appear saying the files are in use and the installation process stops.
“Internal server error”, missing performance data, page cannot load or corrupted pages issues occur after application update (4211373)
Symptoms ... The “Internal server error” warning message appears in the various application pages, pages without performance data or corrupted pages are displayed, or page cannot be loaded issues might be encountered after the application is updated to a newer version.
The ApexSQL Monitor repository database transaction log file continues to grow even after data was deleted using the Purge data option (4214906)
Applies to ApexSQL Monitor Symptoms Free hard disk space can be used up due to continuous growth of the ApexSQL Monitor repository database log file. ... Cause ApexSQL Monitor uses the default SQL Server instance settings when creating the ApexSQL Monitor repository database, which means the Auto growth option is turned on.
Cannot update the ApexSQL Monitor user console to a newer version (4211367)
On computers where only the user console is installed, the installer will offer only the full installation of ApexSQL Monitor, instead of clean updating of the user console ... Affected versions:
Internal error: Expression error ‘Runtime Error (at 202:207): External exception E0434352 (4214888)
checked by default, the abovementioned error could be encountered Affected versions: ApexSQL Monitor 2014.01 and 2014.02 Workaround If the user encounter this particular error during the installation, unchecking the “Create SQL logon (sysadmin)” option in the Configuration dialog will allow completing the installation process without the error Resolution We are in the process of resolving this issue and the fix will be available soon If you experience this issue and need additional help, please
The “The server <server_name> doesn’t exist in the database” error is encountered when disabling the monitored SQL Server (4211414)
Symptoms ... After extended work in the ApexSQL Monitor console, when user selects the monitored SQL: Server instance from the monitored servers list and presses the Disable button, the error message “The server doesn’t exist in the database” will pop up and the operation will not be accomplished leaving SQL Server enabled.
SQL Server database can’t be taken offline when monitored via ApexSQL Monitor (4213602)
ApexSQL Monitor 2014 R3 and earlier ... Workaround ... For users that run into this issue, the problem can be solved by temporarily by stopping the ApexSQL Monitor service. ... To do that: ... Run Services from the Control Panel->All Control Panel Items->Administrative Tools
Internal server error (4213585)
Symptoms The Internal server error warning message appears in the Dashboard page when in the instance tree view a particular SQL Server is selected. ... Problem The Internal server error warning message appears for a particular server not for the all monitored servers.
The “Service is not located. Please try different machine name or port, or verify that the service is running” error (4213600)
Please try different machine name or port, or verify that the service is running” after successful completing of the installation Reason Due to a bug, the above mentioned error will be displayed because the Monitor.dat file contains the inappropriate URL and under certain circumstances, it will disable the use of ApexSQL Monitor Affected versions: ApexSQL Monitor 2014.01 and 2014.02 Resolution When this particular error is encountered, follow the steps below:
SQL Server can’t be added for monitoring due to blank control displays in the ‘Add server’ dialog (4213593)
Applies to ApexSQL Monitor Symptoms A SQL Server instance can’t be added for monitoring, due to the fact that the Add server dialog buttons are blank and user interaction is not allowed: Cause ApexSQL Monitor utilize the Microsoft Windows Presentation Foundation (WPF) as a graphical subsystem for GUI rendering.
How to set up and activate custom performance metrics (4209558)
This article explains how to create and set up custom SQL metrics for monitoring the SQL Server. ... Custom SQL metrics are T-SQL based queries that can be created in ApexSQL Monitor to collect calculated performance data
How to manage monitored queries (4211299)
Timely, queries will be collected and added automatically for monitoring. ... Within the Query waits view, users can review query execution time and other information like total wait time, execution count etc.
How to migrate the repository database to a different SQL Server (4218803)
This article describes post migration steps after the ApexSQL Monitor central repository database has been migrated to another SQL Server instance. ... Description ... If the ApexSQL Monitor central repository database needs to be monitored to a new SQL Server, it can be moved via backup and restore, attach or detach etc.
Associação de novos produtos
- Ferramentas de autoatendimento
- Base de conhecimento
- Notificações e alertas
- Suporte a produtos
- Downloads de software
- Documentação técnica
- Fóruns de usuário
- Tutorial em vídeo
- Feed RSS
- Fale conosco
- Suporte técnico
- Visualizar tudo