×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Happy Friday, All!
With the increased amount of web pages we are using on our systems, I am noticing that the QZDASOINIT jobs appear to be chewing up more and more CPU cycle times. That being said, I am looking into moving the jobs to their own subsystem and changing the memory pool on them (as per a wiki document I found). However, I'm wondering if there's anything else I can do to curb the bad habits of these database queries?
One thing I think will make a difference is to move to a different strategy other than "select X for lib.member" used in virtually all of the web pages we host. However, I thought I'd hit the group up for some advice to see what everyone else is doing.
If it makes any difference, the i5 is being used to house the data and we have Windows Server 2003 Web edition hosting the web (ASP / ASPX) pages. It is these pages that access the i5 through an ODBC string.
Thanks!
/b;
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-6746
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
