September 15, 2006 at 12:45 pm
I'm looking into a db mirror setup but using certificates instead of windows authentication. I have setup the certificates and created end points on both servers, but am running into some problems. For instance, on the primary/principal server after the endpoint is setup I try running the following command:
Alter database dbmirror set partner='tcp://mymirror:5022'
--mymirror is the netbios name on the same workgroup of the mirror instance
The prinicpal returns the error message stating that mymirror cannot be reached, but I know it's up and I can ping it. I pretty much followed the steps in BOL.
Another question, if both prinicpal and mirror belong to the same workgroup and are not part of the domain or AD, can they utilize windows authentication somehow?
Thanks
September 16, 2006 at 2:20 pm
try to create sql server alias
check
Database Mirroring in SQL Server 2005
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
Troubleshoot Connectivity Issue in SQL Server 2005 - Part III
http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
September 18, 2006 at 2:54 pm
Thanks for the tip. Setting up an alias helped. However I have one more problem with a witness server, which is sitting on SQL 05 Standard. I think the problem is in the fact that it is a non-default instance, so you'd see it as SQLBOX\SQLINSTANCE_2
Can someone verify this?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply