Deleting Key vs. Disable Key in SQL

hiddentext

Performance wise, does it matter?

Waldo

No it doesn't.
When you disable a key (or uncheck the MaintainSQLIndex), the key disappears in SQL Server.

kriki

[Topic moved from Navision forum to SQL Performance forum]

Marije_Brummel

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.

Waldo

I was concentrating on performance, indeed :oops:.
Unchecking MaintainSQLIndex is the best (only) option for your application.

kriki

Mark Brummel wrote:

If you are not sure what you are doing, you might want to hire an expert.

Hint hint hint...

Alex_Chow

kriki wrote:

Mark Brummel wrote:

If you are not sure what you are doing, you might want to hire an expert.

Hint hint hint...

Wow, I read that so quick didn't even realize there was an advertisment in there.

Waldo

Yeah, you get used to it

Marije_Brummel

Wow, so you are suggesting I am an expert in this?? :oops:

Waldo

good reply!

DenSter

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.