tp@mccall.uucp (02/07/90)
I've read about databases but never used one before. Thus forewarned, could anyone answer a few questions for me? I am writing an application that has to maintain some moderately complicated data structures on disk and get to them in reasonable amounts of time. I could do this with indexed files, but it would be easier with a database, so I'm trying to convince management that I need one. I am considering Rdb for various reasons. The only info I have on it is the SPD. 1) I think relational would be simpler to use and more flexible in the long run (I know it will handle this application just fine). 2) We already buy stuff from DEC, so it is easier than searching through myriad 3rd party vendors. 3) I'm currently trying to justify switching to CD-ROM for media and documentation updates, and I figure Rdb should be on those, which would be convenient and save us money on updates. The questions: 1) Are any of the above reasons faulty? 2) Are segmented strings sufficiently general to implement BLOB's (Binary Large OBjects)? I have some unstructured data that I'd like to stick in the database for future access. I'd like to have this pointed to by a standard relation, and for all usual concurrency and integrity controls to apply. 3) Is network access to a remote database transparent and fully functional, or are there restrictions? In particular, I need concurrent local and remote access, as I do remote support on these applications. 4) If I write a set of library routines and/or shareable images that access an Rdb database, to be shared by several applications, do I need the full development version of Rdb to link against those libraries/images? In other words, if there is only one system on which development of database access software would ever be done, but other systems where people would need to link against the shareable images thus produced, is it sufficient to have Rdb Runtime Only installed on those other systems. 5) Are there any other packages I REALLY should consider? Price is an issue, but so is application development time. I can't take the time to do an extensive search, and I can't afford to get something cheaper that would require more effort to use (as it would increase development time). On the other hand, if there are packages of equal or better functionality that are SIGNIFICANTLY cheaper, or packages of equivalent price that are SIGNIFICANTLY better, I would like to know about them. My development environment and my target production environment are all LAVC's of VAXstations. I'll summarize any useful responses I get via email back to the same groups to which this message is posted. Thanks. -- Terry Poot (800)255-2762, in Kansas (913)776-4041 The McCall Pattern Company, 615 McCall Rd., Manhattan, KS 66502, USA UUCP: rutgers!ksuvax1!mccall!tp Internet: tp%mccall@ksuvax1.cis.ksu.edu