Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL Server vs. MS Access

Status
Not open for further replies.

ncar35b

Technical User
Jan 10, 2003
55
US

Hi. I'm not really sure which forum to post this on, but here goes. I have to create a website that makes calls to a small database (10 tables, under 3mbs). The website will be receiving a modest amount of traffic (250,000 - 300,000 hits per month). I'd like to get developers' opinions if you think I can use Access (I should be ok with their 255 concurent user limitation), or if I need to go with SQL Server.

Thanks!
 
SQL is always a better choice. However, having said that there are some things to consider. Are you hosting this on a server you have access to the console? Is this hosted by someone else not providing you with the choice? If the 2nd is true, Access is a great alternative to a small-mid sized site. How long are these records going to be stored. I forget but Access has a modest limitation to how many records can be stored. The nice thing about an Access solution, you don't need any special database engine. Just create your Access mdb file and upload it to your website.

If you have the money and the resources for SQL, I'd go that route. you never know if you may outgrow Access. But then it's not hard to migrate.

Hope that helps.

P.S. I do websites both ways.
 
OK my 1c

Access = free (for most people who have purchased office)
SQL server not freee but way better
MSDE (read free version of SQLServer) free and way better than access.\

Supports using memory to run querys, advanced indexing, triggers, storedprocs, better security..... etc...

MSDE Limitations - database can't grow past 2 gig, 5 parallel querys can run (no limit to the number of user connections, just how many querys can be executing at any one time...
Doesn't support Optimizer hints (just ignores them)

go SQL/MSDE you will never look back as access being the "good days
 
Hmm.. never thought of that. Does MSDE require you to install an "engine"? Keep in mind the only reason I would choose Access is that it's totally managable on a remote website.
 
The MSDE is the database engine.. now comes the difficult part (it doesn't have any development tools - but if you have SQL EM or Query Analyser they work with MSDE fine)

for remote work (I have a webpage that only I can log onto and doesn't have any references to it that I do all my remote db work on... I just issue commands and return resultsets if they have them. to the web page as a result.)

There is also a kick but version of Enterprise Manager (Web based - running ASPX (dot net 1.1) on planet source code (i think) check it out... free open source)

Sooooo use some version of em or TSQL to create your database and procs then ... yeeeha deploy to the web! free - free - free

:)
 
Thanks pkailas and NoCoolHandle. I will have complete access to the server, so that's not a problem. It looks like SQL Server is probably the way to go. Not worth the risk of outgrowing MS Access.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top