Navision SQL Tools

Administrator

Navision SQL Tools
SQL Tools for Microsoft Business Solutions - Navision.

Components Included:
- Application Benchmark Toolkit
- Performance Troubleshooting Guide
- SQL Server Resource Kit

http://www.mibuso.com/dlinfo.asp?FileID=561

Discuss this download here.

nEWvision

Hi

I have got a task to identify the usused keys and to identify the Keys where MaintainSQLIndex, MaintainSIFTIndex and SIFTLevelsToMaintain has to be changed in order to get the best performance. I have used Unused Key tool to identify the unused keys but I am not very sure about How to identify the Keys that needs the correction for MaintainSQLIndex, MaintainSIFTIndex and SIFTLevelsToMaintain. :?

I tried to understand the use of Key Information Tool but could not understand how the information generated by toold should be used.

I would really appriciate the suggestion of all the experts on this forum.

Regards
NewVision

Marije_Brummel

PLEASE! Leave SQL performance tuning to experts. I is not my intention to advertise my services, but you can more easily break something than fix something.

The tools can be a great help, but they have to be used and interpreted by someone who knows what he is doing. Both knowledge of SQL server as C/AL is required in order to make the right decisions.

SQL server has a completely different approach as for index handling as Navision does, please be carefull with this.

Happy Christmas!

nEWvision

Hi Mark

PLEASE! Leave SQL performance tuning to experts.

I really appriciate your concerns for involving the expert for the job but I believe that tuning a SQL server is not a rocket science that can not be learnt. Please go ahead with your suggestion

The tools can be a great help, but they have to be used and interpreted by someone who knows what he is doing. Both knowledge of SQL server as C/AL is required in order to make the right decisions.

SQL server has a completely different approach as for index handling as Navision does, please be carefull with this.

I have worked on SQL Server and C/Side both so Please go ahead with your suggestion on How the information generated by Key Infiormation Tool can be used to identify the Keys and other changes that I mentioned in my first message.

DenSter

Mark's point is:

Mark Brummel wrote:

you can more easily break something than fix something

This applies double for those people who underestimate what is involved. You don't have to take our advice, but don't complain when it goes wrong please

Oh and Merry Christmas *HO HO HO* 8)

nEWvision

Hi DenSter

This applies double for those people who underestimate what is involved. You don't have to take our advice, but don't complain when it goes wrong please

I am not underestimating anyone here. How can I do that mistake? I know very well whom I am talking to? You guys are superb in your area.

With all due respect I am trying to say that instead of saying that I should not go for it, I should be guided for the process and the precaution that I should take while doing the activity.

No wrong intention.

Merry Christmas *HO HO HO* *HO HO HO* *HO HO HO*

Savatage

Sounds like there is alot of trial & error involved.
That's why we're still on Native

I don't have the time to go thru all of
http://www.microsoft.com/technet/prodte ... fault.mspx

You would think that since SQL seems to be the way MS is moving towards - not just for Navision, that they would be working on some great tools/dashboard to make everyone's life easier. Else the emergency help center is going to field alot of calls. (2 cents)

DenSter

I guess what I think you should do is get an expert involved (a real person in your office) to at least cover the basics. You really do not want to start messing around (doing something wrong here can corrupt your database). Just so long as you realize that most (like 99% of the work) is done within NAV you should not be able to screw up anything beyond repair. Do NOT touch any table design on SQL Server, including field design, trigger code, and indexes. You can run indexdefrag and things like that, but do yourself a favor and leave the table design in SQL Server alone. There is nothing you can do there, don't even try it.

nEWvision

Hi Denster

Thanks for your suggestion. I will seriously follow the suggestion given by you and would not proceed for somethning, I am not comfertable doing with.

I do not have any Sql Expert in my office to assist me in doing the activity. Currently I am trying to do this activity on Test database and the scope is limited only to identify the SIFT Level that is not being used and the unused key.

I wanted to know if we have some tool available which can be used to identify the Sift level that is not being used by the system currently and we can mark it as inactive. I tried to use Key Information Tool but finding a bit difficult to analyse the data generated by the tool.

I would appriciate your help on this.

Marije_Brummel

The tools provided my microsoft still require a lot of manual interpretation. This is where the knowledge of both systems is required in order to make the right decision.

For example, I was tuning a database this week and after changing the SIFT levels, one process was better, but another process was slower.

As a performance consultant I see a lot of bad stuff, both on C/Side and SQL.

Yes there are tools that help you analyse this automated, but these are not for free.

Please have a look at our website www.sqlperform.com and let us know if we can help you. The installation can be done remote.