How to remove a push subscription?

I have a publication within a transactional replication with a push
subscription. I had deleted the subscription on the Publisher through the EM.
And Publisher EM showed the subscription is removed. But when I checked the
Subscriber EM, the subscription is still there under the
Replication\Subscriptions, and it seems there is no way to remove it on
Subscriber EM. Can someone please help me on this? How do I remove it on the
subscriber?
Thanks,
Hi,
to dtop a pull subscription you can use:
sp_droppullsubscription system stored procedures.
hope it works fine with you.
SaeedA
"FYK" wrote:

> I have a publication within a transactional replication with a push
> subscription. I had deleted the subscription on the Publisher through the EM.
> And Publisher EM showed the subscription is removed. But when I checked the
> Subscriber EM, the subscription is still there under the
> Replication\Subscriptions, and it seems there is no way to remove it on
> Subscriber EM. Can someone please help me on this? How do I remove it on the
> subscriber?
> Thanks,
|||Hi,
You can use :
sp_dropsubscription, you can see BOL for more details
SaeedA
"FYK" wrote:

> I have a publication within a transactional replication with a push
> subscription. I had deleted the subscription on the Publisher through the EM.
> And Publisher EM showed the subscription is removed. But when I checked the
> Subscriber EM, the subscription is still there under the
> Replication\Subscriptions, and it seems there is no way to remove it on
> Subscriber EM. Can someone please help me on this? How do I remove it on the
> subscriber?
> Thanks,

How to Reintialize A Single Article!

Hello All,
I'm using Transactional Replication and it's Push subscription.
I want to Reintialize 1 article, i did this,
exec sp_reinitsubscription
@.publication = 'inventory',
@.article = 'customer',
@.for_schema_change = 1,
@.subscriber = 'subscriber'
but error
"Cannot reinitialize article 'customer' in subscription
'Subscriber:Inventory' to publication 'inventory' (subscribed with the 'no
sync' option)."
How can I Reintialize A Single Article?
Thanks in advance!!!
Naveed.
you can't. You are best to drop the article from the publication, and create
another publication with this article in it by itself.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Naveed" <nrehman@.marsonssoft.com> wrote in message
news:ud8A0l5qEHA.2724@.TK2MSFTNGP14.phx.gbl...
> Hello All,
> I'm using Transactional Replication and it's Push subscription.
> I want to Reintialize 1 article, i did this,
> exec sp_reinitsubscription
> @.publication = 'inventory',
> @.article = 'customer',
> @.for_schema_change = 1,
> @.subscriber = 'subscriber'
> but error
> "Cannot reinitialize article 'customer' in subscription
> 'Subscriber:Inventory' to publication 'inventory' (subscribed with the
'no
> sync' option)."
> How can I Reintialize A Single Article?
> Thanks in advance!!!
> Naveed.
>
|||In article <#3hYFP6qEHA.2796
@.TK2MSFTNGP10.phx.gbl>, hilary.cotter@.gmail.com
says...
> you can't. You are best to drop the article from the publication, and create
> another publication with this article in it by itself.
>
can you drop just an article from a publication
or do you have to drop the whole publication
itself? I have run into this situation before
where I had 5 pretty large articles in 1
publication and needed to drop just 1 of those
articles. I couldn't just do that. I had to
drop the whole pub.
-comb

How to reinitialize a table in transactional publication.

I have set-up replication using transactional publication and I have
configured subscription to be near continuous.
I have this issue. When setting up subscription I have specified that the
subscription database already had data. So when the snapshot agent is
initialized it does not recreate the tables on the subscription database.
This is ok. But, now if I was to re-initialize only one of the tables, how
do I achieve this without breaking replication.
-Nags
You can't really do this.
If you start with a no-sync, you can't re-initialize. Only subscriptions
that were set for automatic synchronization can be re-initialized.
What I do in situations like this is to drop the article, and then recreate
it in a new publication.
"Nags" <nags@.DontSpamMe.com> wrote in message
news:eQMRViYIEHA.828@.TK2MSFTNGP10.phx.gbl...
> I have set-up replication using transactional publication and I have
> configured subscription to be near continuous.
> I have this issue. When setting up subscription I have specified that the
> subscription database already had data. So when the snapshot agent is
> initialized it does not recreate the tables on the subscription database.
> This is ok. But, now if I was to re-initialize only one of the tables,
how
> do I achieve this without breaking replication.
> -Nags
>
|||Can we drop an article once the tables are published and also subscribed ?
I thought that once there is a subscription on a publication (at least in
transactional publication) we cannot drop the article.
-Nags
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:OIi$glcIEHA.3528@.TK2MSFTNGP09.phx.gbl...
> You can't really do this.
> If you start with a no-sync, you can't re-initialize. Only subscriptions
> that were set for automatic synchronization can be re-initialized.
> What I do in situations like this is to drop the article, and then
recreate[vbcol=seagreen]
> it in a new publication.
>
> "Nags" <nags@.DontSpamMe.com> wrote in message
> news:eQMRViYIEHA.828@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
database.
> how
>
|||You will have to drop the subscription for both automatic and nosync
subscriptions, then you can drop the article.
"Nags" <nags@.DontSpamMe.com> wrote in message
news:uSGXCLhIEHA.3440@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Can we drop an article once the tables are published and also subscribed ?
> I thought that once there is a subscription on a publication (at least in
> transactional publication) we cannot drop the article.
> -Nags
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:OIi$glcIEHA.3528@.TK2MSFTNGP09.phx.gbl...
> recreate
> the
> database.
tables,
>
|||But, I do not want to break replication
-Nags
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:eg$wjYkIEHA.3536@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> You will have to drop the subscription for both automatic and nosync
> subscriptions, then you can drop the article.
> "Nags" <nags@.DontSpamMe.com> wrote in message
> news:uSGXCLhIEHA.3440@.TK2MSFTNGP09.phx.gbl...
?[vbcol=seagreen]
in[vbcol=seagreen]
subscriptions[vbcol=seagreen]
that[vbcol=seagreen]
is
> tables,
>
|||Nags wrote:
> I have set-up replication using transactional publication and I have
> configured subscription to be near continuous.
> I have this issue. When setting up subscription I have specified that the
> subscription database already had data. So when the snapshot agent is
> initialized it does not recreate the tables on the subscription database.
> This is ok. But, now if I was to re-initialize only one of the tables, how
> do I achieve this without breaking replication.
> -Nags
>
You are not very well..
However, there are several tricks you can try:
a) you can afford having no transaction on the source table for a
certain time
=> put a trigger for insert / update / delete on the table which
always raise error and rollback
=> wait the log reader agent and the distribution agent have purged
any pending transaction on this table
=> bulk copy your table from publisher to subscriber
=> remove the trigger
b) you can also create a new publication on the table ( I never tried to
publish twice a table on the same database, but you can always create a
"mirror" table on the publishing database that you keep in sync with
triggers )
On the subscriber, subscribe to this new publication and wait for
synchronisation
Now, here is the trick:
On the publisher you have articles A and A2 which you know are in sync
On the subscriber you have tables Arep and A2rep and you know that A2rep
is in sync
So, stop the log reader agent.
Wait long enough so that the distributing agents tell "no more transactions"
Copy A2rep into Arep
restart log reader agent.
Now Arep is sync'ed and you can drop all the A2 stuff.
If you are not familiar with these operations, you might make a
rehearsal on a test server before trying your production server!

how to reinitialize a subscription with TSQL ??

how to reinitialize a subscription with TSQL ??Hassan,
have a look at these in BOL:
sp_reinitsubscription
sp_reinitpullsubscription
sp_reinitmergesubscription
sp_reinitmergepullsubscription
Rgds,
Paul Ibison
sql

How to reference a shared datasource already on report server for data driven subscription

I see there's MS documentaion on creating a data driven subscription.
The example shows to create a data source for the data retrieval plan.
see
http://msdn2.microsoft.com/en-us/library/microsoft.wssux.reportingserviceswebservice.rsmanagementservice2005.reportingservice2005.createdatadrivensubscription.aspx
I would like to set the data source to a share data source on the
server. How should I implement that?
I have tried to use the following but failed:
...
delivery.Item = rs.GetDataSourceContents("/Data Sources/
testDataSource");
...I have worked this out: By creating a DataSourceReference object:
DataSourceReference reference = new
DataSourceReference();
reference.Reference = "/Data Sources/testDataSource";
delivery.Item = reference;
But then I got error like:
The current action cannot be completed because the user data source
credentials that are required to execute this report are not stored in
the report server database.
My credential information is stored with data source. If I manually
create the data-driven subscription from Report Manager, and use the
same shared data source, I wouldn't get this error. Anyone knows why?
Thanks