You and others have often suggested copying the database locally and
seeing if the performance still suffers to rule out the network
components. Are you able to try that? Sorry if I missed that post.
--Mike
On 2014-08-25 15:02, Ted Roche wrote:
Update: problem still there.
WAG KING's guess of swapping out workstations: the app shows the same
problems when she works at someone else's desk, so we're guessing it's
not
hardware at the workstation end.
Rich thought networking, also one of my favorite things to blame, but
Tech
folks insist they are seeing no problems in the logs. (Yes, they might
not
be looking at the right things, or know what to look for, but...)
Tracy's bloat theory looks deflated: we did a full pack, drop and
reindex,
and even a full DBC creation from script, no significant change in
size.
We're reviewing the code to see if there might be something funny like
"create all the temp files on the network server and forget to close
them"
but we're talking about veteran experienced programmers and an app
that's
running all over the country, just not this particular custom feature.
Will update if we learn anything...
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
