Has anyone compiled any reasons for buying or developing in UniVerse vs. Oracle or some other relational database?
I keep hearing things like: - UniVerse doesn't cache like a relational db - UniVerse doesn't use indexes properly - UniVerse selects aren't as fast as a relational db and I don't know what to reply. I've googled Multivalue vs. Oracle and found a bunch of complaints that UniVerse doesn't manage data or security like some people think it should. I have a friend who said that sometimes he just wished someone would tell him what to do. He would probably not like UniVerse. I found one white paper on IBM: ftp://ftp.software.ibm.com/software/data/u2/pubs/whitepapers/202452.pdf It would be nice to see hard data like: - Universe vs. Oracle speed benchmarks such as - time to select a 4 million record file. - time to update 4 million records. - time to LIST 4 million records. - UniVerse vs. Oracle tables per (Order Entry, for instance) app - number of UniVerse programmers to support a $100m sales company vs. Oracle - Cost of a UniVerse system vs. Oracle. Oracle here is generic for any relational data base management system, I suppose, including DB2. -- Louie in Seattle ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
