Error in master.sys.sp_expired_subscription_cleanup - by Wilfried Weber

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 774533 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/17/2012 2:25:02 AM
Access Restriction Public

Description

After a subscription to a database whose name contains a point (e.g. "A.B") is expired, a call to master.sys.sp_expired_subscription_cleanup ends in the error "Server 'A' konnte in 'sys.servers' nicht gefunden werden. Stellen Sie sicher, dass der richtige Servername angegeben wurde. Führen Sie ggf. die gespeicherte Prozedur 'sp_addlinkedserver' aus, um den Server in 'sys.servers' hinzuzufügen."
Sign in to post a comment.
Posted by Millstone1998 on 7/11/2013 at 2:57 AM
I'm disappointed to see this was closed as "Won't Fix". Databases are often suffixed with a version number (eg in the error below if the project was called Rabbit and the version is 2.0 so the database is named Rabbit2.0 - not my preferred naming convention but an inherited one that is relatively common) . I'm adding the English error message here to help people searching for this issue.

Could not find server 'Rabbit2' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.

I think the fix may just be to add QUOTENAME around the @publisher_db.
Kind Regards, CarrieAnne
Posted by Microsoft on 1/14/2013 at 10:56 AM
Hi Wilfried Weber,

given my previous message, I'm archiving this work item for now.

Best regards
Jean-Yves Devant 
Program Manager Servicing and Lifecycle Experience of High Availability Technologies in SQL Server
Posted by Microsoft on 1/4/2013 at 4:49 PM
Hi Wilfried Weber,

thanks for taking the time to share your feedback, this is really important to us.
Unfortunately this does not meet the bar. We do not plan to address this for now. We will revisit the decision if more customers vote for the issue. In the meantime we recommend you do not use a . in the name of a database.

Best regards
Jean-Yves Devant 
Program Manager Servicing and Lifecycle Experience of High Availability Technologies in SQL Server
Posted by Microsoft on 1/4/2013 at 4:35 PM
Hi Wilfried Weber,
    
thanks for taking the time to share your feedback, this is really important to us.
We will investigate the issue and get back to you.

Best regards
Jean-Yves Devant 
Program Manager Servicing and Lifecycle Experience of High Availability Technologies in SQL Server