This Knowledgebase article explains the protection offered by Neverfail for SQL Server AM(X). There is a sister article ( Knowledgebase article #560 - 'Neverfail for SQL Server – Application Module – Versions') that lists all the versions of the AM(X) that have been produced to date and the versions of related supported software. In addition, there are links from that sister article to articles that explain the unique features of each version.
Neverfail for SQL Server proactively monitors your SQL Server database environment and protects all database instances present at install time. Existing and newly created databases and logs will be protected automatically. Please note that database instances created after Neverfail for SQL Server has been installed will not be protected. The following configurations of SQL Server are supported in respect to the hardware platform:
x86 Platform (32-bit hardware)
- SQL Server Standard / Enterprise 2005 (up to SP2)
- SQL Server Express Edition 2005 (up to SP2)
- SQL Server 2000 SP4 Standard / Enterprise
- MSDE 2000 SP4
x64 / Intel 64 Platform (64-bit hardware)
- SQL Server 2005 x64
Any other SQL version(s) running in WOW64 (as a 32-bit application on 64-bit hardware) is not supported and will be ignored if SQL Server 2005 x64 is present.
The IA-64 Itanium Platform is not supported.
This is a list of all services protected by this AM(X). Please note that where an AM(X) supports multiple vendor versions, some services may not be present in a particular version.
- Task Scheduler (Schedule)
- Indexing Service (CiSvc) – SQL Server 2000
- Search Service (MSSearch) - SQL Server 2000
- SQL Server Integration Services (MsDtsServer)
- SQL Server Browser (SQLBrowser)
Instance specific services
- SQLAgent$InstanceName (SQLAgent$InstanceName) – SQL Server 2000
- MSSQL$InstanceName (MSSQL$InstanceName) – SQL Server 2000
- SQL Server (Instance) (MSSQL$Instance)
- SQL Server Agent (Instance) (SQLAgent$Instance)
- SQL Server Analysis Service (Instance) (MSOLAP$Instance)
- Msftesql$Instance (Msftesql$Instance)
- SQL Server (MSSQLSERVER)
- SQL Server Agent (MSSQLSERVER)
- SQL Server Analysis Service (MSSQLSERVER)
- SQL Server Reporting Service (MSSQLSERVER)
When the AM(X) is installed, all protected services will be set to manual unless otherwise stated.
This is a description of the protected data set that was determined at AM(X) install time. Please note that exact filters will be based on the configuration of the application AM(X) when it was installed.
- All registry data and program files
- All installed SQL Server instances discovered at install time
- All the databases for the protected SQL Server instances
Automatic Filter Discovery
The AM(X) does provide a filter discovery component. For detailed information about the Automated Filter Discovery in Neverfail for SQL Server, please refer to Knowledgebase article #398 - 'Automated filter discovery in Neverfail for SQL Server'.
- The AM will automatically protect all newly created databases for SQL Server, independent of location (default or user defined).
Unsupported Components or Features
The AM(X) does not protect the following application features or components:
- This AM does not provide runtime detection of new SQL Server instances. In order to protect the newly created services (for each new instance), the AM will need to be reinstalled according to Knowledgebase article #462 - 'How to upgrade or reinstall an Application Module to protect previously unprotected features'.
- For protecting the reports generated by the SQL Server Reporting Service, which are published via an IIS Web Server Virtual Directory, Neverfail for IIS must be installed.
- The Report and Analysis projects created with the Business Intelligence Development Studio are not protected by default. In order for them to be protected, a File Filter must be defined manually for the user location where they are saved. For more information on how to create File Filters from the Neverfail Heartbeat Management Client, please refer to Knowledgebase article #850 - 'How to Specify or Adjust Filters Manually'.
- Run-time filter discovery is not provided for the OLAP Services; the configuration will be determined at install time.
- SQL Server VSS Writer (SQLWriter) as this service is started on demand.
- Jobs temporary directory.
- Databases attached using SQL Server Management Studio are not protected by the filter discovery component. File filters have to be added manually for the specific locations. For more information on how to create File Filters from the Neverfail Heartbeat Management Client, please refer to Knowledgebase article #850 - 'How to Specify or Adjust Filters Manually'.