Replication or another solution??? Newbie!

  • Hi,

    I have a local SQL Server database.  We use a provider to host our website.  They support SQL Server.  I am using SQL Server Developer Edition.  I would like to upload part of our local database to the www and allow users to enter data on the www and then I want to be able to synch the data with the main local database.  I have the following questions:

    • How do I upload the database?  Our provider has given me the servername, database name, login and password.
    • How do I keep the 2 databases in synch (the remote and local)?  Replication or....?
    • If I should (and can) use replication, which one would I use--snapshot, transactional or merge?

    I would appreciate any help any of you could provide...general 'rules of thumb' when setting something like this up, etc.  Thanks!

     

     

  • (A) Upload the Database any way you like.

    (B) Set up Transactional Replication between the 2 Databases.


    Kindest Regards,

  • MrSQL,

    Thank you for your response! 

    • What would be the reasoning in using Transactional Replication over Merge Replication? 

    My application will have the users updating/entering via the web and I will be changing updating the main local database, which will require me to synchronize them.  I would like to synch the databases a couple/few times per week.  Ex: after a deadline for the users to enter/update info, after I make updates to tables and wish them to viewed on web, etc. 

    • From what I understand, I should be able to set this up to synch on a schedule and then (?) even manually run a synch if I want...?

    Thanks again for your input!

     

  • Ok. Then Merge Replication would be a better option if the users are disconnected from the network at any length of time. However, if the users are always connected to the network, then Transactional Replication will do!


    Kindest Regards,

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply