SQL Server Performance Forum – Threads Archive

difference b/w access and sql

wht are the pros and cons of using sql server as backhand and wht are the pros and cons of using ms-access as backhand with vb and vb.net
which one is best.

Big difference, SQL Server is a database. Access non.
Luis Martin
Moderator
SQL-Server-Performance.com All postings are provided â€œAS ISâ€ with no warranties for accuracy.

Check:
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=2594 Luis Martin
Moderator
SQL-Server-Performance.com All postings are provided â€œAS ISâ€ with no warranties for accuracy.

<blockquote id="quote">quote:<hr height="1" noshade id="quote">Originally posted by LuisMartin Big difference, SQL Server is a database. Access non. Luis Martin Moderator SQL-Server-Performance.com All postings are provided â€œAS ISâ€ with no warranties for accuracy. <hr height="1" noshade id="quote"></blockquote id="quote"> That’s your opinion, Luis. [<img src=’/community/emoticons/emotion-4.gif’ alt=’

‘ />] nashik, there is no _best_ solution. Too many factors to be considered. Generally SQL Server (or MSDE for that matter) is preferable, but this really depends on your requirements, enviroment, budget and so on, and so on… However, since this is a fairly common question, you might want to google for information. It is certainly helpful when you first determine your need before searching, so you better know what to search for. –Frank http://www.insidesql.de</a>

In any case SQL Server is higher hand than MS Access and for information review below articles:
http://www.databasejournal.com/features/msaccess/article.php/1490561
http://www.mssqlcity.com/Articles/Compare/sql_server_vs_access.htm HTH Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

As Satya said, the term SQL "Server" comes from the word SERVICE which really gives you the difference between "file access" and "data management and service". The concepts are far different. So, MsAccess is "accessing" a File (the "mdb" in this case) while SQL is reaching a service, something to be requested and served … from another "entity" (server, machine, chinese guy …), what it was once called "client/server" environment. Sometimes that is forgotten … Then u come up with users, maintenance issues, dedicated servers, performance, etc etc … a quite different story in those different worlds. The other problem is "should I develop with .NET, MsAccess VBA, or Visual"??? Thats another story too, …. It will always depend on your needs, sure.

What it comes down to is failry simple… If your writing a relatively small, "piss ant" application that has less than 5 or so simultaneous users and the data being stored (table size) is relatively small (under a couple thousand rows, per table), and there are a small number of tables, and your orginazation is very small (cheap), and you don’t need a super fast, super reliable DB, then MS Access is a conceivable alternative to SQL server. Sure MS Access will work with more users, bigger tables, and possibly run fairly quickly in the beginning stages of your development, but I’ve found that in a production scenario, the Apps I’ve built using MS Access quickly get too big or too "used" (more users than expected) to function reasonably, and therefore we migrate them to SQL Server. The good thing is, the migration from MS Access to SQL Server isn’t that hard, so you can always start small and pay the big bucks later to migrage your APP to SQL Server if you need to. However, if you expect multiple users, or if your database will grow quickly, or speed/reliability are in high demand, you should probably consider a higher end DB, of which SQL Server is just 1 option. I hope that helps.

]]>