One of my client using Nav 3.7 with Sql 2000 database. Frequently database getting hang while positng sale invoices. Number of users is around 50, around 30 users loging through VPN connectivity. Volume of transaction is huge at anytime.
Is anyone tell me any problem with SQL 2000 database while using huge transaction at the time. What will be the remedial action for this issue.
Regards,
Raja
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Raja
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
There are also some examples, ppt/pdf/wmf files, and there are explained how to optimizes NAV for SQL.
Regards
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Well, as my dear "collegues" already mentioned, there's a lot you could do to improve performance, even though your somewhat limited (technically) with NAV 3.70 and SQL 2000
Anyway, the problem you describe "smells" like a blocking issue which would not be unusual during Invoice postings. To start fixing the problem it might be feasible to monitor the "Who is Who" about blocks.
Firstly I'd like to recommend to read my BLOG abou that issue:
http://dynamicsuser.net/blogs/stryk/archive/2008/11/03/blocks-amp-deadlocks-in-nav-with-sql-server.aspx
The TSQL scripts are related to SQL 2005; so please find herewith some SQL 2000 variants:
The Table:
The Stored Procedure:
The Alert (monitoring "SQL Server: SQL Locks- Lock Wait Time (ms); > 3000) and the Job have to be created manually.
ONce you know where the blocks are coming from you might be able to fix it; e.g. by optimizing C/AL code etc.. Most important here is to optimize the SIFT structures! Again, I dare to link to my BLOG:
http://dynamicsuser.net/blogs/stryk/archive/2007/10/28/included-columns-vs-sift-tables.aspx
Hope this helps.
Cheers,
Jörg
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool
Dont forget, that every read mean, that the server must read 8K......
So, if the reads are smaller, the server found the data faster.
Also you can anlyze the founded queries to see, whats the "costs" of this queries is
To find blocks you can use stryks little tool.
Sometimes it's a "hard work" to find out all the "bad programms". Also the NAV standard isn't perfomant ...
But if you find out all these programms, you can redesign your table structure / indexes, SIFTS, Buckets and your source self.
Here in this subforum are many post about the theme: How to perfom a NAV database to SQL.