Results 1 to 8 of 8
  1. #1
    Join Date
    Apr 2008
    Posts
    1

    Unanswered: Scope & Limitations of MS Access and SQL Server

    Hello everybody

    My office gave me assignment to find out the scope & limitations of the two Microsoft database applications - MS Access and MS SQL Server. After the findings, we have to chose the more appropriate database for our new project, which will have a humble start but may grow big in a year or two.

    I will apreciate the info in facts & figures (not only in general).

  2. #2
    Join Date
    Jan 2007
    Location
    UK
    Posts
    11,434
    Provided Answers: 10
    Define "big"?
    George
    Home | Blog

  3. #3
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    MS Access should not be used for more than five or six concurrent users.
    MS Access should not be used for large, Enterprise applications. It is an appropriate for small to mid-size utility applications.
    SQL Server (and other true database servers) do not include a user interface, so you will need to develop an application to input and output the data using VB, ASP, or some other development platform (even Access).

    Describe the nature of your business requirements.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  4. #4
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    You can safely remove Access from the back-end equation, and put your data into SQLExpress. This way, when you grow out of the allowed boundaries of SQLExpress, you can put the database into SQL standard or enterprise. SQLExpress is free vs. Access.
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  5. #5
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    ...though he'll have to decide upon a development platform for his interface if he is going to use a true database server, while Access has forms and reports built into it.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  6. #6
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    After re-reading the last line of the original post I think the guy/girl wants us to do a comparative research for him/her. Anybody has free time for pro bono work?
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  7. #7
    Join Date
    Jun 2003
    Location
    Ohio
    Posts
    12,592
    Provided Answers: 1
    Eh, he hasn't been back to the boards, so I'll assume he got what he wanted.
    If he wants a comparative analysis, hopefully he'll just try googling "access SQL Server comparison", which would bring this to the top of the list:
    http://www.microsoft.com/sql/prodinf...-features.mspx
    ...and thats all the pro-bono web surfing I'm going to do today.
    If it's not practically useful, then it's practically useless.

    blindman
    www.chess.com: "sqlblindman"
    www.LobsterShot.blogspot.com

  8. #8
    Join Date
    Oct 2002
    Location
    Baghdad, Iraq
    Posts
    697
    Quote Originally Posted by rdjabarov
    You can safely remove Access from the back-end equation, and put your data into SQLExpress. This way, when you grow out of the allowed boundaries of SQLExpress, you can put the database into SQL standard or enterprise. SQLExpress is free vs. Access.
    Another way of looking at it: the JET database engine (the backend for Access) is also free and available on recent versions of Windows. It's also an installation-free solution, e.g. you could make your app run on a USB thumbdrive.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •