remove a push subscription from subscriber server

Hi all,
How do you remove a push subscription from subscriber server?
This is our Server and we get are data pushed every 15 minutes from a remote
server that
is not managed by us.
Once in a while they need to do a complete push of all the data and need the
subscription
removed. How? Since it is our server and our replicated data, how can I
remove it?
You cannot right click and delete.
thanks,
gv
You need to change the account that they are using to push the subscription.
Query
select distribution_agent from MSreplication_subscriptions to get the name
of the agent. Then run profiler filtering so that only this application name
comes through. Note the login and then change the password on it locally or
remove it from the database users or server roles.
http://www.zetainteractive.com - Shift Happens!
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
"gv" <gerry.viator@.accesspointinc.com> wrote in message
news:e5628BcQIHA.4128@.TK2MSFTNGP06.phx.gbl...
> Hi all,
> How do you remove a push subscription from subscriber server?
> This is our Server and we get are data pushed every 15 minutes from a
> remote server that
> is not managed by us.
> Once in a while they need to do a complete push of all the data and need
> the subscription
> removed. How? Since it is our server and our replicated data, how can I
> remove it?
> You cannot right click and delete.
> thanks,
> gv
>

Remote Distributor question

sql2k sp3
BoxA Publisher.
BoxB Subscriber. To be used for reporting.
I want the processing drain of Replication to be done on
BoxB. So I was thinking of putting the Distributor on BoxB
and using a Push Subscription.
Do any of you gurus see any problems with my idea?
TIA, Chris?
Reporting services chews up a lot of cycles. You might find it better to
keep the distributor on the publisher.
The point you start to move the distributor off the publisher is when you
start to get significant locking on your distribution database.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:0a4701c46e74$e3ab90f0$a601280a@.phx.gbl...
> sql2k sp3
> BoxA Publisher.
> BoxB Subscriber. To be used for reporting.
> I want the processing drain of Replication to be done on
> BoxB. So I was thinking of putting the Distributor on BoxB
> and using a Push Subscription.
> Do any of you gurus see any problems with my idea?
> TIA, Chris?
|||>Reporting services chews up a lot of cycles.
My bad. I wont be using actual Reporting Services.
You might find it better to
>keep the distributor on the publisher.
>The point you start to move the distributor off the
publisher is when you
>start to get significant locking on your distribution
database.
>
Why is this? Why do people do it then?

>--Original Message--
>Reporting services chews up a lot of cycles. You might
find it better to
>keep the distributor on the publisher.
>The point you start to move the distributor off the
publisher is when you
>start to get significant locking on your distribution
database.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"ChrisR" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:0a4701c46e74$e3ab90f0$a601280a@.phx.gbl...
BoxB
>
>.
>
|||Well, most people do it to reduce the load on the Publisher. The question is
when should you do it, and there is no real rule of thumb, at least as far
as I am aware.
The deciding factor for me is when you experience locking in your
distribution database.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:0c4201c46e8a$e7dd03a0$a601280a@.phx.gbl...[vbcol=seagreen]
> My bad. I wont be using actual Reporting Services.
> You might find it better to
> publisher is when you
> database.
> Why is this? Why do people do it then?
> find it better to
> publisher is when you
> database.
> message
> BoxB

Remote Distributor and Subscriber on same machine - is that OK?

Hi,

Server A houses the Production DB which services an OLTP system. Transactional replication is configured on this server which has two subscribers - on two separate servers (servers B and C). The Distribution database currently resides on Server A (which is also the Publisher).

Server B is on the same LAN as Server A (on the same rack). I'm considering moving the Distribution database from Server A to Server B to offload some of the processing overhead from Server A.

Are there any gotchas/performance problems associated with having the Distribution database (remote distributor) and the Subscriber on the same server (server B) in a transaction replication topology?

Please advise or point me to the appropriate documentation - I haven't found anything that addresses this specific question...thanks in advance,

Smitha

This is actually a rather popular configuration (at least the ones that I have seen) inside Microsoft as this allows you to upgrade the Distributor and Subscriber to a new release together and then use the Subscriber as a test bed for the new release while receiving continuous updates from the production system. You do need good network connectivity between the publisher and the distributor\subscriber as pulling snapshot data (or backup\restore for that matter) can easily saturate a 100Mbit Ethernet connection. So to minimize impact on the production system, you may want to get a dedicated connection between the two.

-Raymond

|||

Thanks Raymond. I shouldn't have to worry about the snapshot/backup+restore because I've used this second server as the backup files' location in the past (and still perform copy-only FULL production DB backups to this server). The restore takes a while since it reads from and writes to the same drive but this is OK for an operation that may happen 2-3 times a year.

Thanks again,

Smitha