Results 1 to 6 of 6

Thread: Newbie SQL Server question

  1. #1

    Thread Starter
    Addicted Member
    Join Date
    Aug 2002
    Posts
    187

    Newbie SQL Server question

    Hi all,

    I am about to convert a VB app using Access to SQL server.
    The app uses a split db ie. a client side db and a server side db.

    My question relates the the client side db. If this is converted to SQL server db, the client machine should have the required files to run the client db right ?

    Obviously the server side will work as SQL server is installed on the server.

    If someone can confirm that I will have no probs on the client side or if I will need to install some runtimes it would be much appreciated.

    Just starting to learn SQL server so just want to make sure before I start.

    Cheers

    Jack

  2. #2
    PowerPoster
    Join Date
    Oct 2002
    Location
    British Columbia
    Posts
    9,758
    SQL Server is much more powerful than Access, so depending on your needs, there may be no reason for a Client side DB.

    How do you use the Client side DB? What data does it store?

    Microsoft offers the MSDE, free if you have the correct licenses, that can be used as a client side db.

  3. #3

    Thread Starter
    Addicted Member
    Join Date
    Aug 2002
    Posts
    187
    The client side holds some blank tables used to store temporary data and perform some number crunching before sending the results to the server db for storage.

    As there is quite a lot of data entry, I thought it much more efficient to use this type of architecture. There server db does not need to hold the data entry, just the results of crunching the data.

    Cheers

    Jack

  4. #4
    Hyperactive Member
    Join Date
    Aug 2002
    Location
    Norwich, UK
    Posts
    405
    the company i work for is actively trying to move away from this type of architecture, where you have maybe an access db holding company product info and then the relevent stuff gets synced to a sql server db. in my experience having various disparated data sources is not a good thing.

  5. #5
    Katuil
    Guest
    Here's a thought...

    Create your temp tables in SQL Server. Make them user dependent. In other words, add a field that has the user name. Then when your done commit the data and clean up the temp table based on the user name. This will keep everything on the server.

  6. #6

    Thread Starter
    Addicted Member
    Join Date
    Aug 2002
    Posts
    187
    Thanks for all the suggestions...I am looking at replication as an option at the moment.

    This will enable to draw down a copy of the "client db" do the crunching and upload into the "server db".

    Cheers

    Jack

Posting Permissions

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



Click Here to Expand Forum to Full Width