Board index Unix Questions

PICK

PICK

Post by Gary J. Haberma » Wed, 13 May 1992 01:56:59



Over the last week there have been several postings about PICK.   I have two
different version of PICK based systems running here:  Information which is
PRIME's version and uniVerse from Vmark.  Some people call PICK as Operating
system,  but I call it a database manager.  It has its own programming lanugage
(info-BASIC & uni-Basic)  they are very similar.  It also has its own Query language.

There are two version I know of for UNIX,  uniVerse  from Vmark and Unidata from
Unidata Inc.  I'm currently running uniVerse on my CDC 4680 to support  our Library
 system.  Perfromance  has been incredible 75 users doing input and data query can't make
the system break a sweat.  I hope to be running Unidata some time this summer on a new
3 cpu CDC 4680 with 14 gig for admin processing.  I don't know enough about Unidata yet to
give any  good information on it, but I do know that it supports both the standard PICK
query language as well as SQL.

There are alot of good articles in NEWS & Review about PICK.

Thurman Marketing Services
23181 Verdugo Suite 104a
Laguna Hills CA 92653

FAX (714) 380 - 3942

If you need any more information just drop me a note.

Gary

--------------------------------------------------------------------------


Widener University, Chester Pa.    Phone    : (215) 499 - 1044

 
 
 
Top

1. Here's your chance to advocate to someone picking a system.

1.  What is the scope of "Intranet" mean?

Intranet = Internal Web Server??
Intranet = Internal Web Server/Email??
Intranet = Internal Web Server/Email/Proxy Server??
Intranet = Internal Web Server/Email/Proxy Server/File & Print Services??
Intranet = Internal Web Server/Email/Proxy Server/File & Print Services/Database
(Oracle)???

2. How much money is allocated for this "Intranet" project?

It sounds like you are trying to do this cheaply, which will inevitably lead to
disaster.  I know your type.  Let's scrape some parts together, install some FREE
software, and put it into production ..... then one day something will happen,
hardware will fail and you won't have a backup, software will flake out and you
won't have support, you will get hacked and not know why, or worse, the users will
use the systems and drive performance into the ground and you won't be able to
scale.

My advice to you is "DO IT RIGHT THE FIRST TIME"!  I am currently cleaning up a
mess created which was created under this "Do everything as cheaply and lame as
possible philosophy".  Put simply, everyone loses!  The users have crappy
performance and the support people look like zombies because they get paged all
day and night when the wind blows through the house of cards.

However, if you must go down the trail of disaster make sure do things like hard
code IP addresses into the client software which will access the server.  Don't
ever do a backups and install frills like a UPS (uninterruptable power supply).
Make sure all users have the same password as their login.  Use as much FREE
software as possible and feel free to make changes to the source code to enhance
functionality.  When new versions of software become available, just compile and
put it into production, testing in uneccessary.  And never have a backup machine
on hand.  Lastly, if you connect to the Internet, use a 28.8k modem for the whole
company, frills like ISDN or a fractional T1 are not neccessary.

-Mike

p.s. - Run LINUX on a refurb Packard Bell for best results.  Make sure you use
refurb IDE drives too!

"I crack myself up!"

2. Setting secure directory ownership

3. Randomly pick lines from text file (cookies)

4. pppd failed

5. "Select" utility for picking files

6. Networking blues

7. Modem picks up but no login!!!!

8. Tekram 680C controller on Linux

9. SATA RAID 1 - which controller to pick?

10. picking locks ;-)

11. Retailer picks Linux for point-of- sale system

12. Please stop picking on Microsoft

13. How to detect phone ring but not pick it up?


All times are UTC
Board index