× 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.



We don't use ODBC. We use the .NET stuff that comes with Client Access. Exact name/term eludes me since I'm an amateur on the .NET side.

From the article Eric kindly provided it does seem relatively easy to turn on a processor for a month and see what the result is, if any.

Sam

On 6/4/2013 7:48 PM, Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:
Just a thought...if it only seems to be your .NET apps that have any
noticeable performance issues are you separating the ODBC jobs, etc into
their own subsystem? Then you can adjust memory pools, etc just for those
jobs and focus on the direct issue vs using a light anti-tank weapon to
kill a mosquito?


Thanks,
Tommy Holden


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.