Hi.
I'm building a web site where I need a DB. Is not a comercial site and don't have very special needs.
In your opinion should I use MS Access or SQL Server.

Thanks.

MGil

If you can, use SQL Server. Access is created as desktop DB. It can work on web and for small sites it's fine. If you're not expecting huge number of visitors Access will do the job.
In other words, if you can choose, choose SQL Server. If you can't, Access will finish the job.

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
Hi.
I'm building a web site where I need a DB. Is not a comercial site and don't have very special needs.
In your opinion should I use MS Access or SQL Server.

Thanks.

MGil
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

Viktor Farcic

TalkZone Manager

Hi,

You can run quite busy sites with Access 2000 and using Jet OLEDB Connection strings. Most of the time websites are just performing read operations on the backend so you are not likely to experience record locks. If you are going to have lots of write operations (additions and modifications) performed by lots of users at the same time then definitely go for SQL Server or similar. If only one or two people are updating the database (say the site owner/admins) then you would be surprised at how much traffic you can throw at Access 2000. DSNless connections will help improve performance of an Access backend as well. If you want to record your web logs straight into a DB backend or of custom usage statistics then you should also go for SQL Server or similar.

Of course PHP, MySQL and PHAkt looks like quite a good way to go. I haven't tried PHAkt yet but will soon. You should get a lot better performance than Access and probably close to equal if not better than SQL Server especially if your web server is being run on Linux. You'll certainly save thousands in license fees going the Opensource route.

Edited by - kumaschow on 08 Apr 2002 12:58:18

Thank's Viktor and kumaschow.

But there is another issue that I have in mind about Access DB...

I only need a short number of insert operations a day in my DB. But probably I will have a large number os users visiting my site at the same time. Access can work fine on this conditions and simultanious readings?...

And about the connection...Should I use a "Jet OLEDB Connection string" or a DSN connection.

Thanks again.

MGil

Use "Jet OLEDB Connection string". It's faster.

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
Thank's Viktor and kumaschow.

But there is another issue that I have in mind about Access DB...

I only need a short number of insert operations a day in my DB. But probably I will have a large number os users visiting my site at the same time. Access can work fine on this conditions and simultanious readings?...

And about the connection...Should I use a "Jet OLEDB Connection string" or a DSN connection.

Thanks again.

MGil
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

Viktor Farcic

TalkZone Manager

I've read a topic about using MS Access as the Database Server a certain website. It says that it can accomodate a little bit of traffic but only 10 users or less than that can access your database.