Skip to main content

Trace Flag is no more Required


You may remember that customers who were running NAV 5.0 and NAV 2009 with SQL Server option were required to enable the Trace Flag 4616 in the SQL server database. However, this is no longer required with the latest NAV 2009 SP1 version, as it uses “VIEW SERVER STATE” permissions to enable visibility to the required connection information for each user. Therefore, now it is recommended that Trace Flag to be disabled after upgrading it 2009 SP1. If you are going for new installation, of course this is not required at all.
In most cases, we enabled the Trace Flag by adding it to the startup parameters by opening the "Configuration Tools" folder of the "SQL Server Configuration Manager". However, you can disable it now by following the below steps;

1. Go to Start-> Run and select the "Microsoft SQL Server 2005/2008" program group, select the "Configuration Tools" of 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 (mostly at the end), remove the following: ';-T4616'
6. Click OK to save the change.
7. Restart the SQL Server service


Note:
In certain instances, you may have done this by using the DBCC TRACEON command. If that is the case, you could also do this by SQL Server Query Window.

Comments

Post a Comment

Popular posts from this blog

Upgrade from NAV 5 to NAV 2009 SP1 – A QUICK GUIDE

Regardless of the version from which you are trying to do the upgrade, the whole process can be divided into two main phases as Object Upgrade and the Data Upgrade. Let’s first look at the Object Upgrade. In Object Upgrade, you have to identify all the customizations done in the current live version of the customer database and implement the same in a new 2009 SP1 database. Please remember that there are no short-cuts for this process. This is entirely a manual process, but you can make use of the existing tools such as Developer Toolkit. Using the Developer Toolkit you can compare/merge the original version 5 db and the current customer database wherein you can identify the differences between the two databases and implement the modifications in a new 2009 SP1 fresh database. Once you complete this process, you are through with the phase no 1. Remember that this is the most time consuming phase in an upgrade project. If you make any mistakes then you have to suffer lot in the subseque...
Post a Comment
Read more

Microsoft Announces the Availability of Management Reporter for Microsoft Dynamics ERP

Microsoft has now announced the general availability of Management Reporter for Microsoft Dynamics ERP. Management Reporter, formerly codenamed Management Reporter 2.0, will act as the replacement for Microsoft FRx, www.newscom.com/cgi-bin/prnh/20000822/MSFTLOGO Management Reporter extends the proven functionality of Microsoft FRx and enables people to quickly and easily create, generate, help secure and publish professional-looking financial statements, such as profit and loss statements, balance sheets, and cash flow reports, and will also allow them to take advantage of the following: • Custom reports without IT assistance. These reports reduce the burden on the IT department by empowering the finance team to create its own financial statements. • Deep cross-functional analysis. Management Reporter provides easy and accurate financial reporting, intercompany reconciliations and eliminations. • Reduced training time and increased productivity. A familiar user interface and reporting ...
Post a Comment
Read more

Future of NAV Development Environment

The C/SIDE development environment is going to be replaced from Classic Client to RTC. As you know, still we have to depend on the NAV Classic Client for making any customization, even though we do the implementation in RTC, but this structure is going to replace with the upcoming versions of Dynamics NAV. Some of the highlights would be as follows; 1. No Object Designer! Simple. This will be replaced with Designer Home Center; it will be another role center which allows developers/consultants to make any changes to the standard objects of the application. 2. Page Designer will be replaced with another page where it will allow you to proceed with your table customizations. This feature will be brought into the other object types as well. 3. In the Object List, developer will find the all objects including data about where they used and information about the usage. 4. No Visual Studio! Own simple editor for making all changes in Code Units. 5. The structure of the Editor would be more t...
Post a Comment
Read more