Dear concern,
We have 1 client using NAV 6.0 R2 SQL DB(IN Version) having size of 7 GB only.Before Go Live they were working on NAV 6.0 SP1 (Classic), but somebody convert Database in NAV 6.0 R2.Now they are working on NAV 6.0 R2. They are using 1 company having 4 branches (branches mapped as responsibility center), 50 users are working concurrently. There are facing locktable issue on every transaction, system is too slow and even sometimes they are getting deadlock error also.
Their Hardware configuration as :
Processor : Intel(R) Xeon(R) CPU E5-2420 0@1.90 GHZ (2 Processors)
Memory (RAM) : 64 GB
System Type : 64-bit Operating System
We have created .ndf files in seperate files (D Drive) and .ldf files are on different drive (E Drive) having seperate files.
Please help me it's urgent ](*,)
0
Comments
I want to confirm one more thing, is there any speed/locktable/deadlock issue if database has been converted from NAV 6 SP1 to NAV 6 R2?
Most of the cases these types of errors occurs due to SQL database issues. When you just convert the database without proper migration most of the time the database index are not working as it should be. therefore it is always good to rebuild your database index and check.
I don't see the database size have a much of a problem with the slowness.
Best regards,
Tharanga Chandrasekara.
For more info : NAV Community Blog |NAV General Blog]
Look for the "low hanging" fruit first. When you went live things like this can start causing problems.
Another item that can caus slow downs is posting analysis view. Check your settings and see what is happening whenever you post.
If you have users running NAV vis RDP, make sure the terminal server is not overloaded.
http://mibuso.com/blogs/davidmachanick/
Automatic cost posting is unchecked and yes users are working on RDp but there is no overload on Terminal server
what is your disk configuration? What security model do you use?
RAID5, 64 GB RAM, OS : Windows 2008 R2 server, SQL 2008 R2
I would suggest you download a tool that will help you identify what is going on.
http://www.stryk.info/downloads.shtml
Download "Block Detection (Presentation Pack from "Decisions 2010")"
There is a PDF file in the zip file that explains how to install the tool and how to use it.
This should give you some hints what may be wrong, or what tables indexes are affected.
The issue may be also related to the SIFT keys, anyhow wuthout further investigation it is difficult to say anything.
I hope this helps.
RAID5 - could be a reason. RAID5 is terrible slow. I think raid10 is a lot better fro nav. I use raid5 on test system to save disk space - and have a lot performance issues.