Traceflag 4616

ta5
ta5 Member Posts: 1,164
edited 2007-05-29 in SQL General
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

Answers

  • ara3n
    ara3n Member Posts: 9,258
    what other applications are running on sql?
    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.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • ta5
    ta5 Member Posts: 1,164
    Hi Rashed

    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
  • ara3n
    ara3n Member Posts: 9,258
    Not with 4.0 sp3 .

    If you have downloaded the update for Vista for 4.0 sp3, then yes you need it.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • davmac1
    davmac1 Member Posts: 1,283
    One of the benefits of the SQL Server version is integration with other SQL Server applications.
    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?
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
  • ara3n
    ara3n Member Posts: 9,258
    you loose security. Application role can see system tables and their metadata.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • ta5
    ta5 Member Posts: 1,164
    Hi Rashed
    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
  • ara3n
    ara3n Member Posts: 9,258
    yeah. with 4.03 regular user (non dbo) can go over licensed sessions.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n

Categories