Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2002
    Posts
    4

    Question Unanswered: Transfer SQL database to another ISP

    Hi there....

    Does anyone know what is involved with transferring a SQL database from one ISP to another? Is it just a matter of redefining the name/IP of the database or does a large portion of the database need to be reprogrammed.

    We had a contractor create our database driven website and have to switch ISPs. Just trying to verify the information he gave us.

    Thanks

  2. #2
    Join Date
    Oct 2002
    Posts
    369

    Re: Transfer SQL database to another ISP

    RE:
    Hi there.... Does anyone know what is involved with transferring a SQL database from one ISP to another? Is it just a matter of redefining the name/IP of the database or does a large portion of the database need to be reprogrammed. We had a contractor create our database driven website and have to switch ISPs. Just trying to verify the information he gave us. Thanks
    What is involved with transferring a SQL database from one ISP to another may depend on one and / or more of: the application(s), the former ISP, the new ISP, the DBMS vendor / version, any special access methods you may have or require, etc., etc. [The contractor who created your database should have provided sufficient documentation to explicitly determine exactly what any such requirements would involve; unless perhaps documentation was excluded from the project (to cut costs)?]

  3. #3
    Join Date
    Nov 2002
    Posts
    14

    Re: Transfer SQL database to another ISP

    There is a general problem related to moving databases from one server to another. If you don't have database-specific users, there is nothing to worry about. But if you do, things get a little ugly. SQL Server maintains redundant information about server logins. Behind each database user stands a server login. Along with the local user information SQL Servers keeps both the login ID and login name. Although the login name is portable accross servers, the login ID is a GUID sepcific to the server. Thus when you re-create your logins on the new server, they will have IDs different from the original ones (the ones that are in duplicated in the database). Then SQL Server gets confused. To fix it (on the new server):
    1. Login as sa
    2. Enable updates on system tables
    3. Overwrite the login IDs in the local database with the values from the master database
    4. Disable updates on system tables back
    Zlatko Michailov
    Z-SQL

Posting Permissions

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