Results 1 to 8 of 8
  1. #1
    3 Star Lounger
    Join Date
    Nov 2002
    Location
    South Carolina, USA
    Posts
    257
    Thanks
    0
    Thanked 0 Times in 0 Posts

    coverting to SQL (access 2003)

    OK... I have been advised by our IT department to start thinking about converting all of my access databases to sql. I have asked why...but I get looks like "it is too high tech to explain". Can anyone tell me the pros of converting to SQL? Why should I?

    Thanks, Deborah

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: coverting to SQL (access 2003)

    Access works very well for relatively small databases with a limited number of simultaneous users.

    Migration to SQL Server is advisable if
    - You have tables with millions of records, and/or
    - You have a large number of simultaneous users, and/or
    - You need more sophisticated security and management tools than Access offers.

    You'd transfer the data tables to an SQL Server database, and you could still use Access as a frontend for the users.

  3. #3
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: coverting to SQL (access 2003)

    Based upon the looks you are getting (and I assume no answer), I'm guessing that the reason they want you to convert is two-fold. There is the age-old prejudice of IT depts that Access "is not a real database", and also they feel they will have more control over you if you convert to an SQL database that they control. Given that it will take time and money to convert, I'd ask for a formal statement of their rationale of why it needs to be done, so you can do a cost/benefit analysis.

    Hans mentioned some reasons to convert to an SQL backend. Additionally, an SQL database is more stable and less prone to corruption. This does not mean, however, that it is always the right decision to upscale to SQL server. It just depends on the situation.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  4. #4
    Platinum Lounger
    Join Date
    Dec 2001
    Location
    Melbourne, Australia
    Posts
    4,594
    Thanks
    0
    Thanked 27 Times in 27 Posts

    Re: coverting to SQL (access 2003)

    Can the Access front end cope with many users if the backend is SQL Server?

  5. #5
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: coverting to SQL (access 2003)

    You should give each user a copy of the frontend, regardless of the backend.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  6. #6
    Platinum Lounger
    Join Date
    Dec 2001
    Location
    Melbourne, Australia
    Posts
    4,594
    Thanks
    0
    Thanked 27 Times in 27 Posts

    Re: coverting to SQL (access 2003)

    I understand that Mark, my question (if slightly unexplicit) was, is there any problems using an Access FE with a sQL BE with many users?

  7. #7
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: coverting to SQL (access 2003)

    None at all. That is one of the reasons you'd convert to an SQL backend so you could use it with more FE users than Access can comfortably handle.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  8. #8
    Platinum Lounger
    Join Date
    Dec 2001
    Location
    Melbourne, Australia
    Posts
    4,594
    Thanks
    0
    Thanked 27 Times in 27 Posts

    Re: coverting to SQL (access 2003)

    Thank you.

Posting Permissions

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