InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 11:34:11 GMT20http://www.sqlservercentral.com/Forums/Topic696607-54-1.aspxWrong posting my badFri, 12 Jun 2009 07:56:51 GMTSirFalcon60http://www.sqlservercentral.com/Forums/Topic696607-54-1.aspxThanks steveb, I guess we'll just have to re-write the app to support mirroring.Wed, 15 Apr 2009 02:12:21 GMTkenweed06http://www.sqlservercentral.com/Forums/Topic696607-54-1.aspxIn 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)Tue, 14 Apr 2009 09:03:19 GMTsteveb. http://www.sqlservercentral.com/Forums/Topic696607-54-1.aspxHi 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 tosql server database. It usually reads from a config file the server name and/or the ip addressof the server where the db is hosted. Based on this the only sql server 2005 failover option thatI 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 otherfailover 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.Tue, 14 Apr 2009 08:43:26 GMTkenweed06