Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Traceflag 4616
ta5
Member Posts: 1,164
Hi
As I understand, traceflag 4616 must be set on SQL Server 2005, regardless whether Nav 4.03 or 5.0 is used. Is this correct?
If yes, does anybody have experience with this instance globally flag if other applications are running on the same SQL instance? Or to ask more directly: Could it be a problem for other applications if the flag is set?
Any input will be apprecitated. Thanks.
Thomas
As I understand, traceflag 4616 must be set on SQL Server 2005, regardless whether Nav 4.03 or 5.0 is used. Is this correct?
If yes, does anybody have experience with this instance globally flag if other applications are running on the same SQL instance? Or to ask more directly: Could it be a problem for other applications if the flag is set?
Any input will be apprecitated. Thanks.
Thomas
0
Answers
normally navision should be the only db on the sql server.
all traceflag is doing is revert to pre- SQL Server 2005 behavior.
In earlier versions of SQL Server (prior to SQL Server 2005), all data, including metadata, was available through relational tables called system tables. Every database in a SQL Server instance had its own set of system tables and, in addition, there were system tables that existed only in the master database. System tables have several properties by which they can be recognized: names that start with "sys", xtype values in the sysobjects table of "S", and Object ID values less than 100.
Prior to SQL Server 2005, most of the data in the system tables was visible to any user, except for data in a few columns with limited visibility, such as password columns.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Thanks for the information. I don't not yet what apps will run on this server. I agree with you that Navision should be the only one.
Last question on this: Has the flag to be set also for 4.03 with SQL 2005?
Regards
Thomas
If you have downloaded the update for Vista for 4.0 sp3, then yes you need it.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Seems strange that even version 5 requires SQL Server 2005 to revert to SQL Server 2000 behavior. Do you know excatly what that means? What new features do youy lose?
http://mibuso.com/blogs/davidmachanick/
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Thanks for the info.
Strange thing, do you no why 4.03 does not need the traceflag but 4.03 Vista Patch and 5.0 do need it?
Thanks in advance.
Thomas
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n