bking@ersys.edmonton.ab.ca (Barry King) (05/31/91)
The organization I work for is currently attempting to establish a 'standard' database engine for OS/2 development. There is a requirement for client/server support, inter-operability with DB2 as well as stand alone applications. SQL Server is clearly an excellent choice for served applications. However, for standalone apps, SQL Server is, mildly put, major overkill. So far I've been told that it will run in 6 Mb standalone. Can anyone tell me if this is the case? That is, with 6 Mb, OS/2 EE 1.3 and SQL Server in 6 Mb, will there be enough left over to do anything useful without thrashing the poor hard drive to bits? An edict has been passed down that whatever DB engine we choose must be accessed via SQL - that is, no direct API calls. This, to me, is not a realistic requirement but we're talking standardization here...anyway, that being what it is, does anyone have other suggestions for the standalone situation? There's XDB, SQLBase (Gupta), DataEase...what would the mimimum useable memory requirements be for these? I know pretty much what the vendors say but experience has shown me that these numbers are merely guidelines - I'd prefer numbers from people who are actually using these products in production. Performance is an issue, of course, especially with the overhead of SQL so any comments would be appreciated. Please respond via e-mail and if there are enough responses to warrant it, I will summarize. Thanks. Barry King bking@ersys.edmonton.ab.ca Edmonton Remote Systems: Serving Northern Alberta since 1982