Post reply

sql server 2005 failover

  • April 14, 2009 at 8:43 am

    #208322

    Hi guys,

    I have an issue here which you can probably assist me with.

    Here's the scenario, I support an application that is written in vb and connects to

    sql server database. It usually reads from a config file the server name and/or the ip address

    of the server where the db is hosted. Based on this the only sql server 2005 failover option that

    I have used is sql server clustering and it works perfectly since I have the virtual server IP address/name to specify at the config file coupled with the many other advantages of clustering.

    However not everyone can afford to buy storage facilities. So i'd like some advice on the other

    failover options as im not well conversant with mirroring and logshipping.

    Specifically i'd want to know with mirroring and logshippin how redirection takes place from the primary server to the secondary server and in my case how does it happen without having to change the servername specified in the config file of each client connecting to the server.

  • April 14, 2009 at 9:03 am

    #977310

    In database mirroring you need to specify the fail over partner in the connection string that is in the config file of the application. The code is usualy FAILOVER PARTNER =, or something similar depending on what sort of connection you are using.

    The application will then try to connect to the primary server but if i can not it will attempt to the failover partner (mirror)

  • April 15, 2009 at 2:12 am

    #977893

    Thanks steveb, I guess we'll just have to re-write the app to support mirroring.

  • June 12, 2009 at 7:56 am

    #1008658

    Wrong posting my bad

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

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