Search

Error in master.sys.sp_expired_subscription_cleanup by Wilfried Weber

Closed
as Won't Fix Help for as Won't Fix

1
0
Sign in
to vote
Type: Bug
ID: 774533
Opened: 12/17/2012 2:25:02 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
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."
Details (expand)

Product Language

German

Version

SQL Server 2012 - Enterprise Edition

Category

Replication

Operating System

Windows Server 2008 R2 Datacenter (SP1)

Operating System Language

German

Steps to Reproduce

- Create database with name "A.B"
- Publish the database using Merge-Replication
- Let the subscription expire
- Call procedure master.sys.sp_expired_subscription_cleanup

Actual Results

Error-message "Msg 7202, Level 11, State 2, Procedure sp_expired_subscription_cleanup, Line 70
Server 'IFCC' 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."

Expected Results

No error-message, the expired subscription should be cleaned up.

Platform

X64

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
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
Sign in to post a workaround.