January 8, 2008 at 5:42 am
We have a two node cluster setup of SQL Server 2005 sp2. Within this set up, a new instance was recently created. It is suspected that when the instance was built, the physical name of the 'real' server was typed instead of the logical name that can fail between the two servers.
This manifests itself as a problem when trying to say set up transaction log shipping on the new databases that have been defined as the @server_name value does not exist.
What is being shown is are in house standard values.
The Master view SYS.Servers shows in the Name and Data_Source column this wrong value.
Assuming this is the root problem, how can we correct the value in SYS.Servers for these to columns? Standard Update on the view won't work as being a system table it doesn't like 'backdoor' changes.
January 8, 2008 at 8:21 am
Resolved.
Needed to correct the linked servers via SP_DropServer and SP_AddServer remembeing the local option.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply