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



   All this is easier said than done when the client has no source code to
   the package. I'm having enough trouble convincing them that replacing
   their 400 package with an SQL Server solution. It's time to get them a
   trip to Rochester.

   I walked into a meeting with their IT staff this AM. I'm old enough to be
   the father of everyone in the room. Fortunately, I never spent any time in
   Indy during my mis-spent youth.  :-))
   -- 

   Paul Nelson
   Arbor Solutions, Inc.
   708-670-6978  Cell
   pnelson@xxxxxxxxxx
   -----midrange-l-bounces@xxxxxxxxxxxx wrote: -----

     To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
     From: "Pete Massiello" <pmassiello@xxxxxxxxxxxxxxxx>
     Sent by: midrange-l-bounces@xxxxxxxxxxxx
     Date: 04/10/2006 09:58PM
     Subject: Re: *Max4GB or *Max1TB

     Paul,

      I think you would be better off determining which access paths can be
     shared (subsets of the other) and then sharing those access paths. Then
     determining which Logical Files are not being used and delete them.  If
     you think about it, each time a write is done to the physical file, you
     have to go out and update those 250 logical file access paths.  That
     takes a lot of time.

      While you might get some improvement with changing from 4Gb to 1TB as
     the size, I think the number of logical files is the issue.

     Pete

     ---------------------------- Original Message
     ----------------------------
     Subject: *Max4GB or *Max1TB
     From:    pnelson@xxxxxxxxxx
     Date:    Sat, April 8, 2006 11:16 am
     To:      midrange-l@xxxxxxxxxxxx
     --------------------------------------------------------------------------

     > I've got a client experiencing performance problems with his software
     > package. Many of the files have a huge number of logicals built over
     them
     > for various purposes. One has over 250 logicals and joined logicals.
     All
     > of the files are defined as having an acces path size of 4GB.
     >
     > This system is also being hit with lots of ODBC requests that were
     > permitted to be built by the previous IT manager (windoze bigot).
     >
     > I know how to throttle back the ODBC impact, but should I change the
     acces
     > path size to 1TB for just the logicals or both the physical and its
     > associated logicals to improve the overall performance?
     >
     > Thanks
     > --
     >
     > Paul Nelson
     > Arbor Solutions, Inc.
     > 708-670-6978  Cell
     > pnelson@xxxxxxxxxx
     > --
     > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
     > list
     > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
     > To subscribe, unsubscribe, or change list options,
     > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
     > or email: MIDRANGE-L-request@xxxxxxxxxxxx
     > Before posting, please take a moment to review the archives
     > at http://archive.midrange.com/midrange-l.
     >
     >

     --
     This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
     list
     To post a message email: MIDRANGE-L@xxxxxxxxxxxx
     To subscribe, unsubscribe, or change list options,
     visit: http://lists.midrange.com/mailman/listinfo/midrange-l
     or email: MIDRANGE-L-request@xxxxxxxxxxxx
     Before posting, please take a moment to review the archives
     at http://archive.midrange.com/midrange-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.