Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Great Plains Slow on SQL 2000

Status
Not open for further replies.

DomP

IS-IT--Management
Oct 15, 2001
53
US
We are using GP 9 Standard on a SQL 2000 Standard box. Single processor Xeon 3.06 with 3 gigs of ram.

We have approx 25 GP databases running on this server along with 25 in another SQL application.

It takes minutes to switch from one client to the other in GP so I'm wondering if there could be a configuration issue or if these is flat out too many databases to support on one server. Once we are in a database GP runs fine. It's just the slowness in switching from one to the other.

Thanks,
Dom
 
When you say "switch from one client to the other in GP" do you mean to switch companies?

There are SO many things this could be.... First question I would ask is, does it also take this long if you do it directly on the server and as 'sa'?


Victoria
Flexible Solutions, Inc.
 
Yep, switching companies, and yes, happens on the server as sa.
 
One other test I usually do to check GP 'speed' is to go into SmartList and choose Account Transactions to see how quickly it will be bring back the first 1000 records. It should be a few seconds.

Next step is probably to see if you have customizations or 3rd party products that are loading something up whenever GP switches companies? You could also create a DEXSQL.log to trace what is being called when you switch companies and if there are any errors or repetitive loops.

Victoria
Flexible Solutions, Inc.
 
Victoria,

Thanks for your help. FWIW ---

Just an update in case you experience this. After opening an incident with Microsoft they informed us that this is a known issue. I can't say if everyone experiences it however.

It turns out that the slow login is caused because of too many entries in the SY07110 table. This table is the menu master table and it is used by Advanced Security. Seems it has the potential to build over time. Once cleared everything was fine. While this may re-occur it's nice to know we can combat the problem.

Dom
 
Dom,

Thanks for letting us know what it turned out to be. While I have heard of this before, it's not very common, so it isn't usually one of the first places we look. But helpful to add to the list of possible issues, for sure.


Victoria
Flexible Solutions, Inc.
 
DomP you deleted the Sy07110 table. Did your advanced security still work? Is the information in this table rebuilt by GP?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top