stryk wrote:
But: with NAV 3.70 this property was not available, thus, if you had to optimize some indexes you had to do it on SQL site (in some cases).
Sorry but I still don't agree that changing the SQL Index directly is the only way to go in any case. If I were to want to change the SQL index in a 3.7 database, I would add 'the right one' in the NAV table designer. Not sure if the MaintainSQLIndex property was available then (I don't have 3.7 exe anymore), but you could turn that off for 'the wrong one'.
Login
Register
RSS Feed
Rules
FAQ
Search the forum
