cf
Sun Mar 09 23:54:15 CDT 2008
Bernard,
Thank you for the information, greatly appreciated.
For now it should be light access and db size should be fairly small, only one table with four or five text fields with maybe 50-60 records.
Should it *ever* get much busier I'd upsize it to sql. I build a e-commerce site once (10+ yrs ago) and it started getting quite busy and the Access db just would not handle more than 10 concurrent visitors without really taking a hit. But that's when I was into this much deeper, now it's a hobby and haven't used a db for quite some time.
Thanks again,
--
cf <cfnews@NOcharterSPAM.net>
I may be dumb, but I'm not stupid.
Terry Bradshaw
Of historical note on Mon, 10 Mar 2008 10:13:49 +0800
"Bernard Cheah [MVP]" <qbernard@hotmail.com.discuss> scribed:
|Both are methods to get into your mdb database, with old fashion odbc for
|Access driver while ole db style for jet driver.
|And generally OleDb is better than odbc.
|
|Btw - access is meant for small db size and request traffic, if you got
|heavy access, try msde or sql.
|
|--
|Regards,
|Bernard Cheah
|
http://www.iis.net/
|
http://msmvps.com/blogs/bernard/
|
|
|"cf" <cfnews@NOcharterSPAM.net> wrote in message
|news:20080309155744.062da570.cfnews@NOcharterSPAM.net...
|> Hi,
|> I'm putting together a small personal website that will utilize a small
|> Access db (only four text fields); currently I'm developing it on WinXP
|> with IIS 5.1 locally using classic ASP. I have it working but I'm not sure
|> which would be the best connection string to utilize? Both of the below
|> work fine:
|>
|> "Provider=Microsoft.Jet.OLEDB.4.0;" & "Data
|> Source=d:\domains\mydomain.net\db\soapbox.mdb;"
|>
|> "DRIVER={Microsoft Access Driver (*.mdb)};
|> DBQ=d:\domains\mydomain.net\db\soapbox.mdb;"
|>
|> Any insight into which would provide the best performance (albeit an
|> Access db) would be greatly appreciated.
|>
|> TIA
|> --
|> cf <cfnews@NOcharterSPAM.net>
|> I may be dumb, but I'm not stupid.
|> Terry Bradshaw
|
|