noneil
asked on
SQL 2005 database mirroring connection string
I have been doing a bit of research trying to find out how a connection string works for a SQL 2005 instance which is setup with database mirroring.
i am very familiar with microsoft clustering and there being a VIP.
in database mirroring there appears to be no VIP.
i have 3 nodes, a primary a mirror and a witness.
using microsoft sharepoint how would i modify the string and where to connect to a database mirror?
my guess is the web.config file but i cannot find a location.
any suggestions are much appreciated since i have not seen this question answered before it may be very usefull for future references, thanks team!
i am very familiar with microsoft clustering and there being a VIP.
in database mirroring there appears to be no VIP.
i have 3 nodes, a primary a mirror and a witness.
using microsoft sharepoint how would i modify the string and where to connect to a database mirror?
my guess is the web.config file but i cannot find a location.
any suggestions are much appreciated since i have not seen this question answered before it may be very usefull for future references, thanks team!
also:
Connecting Clients to a Mirrored Database
http://msdn2.microsoft.com/en-us/library/ms175484.aspx
Connecting Clients to a Mirrored Database
http://msdn2.microsoft.com/en-us/library/ms175484.aspx
what is your sharepoint version?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thank you very much for pointing me into the right direction.
right now i am using sharepoint services + sp2, the free version available for download from microsoft.com/sharepoint.
i was not sure which web.config file i should be modifying but i will be giving this a shot and reading through all of these articles now.
when i search the hard drive numerous web.config files show up. in order to assume which may be the correct file what i have done is gone to IIS, right click the default site with sharepoint installed, go to ASP.net properties and look at the path pointing to the web.config file. oddly enough though that file is much smaller in size then some of the other web.config files located in various other folders on the drive.
right now i am using sharepoint services + sp2, the free version available for download from microsoft.com/sharepoint.
i was not sure which web.config file i should be modifying but i will be giving this a shot and reading through all of these articles now.
when i search the hard drive numerous web.config files show up. in order to assume which may be the correct file what i have done is gone to IIS, right click the default site with sharepoint installed, go to ASP.net properties and look at the path pointing to the web.config file. oddly enough though that file is much smaller in size then some of the other web.config files located in various other folders on the drive.
In SQL Server 2005, if you connect to a database that is being mirrored with ADO.NET or the SQL Native Client, your application can take advantage of the drivers' ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string, and optionally the failover partner server.
There are many ways to write the connection string, but here is one example, specifying server A as the principal, server B as the mirror, and AdventureWorks as the database name:
"Data Source=A;Failover Partner=B;Initial Catalog=AdventureWorks;Int
The failover partner in the connection string is used as an alternate server name if the connection to the initial principal server fails. If the connection to the initial principal server succeeds, then the failover partner name will not be used, but the driver will store the failover partner name that it retrieves from the principal server on the client-side cache.
Assume a client is successfully connected to the principal, and a database mirroring failover (automatic, manual, or forced) occurs. The next time the application attempts to use the connection, the ADO.NET or SQL Native Client driver will detect that the connection to the old principal has failed, and will automatically retry connecting to the new principal as specified in the failover partner name. If successful, and there is a new mirror server specified for the database mirroring session by the new principal, the driver will retrieve the new partner failover server name and place it in its client cache. If the client cannot connect to the alternate server, the driver will try each server alternately until the login timeout period is reached.