this is a tricky thing to do.
the way it works is SQL Server queries the distribution history and if it is
beyond the retention period then one of the clean up procs will mark the
subscription as "expired"
To test, update your distribution history to an old date, and then run the
expired subscription clean up agent.
here is a sample
update msdistribution_history set start_time=dateadd(dd,-20,start_time),
time=dateadd(dd, -20,time) where agent_id=12
I am picking 20 days as a date which is beyond my retention period which has
a default of 14 days (334 hours). Agent_id is the particular agent_id for
the distribution agent going to the subscription you are trying to expire.
Naturally I hope and pray you are doing this in a development environment.
Another option is to set the retention period to 1 hour and wait 1hour. Do
this by right clicking on your publication selecting properties and set the
retention period to 1.
Then come back in an hour and run the expired subscription clean up agent.
[quoted text, click to view] "nate axtell" <naxtell at progeny dot net> wrote in message
news:ufX8g5gXEHA.3396@TK2MSFTNGP10.phx.gbl...
> Does anyone know how to manually set a Subscription to be Expired? I'm
not
> looking for a hack, but if that is all you have I will try it. I was
hoping
> that there might be a system stored procedure that would do it, although I
> know that is pretty doubtful. The reason for this is because now I have
to
> wait for the minimum setting of 1 day to occur before I can test how I
need
> to reinitialize the subscription. I would like to do this at will.
> Thanks for any suggestions,
> Nate
>
>