Post reply

Switching to another web host

  • September 29, 2003 at 4:21 am

    #82273

    Our website has a large database of around 100,000 registered users.

    The problem now is we are changing our web host, so how can I ensure that the

    database is exactly replicated @ the new host without loosing any data.

    How can the switching between the 2 hosts happen transparent to our web users with no data loss?

  • September 29, 2003 at 5:06 am

    #476162

    What is your definition of "registered users"? Is this just 100,000 rows in a table?

    What security model are you currently using to access the database.

    You could be able to just backup your current database and restore it to the new host. Other options are, detaching the database copying the file across to the new host and re-attaching. You could also create another database on the new hosts server and replicate your existing database to it.

    It depends on how your database/server is currently setup. How is the new hosts server setup? What is the connectivity between the hosts?

    Hope this helps

    Phill Carter

    --------------------

    Colt 45 - the original point and click interface

    Edited by - phillcart on 09/29/2003 05:12:05 AM

    --------------------
    Colt 45 - the original point and click interface

  • September 29, 2003 at 5:22 am

    #476165

    If by "registered users" you mean you have created a SQL Server login and user account for each (and, if this is the case, I suggest rethinking that strategy), check out this article:

    http://support.microsoft.com/default.aspx?kbid=246133

    --Jonathan



    --Jonathan

  • September 29, 2003 at 5:42 am

    #476172

    By Registered users I mean web users not Server logins or user accounts. I mean that the database has many tables of 100,000 each.

    Detaching & attaching the database would be a good idea, but how can ensure that no data is lost between those two operations ?

    The 2 hosts have an internet connection between them.

    Here's how I can Imagine it:

    The database is deattached & attached & the new host & then replication runs to ensure data @ both sides & then the website points @ the new host. Is this possible? I am a bit new to replication, can you send me any article that would help ?

    Thanx a lot

  • September 29, 2003 at 6:17 am

    #476182

    Bear in mind that you need to run replication after your current host is off-line. Otherwise, additions or changes will not be done in the new database.

    Does your system needs to be up 24/7? If not, I suggest you do what you described without any host active.

    If it needs to be up 24/7, you can run replication and test the new host. If everything seems OK, you can make the switch to the new host and run replication again.

  • September 29, 2003 at 5:29 pm

    #476282

    If you have a downtime window. Detach and Attach will be the quickest method. You won't need to wait for database backup & restores.

    You won't need to worry about the transaction log, or missing data. You won't be able to detach the database while there are active transactions. Also, the database won't be available for further updates while you have it detached.

    Hope this helps

    Phill Carter

    --------------------

    Colt 45 - the original point and click interface

    Edited by - phillcart on 09/29/2003 5:32:48 PM

    --------------------
    Colt 45 - the original point and click interface

  • September 30, 2003 at 3:54 am

    #476333

    Please stick to one Thread or atleast point out that you are posting this more then once 😉

  • September 30, 2003 at 6:48 am

    #476354

    I'd agree with Phill. Put your web site into maintenance mode during a slow traffic time and detach and attach.

Viewing 8 posts - 1 through 7 (of 7 total)

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