SQL Server Trace Flag 4616 no longer required for Dynamics NAV 2009 SP1

ukdynsupport — Wed, 28 Oct 2009 18:12:14 GMT

Starting with Dynamics NAV 4.0 SP3 build 24080, all builds of NAV (SQL option) have a prerequisite that SQL Server trace flag 4616 must be turned on. This was initially required when running NAV with SQL Server 2005 but subsequently was also required for SQL Server 2008 when that became a supported database platform.

Why did we need this trace flag? SQL Server 2005 introduced increased security protection for database metadata which means that visibility is restricted by default for users in such a way that they can no longer see connection details for other logins unless the user is granted “VIEW SERVER STATE” permissions. However, Dynamics NAV licensing functionality and the client feature for displaying database sessions both required that users must have visibility to all active connection details. SQL Server trace flag 4616 causes SQL Server 2005 and 2008 to behave in the same way as SQL Server 2000 with respect to metadata visibility. Therefore, when support for SQL Server 2005 was added to the Dynamics NAV product the requirement to turn on trace flag 4616 was also introduced.

Why do we no longer need this trace flag? With the release of Dynamics NAV 2009 SP1, trace flag 4616 is no longer required. The product now uses “VIEW SERVER STATE” permissions to enable visibility to the required connection information for each user.

For customers who have been using SQL Server trace flag 4616 for older versions of Dynamics NAV Microsoft recommends disabling this trace flag after upgrading to Dynamics NAV 2009 SP1 if there are no other applications which require it. Most environments will have this trace flag added to the startup parameters for SQL Server so the following steps can be used to remove it as required:

1. Go to Start-> Run and select the "Microsoft SQL Server 2005/2008" program group, select the "Configuration Tools" folder and then the "SQL Server Configuration Manager" tool.

2. Double-click on the SQL Server service.

3. Select the "Advanced" tab

4. In the list of values double-click on the one called "Startup Parameters"

5. In the list of values for this parameter (normally near the end), remove the following: ';-T4616'

6. Click OK to save the change.

7. Restart the SQL Server service

In some rare cases the trace flag may be enabled on SQL Server using some other means (e.g. DBCC TRACEON command). Consult your SQL Server database administrator for advice in these scenarios.

Best regards,

Gerard Conroy

Microsoft Dynamics NAV Support, UK.

Identify and kill SQL processes causing CPU shortage

ukdynsupport — Fri, 08 May 2009 12:58:00 GMT

There might be cases in which the SQL processes running against the MSCRM database, start using all available CPU resources causing bad performance and downtimes. Using the following script it is easy to identify which processes are running in the SQL instance and, take reactive actions.

-- THIS SCRIPT HAS TO BE USED IN CASE THE SQL SERVER CPU REMAINS CONSTANTLY AT 100%

-- IT ALLOWS TO INTERCEPT (AND KILL IF NECESSARY) THE PROCESS CAUSING THE PROBLEM

-- CHANGE THE CONTEXT TO MASTER AND LIST ALL THE PROCESSES RUNNING

-- AGAINST THE CRM DATABASE SORTING BY CPU UTILIZATION.

-- REMEMBER TO CHANGE THE DATABASE NAME ACCORDING TO THE NAME OF THE CRM DATABASE

USE Master

-- RETRIEVE THE DATABASE ID FOR THE MSCRM DATABASE

DECLARE @DATABASE_ID INT

SET @DATABASE_ID = DB_ID(N'OrganizationName_MSCRM');

SELECT ST.TEXT,

SP.*

FROM DBO.SYSPROCESSES SP

CROSS APPLY SYS.DM_EXEC_SQL_TEXT(SP.SQL_HANDLE) ST

WHERE SP.DBID = @DATABASE_ID

ORDER BY CPU DESC

-- ONCE YOU IDENTIFY THE PROCESS, IF IS POSSIBLE, KILL IT. TO KILL THE PROCESS IDENTIFY ITS

-- SPID AND USE THE KILL COMMAND (REMEMBER TO REMOVE "<" AND ">")

KILL <SPID>

Carlo Gallazzi | Business Systems Architect | Microsoft Dynamics CRM

UK Microsoft Dynamics Support Team Blog : SQL

SQL Server Trace Flag 4616 no longer required for Dynamics NAV 2009 SP1

Identify and kill SQL processes causing CPU shortage