Nav 2009 on SQL 2014

Business Central/NAV Technical Forum
1

Hi!

I’ve upgraded a customer from an old slow sql 2005 to a new vmware (esxi 6.0) virtual sql server 2014 std, with all ssd, 2 mirrored disks for C and D for database. Db size is about 30GB and they have 20GB ram for sql server and 4 for the OS. All is using very little resources and they are around 10 users.

I first did an sql backup and restore and i’ve also tried with nav backup and restore. The problem is that now, after the migration, when the customer, using the classic client, creates a new order, and tabs between lines or enters an item nr on the line and presses tab, it hangs for 5-10 seconds. This happens randomly about 3-4 times a day and can last for up to 20 minutes.

I’ve checked all possible tasks that might run, defrag for instance which i’ve turned off, and any other without finding anything that runs. It also happens randomly which means that it doesn’t seem to be something scheduled.

I’ve followed all recommendations for sql on vmware. I tried to setup Stryks SSI Block detection but it fails on Step 4 when creating the Block Alert, saying: The specified object_name (‘General Statistics’) does not exist.

Any kind of help or pointing in the right direction to go next would be much appreciated. I’m thinking perhaps to install sql 2008 r2 and see if it will run smother on it.

Kind regards,

Sebastian Sidor

2

The soltuion to this problem was to update the NAV Client. The customer was running 2009 Sp1 with a build number around 29000 something. So i updated it to 2009 R2 (6.0.32012) then to 6.0.38655, had to resintall the software, meaning i couldnt just replace the files because it was complaining about .stx file. After that i opened it in 6.0.38655 and it updated the database which took a while and after that it worked perfectly!

3

Unfortunately this was not the solution. The only thing was that the searches and browsing went faster but they still get “hickups” and slow performance for around 10 minutes 3-4 times a day. Next step is to downgrade to sql 2008 r2 and see if that helps…