Slow after upgrade to 7.6.3 mssql

[ControlBaker]

Our company has recently upgraded from Prevasive to MSSql and Version 7.6.3. We are experiencing extreme slowdowns on processing of Pro. Orders and Printing Inventory Reports. I have tried turning off Anti-Virus software on both the server and user stations. Will a file rebuild help? Does anyone have any suggestions?

 

[kscheeler]

How many users and what type of SQL server did you load it on. Processor's, Memory etc..

Were you on 7.6.300 before as well? Some functions will be slower but most will run as well as in Pervasive. In some cases, the slowdown is updating to 7.6.200 + from a previous version.

Within SQL Enterprise Manager, drill down under the server, management, process control and you'll see all of the users that are connected in SQL. Scroll to the far right side and see how they are connecting. It will either be TCPIP or Named Pipes. The preference is TCPIP

Kevin Scheeler

 

[NEmacGuy]

Kscheeler is right, you will want to check if you have the client network components installed on your work stations. Then you can set the preferred liabrary to TCPIP.

Still an issue, when your data was converted from btreive to SQL were they are errors in the conversion log ? If so perhaps you are missing indexs. Get a copy of the MSLChecks from exacts web site. Run it and it will verify the indexs.

Still an issue, Exact has a technotes 01.533.826, 02.017.030 which mention what I have above and more.

If after that still issue,
What are your server specs, network, workstations ?

Finally there still are reports,process.. that are a lot faster on btreive than MSSQL. Btreive is a transaction database engine, if you are running a straight list it is hard to beat its performance.

 

[kstickler]

I used the following solution (pulled from Exact portal) when we were having problems posting...it took forever before we made these changes:


Answer:

Windows XP and 2000 workstations have a wait or run extremely slow or timeout state when posting large reports or data intensive processes in Progression. A possible solution to change the following settings. These settings only apply to Windows XP and 2000 workstations.

The default maximum number of ephemeral TCP ports for Microsoft Windows is 5000. To increase the maximum number of ephemeral ports you must set the following registry parameter:

WARNING: The incorrect use of Windows Registry Editor may cause serious problems that may require a reinstall of the Windows operating system. Exact Software cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Step1:

From Windows Start, Run, Regedt32.exe

Select, Hkey_Local_Machine\System\CurrentControlSet\Services\Tcpip\Parameters

From the Edit Menu, Select NEW, Select DWORD Value. Type the Value Name: MaxUserPort, select Enter.

Double Click on the new value name, MaxUserPort, from the Value window, select Decimal, set the Value data to 15000, select OK.

Step2:

From the Edit Menu, Select NEW, Select DWORD Value. Type the Value Name:TcpTimedWaitDelay, select Enter.

Double Click on the new value name, TcpTimedWaitDelay, from the Value window, select Decimal, set the Value data to 30, select OK.