Tilted Forum Project Discussion Community - View Single Post

dunkelhelmut · 01-08-2004, 11:34 PM

I think you're overreacting here. At work, we have a database server that's being hit by many computers in the office all day, non-stop (for our product's automated test suite). If they're written well, ODBC drivers are designed to handle many simultaneous requests from different clients. I really don't think a spooler will be necessary. In fact, it may be more trouble than it's worth (it's another step in the process that could break, when the ODBC driver should already handle this for you)

Your main concerns here are the database type and the specs of the server. Of course, you'll want a good amount of speed, as well as plenty of RAM and disk space too.

If you're running 60+ cnxns with Access, then you're hosed. Access can barely handle 5-10. Heh. It will work, but don't expect any kind of speed from Access.

If you're expecting a lot of connections, and a lot of data, and a lot of throughput, then Oracle will be your best option. It's not real quick with a low amount of connections, and it's a huge disk space hog (my Oracle installation at work takes up 3GB), but it's designed to be reasonably quick and strong even with hundreds of connections.

SQL Server may not be a bad option either. It's easier to use than Oracle, and it's lightning fast with a lower number of connections.

There are also a number of free database solutions with ODBC support (MySQL and Postgres are the main players), so you can play with those as well.

Whew.

01-08-2004, 11:34 PM	#2 (permalink)
dunkelhelmut Insane	I think you're overreacting here. At work, we have a database server that's being hit by many computers in the office all day, non-stop (for our product's automated test suite). If they're written well, ODBC drivers are designed to handle many simultaneous requests from different clients. I really don't think a spooler will be necessary. In fact, it may be more trouble than it's worth (it's another step in the process that could break, when the ODBC driver should already handle this for you) Your main concerns here are the database type and the specs of the server. Of course, you'll want a good amount of speed, as well as plenty of RAM and disk space too. If you're running 60+ cnxns with Access, then you're hosed. Access can barely handle 5-10. Heh. It will work, but don't expect any kind of speed from Access. If you're expecting a lot of connections, and a lot of data, and a lot of throughput, then Oracle will be your best option. It's not real quick with a low amount of connections, and it's a huge disk space hog (my Oracle installation at work takes up 3GB), but it's designed to be reasonably quick and strong even with hundreds of connections. SQL Server may not be a bad option either. It's easier to use than Oracle, and it's lightning fast with a lower number of connections. There are also a number of free database solutions with ODBC support (MySQL and Postgres are the main players), so you can play with those as well. Whew. Last edited by dunkelhelmut; 01-08-2004 at 11:38 PM..