Publisher unexpectedly drops merge pull subscription

Greetings.
I have several machines that have two merge pull subscriptions for two
databases. One subscription is set to continuous, the other
subscription is set to pull every hour. The publications are set to
drop subscribers if they don't synchronize within 14 days.
This has been in production for one week (we're well under the 14 day
threshold). The continuous subscription is working properly for
everybody. Today, after being off-line for a period of time, one of
the subscribers attempted to merge its hourly subscription, but the
publisher had dropped the subscription from the server and I ended up
with no subscription at the publisher and the following error on the
subscriber:
"The subscription to publication 'Obfuscated' has expired or does not
exist. The step failed."
We have provided a UI through which the user of the subscribing machine
can re-initialize the offending subscription so, we have a work-around.
Hopefully, we can find the cause.
Does any thoughts on why the publication would drop the subscription?
The only entry I can find in this group that seems to match this
straight up was in 1999 regarding a known issue SQL server 7 pre-SP1:
http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/1ffdc41526b24f82/e9b07619ecf86b2e?
Thanks,
KenJ
Make sure your history retention is the same as your retention period
otherwise your subscription will expire when the lesser of the history
retention or publication retention is exceeded.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"KenJ" <kenjohnson@.hotmail.com> wrote in message
news:1163198676.820694.304180@.e3g2000cwe.googlegro ups.com...
> Greetings.
> I have several machines that have two merge pull subscriptions for two
> databases. One subscription is set to continuous, the other
> subscription is set to pull every hour. The publications are set to
> drop subscribers if they don't synchronize within 14 days.
> This has been in production for one week (we're well under the 14 day
> threshold). The continuous subscription is working properly for
> everybody. Today, after being off-line for a period of time, one of
> the subscribers attempted to merge its hourly subscription, but the
> publisher had dropped the subscription from the server and I ended up
> with no subscription at the publisher and the following error on the
> subscriber:
> "The subscription to publication 'Obfuscated' has expired or does not
> exist. The step failed."
> We have provided a UI through which the user of the subscribing machine
> can re-initialize the offending subscription so, we have a work-around.
> Hopefully, we can find the cause.
> Does any thoughts on why the publication would drop the subscription?
> The only entry I can find in this group that seems to match this
> straight up was in 1999 regarding a known issue SQL server 7 pre-SP1:
> http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/1ffdc41526b24f82/e9b07619ecf86b2e?
>
> Thanks,
> KenJ
>
|||Thanks, Hilary.
We haven't seen one drop off since we made this change. It's a rather
interesting combination of settings.
KenJ
Hilary Cotter wrote:[vbcol=seagreen]
> Make sure your history retention is the same as your retention period
> otherwise your subscription will expire when the lesser of the history
> retention or publication retention is exceeded.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "KenJ" <kenjohnson@.hotmail.com> wrote in message
> news:1163198676.820694.304180@.e3g2000cwe.googlegro ups.com...

Published wish list?

Greetings,
Is there a published wish-list or a prioritised "future features" list for
Reporting Services?
Such a list would help me avoid asking if a non-existent feature has been
implemented and (maybe) give me some idea of when a particular desirable
feature may become available...
--
Regards,
Neale NOONSorry, we don't publish the wishlist. (Even if we did, it wouldn't include
current plans/priorities since those are subject to change).
--
This post is provided 'AS IS' with no warranties, and confers no rights. All
rights reserved. Some assembly required. Batteries not included. Your
mileage may vary. Objects in mirror may be closer than they appear. No user
serviceable parts inside. Opening cover voids warranty. Keep out of reach of
children under 3.
"noonie" <noonie1155@.hotmail.com> wrote in message
news:Osahq$JdEHA.1424@.tk2msftngp13.phx.gbl...
> Greetings,
> Is there a published wish-list or a prioritised "future features" list for
> Reporting Services?
> Such a list would help me avoid asking if a non-existent feature has been
> implemented and (maybe) give me some idea of when a particular desirable
> feature may become available...
> --
> Regards,
> Neale NOON
>|||Thanks Chris,
"Chris Hays [MSFT]" <chays@.online.microsoft.com> wrote in message
news:O2PeLbMdEHA.4048@.TK2MSFTNGP12.phx.gbl...
> Sorry, we don't publish the wishlist. (Even if we did, it wouldn't
include
> current plans/priorities since those are subject to change).
Then is this the appropriate forum to "make a wish"?
1. Support for more CSS properties in RDL (background-attachment for
background images would be helpful)
2. More reliable column name discovery in the dataset designer when using
stored procedures (I want to reuse some stored procedures designed for
another application but they potentially return more than one data set and
the designer only identifies the column names of the first potential table
even after running the query with the correct parameters to select the right
data for the second potential table)
3. More rendering choices in the export report function. (RTF is high on my
list)
> "noonie" <noonie1155@.hotmail.com> wrote in message
> news:Osahq$JdEHA.1424@.tk2msftngp13.phx.gbl...
> > Greetings,
> >
> > Is there a published wish-list or a prioritised "future features" list
for
> > Reporting Services?
> >
> > Such a list would help me avoid asking if a non-existent feature has
been
> > implemented and (maybe) give me some idea of when a particular desirable
> > feature may become available...
--
Regards,
Neale NOON|||Anytime you'd like to see something added to SQL Server, send email to
sqlwish@.microsoft.com. Those emails go directly into the mailboxes of the
folks making the decisions and are also logged into an internal database so
we can track them. You probably won't get a personal response, just an
automatic one, but these really are listened to and acted upon. Trust me.
:-)
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"noonie" <noonie1155@.hotmail.com> wrote in message
news:uKLIJfOdEHA.2352@.TK2MSFTNGP09.phx.gbl...
> Thanks Chris,
> "Chris Hays [MSFT]" <chays@.online.microsoft.com> wrote in message
> news:O2PeLbMdEHA.4048@.TK2MSFTNGP12.phx.gbl...
>> Sorry, we don't publish the wishlist. (Even if we did, it wouldn't
> include
>> current plans/priorities since those are subject to change).
> Then is this the appropriate forum to "make a wish"?
> 1. Support for more CSS properties in RDL (background-attachment for
> background images would be helpful)
> 2. More reliable column name discovery in the dataset designer when using
> stored procedures (I want to reuse some stored procedures designed for
> another application but they potentially return more than one data set and
> the designer only identifies the column names of the first potential table
> even after running the query with the correct parameters to select the
> right
> data for the second potential table)
> 3. More rendering choices in the export report function. (RTF is high on
> my
> list)
>> "noonie" <noonie1155@.hotmail.com> wrote in message
>> news:Osahq$JdEHA.1424@.tk2msftngp13.phx.gbl...
>> > Greetings,
>> >
>> > Is there a published wish-list or a prioritised "future features" list
> for
>> > Reporting Services?
>> >
>> > Such a list would help me avoid asking if a non-existent feature has
> been
>> > implemented and (maybe) give me some idea of when a particular
>> > desirable
>> > feature may become available...
> --
> Regards,
> Neale NOON
>|||Thanks Stephen :-)
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:uftM3IadEHA.3380@.TK2MSFTNGP12.phx.gbl...
> Anytime you'd like to see something added to SQL Server, send email to
> sqlwish@.microsoft.com. Those emails go directly into the mailboxes of the
> folks making the decisions and are also logged into an internal database
so
> we can track them. You probably won't get a personal response, just an
> automatic one, but these really are listened to and acted upon. Trust me.
> :-)
> --
> Sincerely,
> Stephen Dybing
--
Regards,
Neale NOON