HP3000-L Archives

May 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Peter Chong <[log in to unmask]>
Reply To:
Peter Chong <[log in to unmask]>
Date:
Tue, 9 May 2000 09:21:05 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (44 lines)
Know your data is key, a System Analyst can be porting those huge data to some manageable form of data, Let say, user got a report may be daily, weekly, monthly or quarterly...Most case, we slice and dice data from Main Database to make some report.

One of Idea is make a report to file or load into a satellite DB(IMAGE), so ODBC with some Excel wizard to pull some data into local spread sheet program.. 

Let say, your Client Form combo lookup box base on SQL and SQL trying to read
millions of records to verifying for inputting back, the user PC will choke for
ODBC service(say not respond) and the user end up press famous ctrl + Alt + Del to discard this task and background ODBCServer run almost 90% of eHP3000 resource to support this simple SQL statement.  End up this task is almost impossible to proceed.

Therefore data can be poring into ODBC/SQL set for specific use, of course some
data synchronization will be required. I know, this is not like good old COBOL IMAGE programs... 

More likely data will flow Client - Transaction/Cache base SQL(IMAGE)  - IMAGE
to help manage millions records to less painful.

Cheers.


>>> "[log in to unmask]" <[log in to unmask]> 05/08/00 11:16PM >>>
Hi to all!
Often in this group there is a discussion what is the best solution to do a
connection between PCs and the HPs, doing data-exchange (from
TurboImage-Databases) and which ODBC-Interface works the best.

We tried several Interfaces and possibilities but we were not able to find a
usefull solution. Our databases are very big (up to 50 Million entries,
cross-connected and... and... and...). To offer only the customer dataset we
use takes about 14 hrs to proceed using the HP-ODBC-Interface...
The Order-Headers take nearly the same and the Sub-Headers have taken about
24 hrs to offer by ODBC... (10 Million entries...).

These times are unacceptable, but we can't decrease them...
We also tried the Minisoft-ODBC-Interface but with the nearly same results.

Our system is a HP979 and we want to be able to access the datas on the
PC/Windows-Side (Reporting, Analyzing,...).

Has anybody a hint or solution what could be the reason or what else we can
try?

Thanks a lot!

Holger Schrörs
QVC-Germany / IS&T - MIS

ATOM RSS1 RSS2