September 6, 2007 at 6:37 am
Greetings,
I have 3 servers all running SQL Server 2005. On each I created a secondary named instance to setup Database Mirroring, with the intent of having a primary, backup and witness server. I've got the database in place to mirror, but am now stuck. The problem is that I am unable to see the new server instances on the network. I have gone through all three and checked that network protocols are active,remote connections are turned on, RPC is active, each server has the same Windows account as a sql login. Is there something else I'm forgetting here?
My server setup: (each of the servers also has a default MSSQLSERVER instance running)
Artemis\Parks - primary database server (Windows Server 2003 Standard SP1, Dell PowerEdge 2650)
Artume\Parksmirror - backup database server (Windows Server 2003 Standard SP1, Dell PowerEdge 2650)
Performance\Witness - witness server for the mirroring process (Windows Server 2003 Standard SP1, Dell PowerEdge 2650, VMWare ESX Server, this is one of 3 virtual servers on it)
September 6, 2007 at 6:50 am
Is SQL Server Browser Service running?
Andras
September 6, 2007 at 6:54 am
No, it is not running on any of them. I didn't realize that needed to be on for Secondary instances to be visible.
September 6, 2007 at 7:06 am
Among others this keeps track of the SQL Server instances installed, and their port numbers. So unless you are running the named instances on fixed ports, this service helps to identify the right port for the particular SQL Server instance. It is not needed if you have only the default instance, with its default fixed port. But, also this service is used to enumerate the instances on a machine.
Regards,
Andras
September 6, 2007 at 10:30 am
Sure enough, enabling the browser did it. Thanks for the insight!
Taylor
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply