If you are having performance issues with your SQL Server system, the last thing you need is to have unnecessary services running, consuming resources that you need for productive work. A common issue I've found when I work on sites that are using SQL Server with Enovia is that unnecessary SQL Server services are running. You will not see a huge difference in performance by disabling the unnecessary services. But, having those unnecessary services running not only will require extra resources but also may expose you to security vulnerabilities due to unnecessary surface exposure (but only if there are problems with the services that you are not using).

SQL Server Versions and Services

Enovia currently supports SQL Server 2005 and SQL Server 2008, depending on which version of Enovia you have deployed. The services for these two versions of SQL Server have the same names and general capabilities. The services that are available with SQL Server (after you install all the services) include:

SQL Server Active Directory Helper
SQL Server Full-text Filter Daemon Launcher
SQL Server (InstanceName)
SQL Server Agent (InstanceName)
SQL Server Analysis Services (InstanceName)
SQL Server Browser
SQL Server Integration Services 10.0
SQL Server Reporting Services (InstanceName)
SQL Writer Service

As you might expect, each of these services performs a valuable function in the SQL Server world. However, if all you are asking your server to do is to support your Enovia database, you need only the few services that I describe below.

SQL Server (InstanceName).
This is the core service of the SQL Server relational database engine. If you have multiple instances installed, InstanceName will be unique for each instance. For a default instance installation of SQL Server, the instance name will be MSSQLServer. This service must be running for your Enovia installation, and the startup type for this service should be set to Automatic (see Figure 1).

Figure 1. SQL Server service startup properties

 

SQL Server Agent (InstanceName).
This is the job and alert management service for SQL Server. The instance name rules are the same as for the SQL Server service. If you are using maintenance plan jobs or other jobs to back up, organize, or optimize your SQL Server installation (which is highly recommended), you will need to have this service running.

SQL Server Analysis Services (InstanceName).
This is the Analysis Services service (i.e., the OLAP engine). By default, Enovia does not use Analysis Services. So, unless you are doing some sort of data warehousing on your SQL Server installation for Enovia (which is not recommended), you should stop this service and set its startup type to Manual. (To access the startup type setting for services, open Administrative Tools in Control Panel, and then start the Services snap-in console.)

SQL Server Reporting Services (InstanceName).
This is the report server capability of SQL Server. By default, Enovia does not use Reporting Services. So, unless you are doing some sort of reporting from your SQL Server installation for Enovia, you should stop this service and set its startup type to Manual.

SQL Server Integration Services 10.0.
This service supports the Integration Services capabilities of SQL Server. Typically, its startup type is set to Manual, and the service is not started. That's the appropriate state for an Enovia installation as well.

SQL Server Browser.
The SQL Server Browser service helps older SQL Server clients discover the instance name to port mapping for SQL Server. This service is not necessary for most clients and is not required for Enovia installations. Typically, this service is not started. But, if for some reason it is, you may have found a specific need for it, so I wouldn't stop it.

The rest.
SQL Server Active Directory Helper, SQL Server Writer, and SQL Server Full-text Filter Daemon Launcher each support specific capabilities of SQL Server. Your best bet with these services is to leave them as you find them, because the overhead to have them running should be very low. Most of the time, these services will not be running.

Will It Really Make a Difference?
Yes. Even when you're not using these services, they will compete with SQL Server at a minimal level for CPU, memory, and I/O resources. It's a best practice to enable only the services that you will actually use.

For Dassault Systèmes ENOVIA V6 on SQL Server and Microsoft news, events, and further information, see the Dassault Systemes and Microsoft Alliance page.

_____________________________________________________________________________________________

 Follow Tier1OnSQL on Twitter