Re: Choosing a standalone, SQL queryable database.

it seems to me from your description of the situation that "you are hosed!" if using a freeware database such as postgres or mySQL requires months and of paperwork and red-tape, then there is no solution other than to write your own simple database tool (which is not hard in Perl or Python or PHP).

what is puzzling about your scenario is you seem to believe you could put "in-house" code in place on the servers without delay, but to use something like postgres presents an issue. this does not "pass the smell test" as they say. something is not as it seems.

if you can put "in-house" code in place without delay or red-tape, download the source code for postgres or mySQL, make some "localizations" to the source, and then compile it on your target server (the compiler is also free and available in source code). you have then deployed "in-house" code and have solved your problem.

ultimately, it seems that whatever project this is for, said project is of very low priority to the decision makers or stakeholders who could eliminate the months of paperwork and red-tape if it were of sufficient importance and priority. if this is case, why should you worry about it if management is unwilling to move it along? note the issue in your next status report and make it management's problem.

"Matt Sielski" <matteus_at_vt.edu> wrote in message news:56ff83b7.0105251228.1316e4ab_at_posting.google.com...
> I'm developing a Perl CGI application for an Apache webserver running
> on a Solaris box, not sure of the verions of either. The application
> will need a database, and right now we're all trying to decide what
> will be best. We have a Sybase server available, but will need
 months
> of paperwork and red-tape to use it. The same goes for installing
 our
> own database solution on the webserver (like mySQL) or adding a new
> server to the network. In essence, we need a local, standalone
> database, like a flatfile or DBM kind of thing. The problem is that
> we need to query this data, ideally with SQL. AFAIK there is no way
> to run SQL on flatfile/DBM since they're not relational systems. Our
> concurrent user count is fairly low (less than 100 at a time) and the
> volume of total DB hits would be under 1000 a day. Any suggestions
 of
> a standalone local database that can be SQL queried? Thanks, Matt
>
> If this isnt the right newsgroup, please let me know.
Received on Sun Jul 22 2001 - 01:27:23 CEST