Deleting Key vs. Disable Key in SQL

hiddentext
hiddentext Member Posts: 45
edited 2007-03-24 in SQL Performance
Performance wise, does it matter?

Comments

  • Waldo
    Waldo Member Posts: 3,412
    No it doesn't.
    When you disable a key (or uncheck the MaintainSQLIndex), the key disappears in SQL Server.

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • kriki
    kriki Member, Moderator Posts: 9,121
    [Topic moved from Navision forum to SQL Performance forum]
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

  • Marije_Brummel
    Marije_Brummel Member, Moderators Design Patterns Posts: 4,262
    Performancewise no. But in navision YES!!!

    Disabling them will result in compile and runtime errors.

    Please either not maintain them or make them shorter and more selective in SQL.

    It is always a matter of give and take between OLAP and OLTP.

    If you are not sure what you are doing, you might want to hire an expert.
    Marije Brummel | Freelance Business Central Specialist
  • Waldo
    Waldo Member Posts: 3,412
    I was concentrating on performance, indeed :oops:.
    Unchecking MaintainSQLIndex is the best (only) option for your application.

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • kriki
    kriki Member, Moderator Posts: 9,121
    Mark Brummel wrote:
    If you are not sure what you are doing, you might want to hire an expert.
    Hint hint hint... :wink:
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

  • Alex_Chow
    Alex_Chow Member Posts: 5,063
    kriki wrote:
    Mark Brummel wrote:
    If you are not sure what you are doing, you might want to hire an expert.
    Hint hint hint... :wink:

    Wow, I read that so quick didn't even realize there was an advertisment in there. :wink::mrgreen:
    Confessions of a Dynamics NAV Consultant = my blog
    AP Commerce, Inc. = where I work

    Getting Started with Dynamics NAV 2013 Application Development = my book
    Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
  • Waldo
    Waldo Member Posts: 3,412
    Yeah, you get used to it :mrgreen:

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • Marije_Brummel
    Marije_Brummel Member, Moderators Design Patterns Posts: 4,262
    Wow, so you are suggesting I am an expert in this?? :oops:

    :mrgreen:
    Marije Brummel | Freelance Business Central Specialist
  • Waldo
    Waldo Member Posts: 3,412
    good reply! :mrgreen:

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • DenSter
    DenSter Member Posts: 8,307
    There is no need to completely disable a key in NAV on SQL Server. The only thing it might do is cause errors in existing functionality (you'll get error messages saying a key doesn't exist). If you want to remove an NAV key on SQL Server, turn off the MaintainSQL property. This will not make any difference in NAV functionality but it will remove the SQL Server index.

    When you start looking at SIFT levels, you really need to know what you're talking about.
    Daniel Rimmelzwaan
    RIS Plus, LLC

Categories