data providers

Discussion in 'ASP.NET / ASP.NET Core' started by tunnel, Sep 11, 2003.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. tunnel

    tunnel

    Hi All

    Looks like I've been doing things wrong from scratch ... I use Jet OLEDB currently for an app which potentially could have 100 simultaneous users. From what I read from Microsoft, Access isn't good if my app is to be used by simultaneous users. Maybe they're biased and are trying to push their SQL server, as my Access app seems to be OK in my limited testing (3 users). Comments?

    Anyway it might be an idea for me to go to MS SQL or MySQL. Is there a comparison I can read as to which is best? More importantly, what does it take to convert my app to MS SQL or MySQL? I know I need to play with the connection string, but what's required to convert the Access database tables? What other things need doing?

    Sorry these questions are so basic but I'm just trying to make sure I restart on the correct foot! Assume I know nothing, which is pretty close. Any links to good info sites appreciated.

    Thanks for any help!
    Graeme
     
    tunnel, Sep 11, 2003
    #1
  2. Takeshi Eto

    Takeshi Eto DiscountASP.NET Staff

    You may want to get MSDE 2000 (Microsoft SQL Server 2000 Desktop Engine), a free personal database built on core SQL Server technology.

    MSDE is compatible with other editions of SQL Server so you can use the same core code base, making your code portable from your desktop to a production site.

    More Info on MSDE 2000:
    http://www.microsoft.com/sql/msde/default.asp
     
    Takeshi Eto, Sep 11, 2003
    #2
  3. Bruce

    Bruce DiscountASP.NET Staff

    True, MS Access is not intended for high concurrent usage. If you expect lots of connection to the database, you should consider upgrading to Access.

    It is a natural extension to go from MS Access to MS SQL. MySQL lacks some of the feature of MS SQL.

    MS Access has a upsizing wizard which convert your access database to a MS SQL or MSDE database. Check MS Access's documentation.



    quote:Originally posted by tunnel

    Hi All

    Looks like I've been doing things wrong from scratch ... I use Jet OLEDB currently for an app which potentially could have 100 simultaneous users. From what I read from Microsoft, Access isn't good if my app is to be used by simultaneous users. Maybe they're biased and are trying to push their SQL server, as my Access app seems to be OK in my limited testing (3 users). Comments?

    Anyway it might be an idea for me to go to MS SQL or MySQL. Is there a comparison I can read as to which is best? More importantly, what does it take to convert my app to MS SQL or MySQL? I know I need to play with the connection string, but what's required to convert the Access database tables? What other things need doing?

    Sorry these questions are so basic but I'm just trying to make sure I restart on the correct foot! Assume I know nothing, which is pretty close. Any links to good info sites appreciated.

    Thanks for any help!
    Graeme
    </blockquote id="quote"></font id="quote">
     
    Bruce, Sep 13, 2003
    #3
  4. tunnel

    tunnel

    Thanks dasp and bruce.

    I just needed to get over the initial hurdle of how to proceed. Seems a lot clearer now on how to go about upsizing ... in fact have made some progress with Access upsizing wizard. Easier than I thought (so far!). Thought MS SQL Server might be easier upsize path to MySQL hence sticking with MS.

    Still changing my app, the proof will be when I test run 'new' app soon.

    Thanks for any help!
    Graeme
     
    tunnel, Sep 15, 2003
    #4
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page