How to remove replication?

Hi, all.
I have two server(Svr01, Svr02) that are replicated each other (Merge replication).
Svr01 must be Publisher distributor.. but, by mistake Svr02 is set to distributor, publisher. (Publisher/distributor are on the same comp..)

I want to fix this..
How?

I think I have to remove replication on both side and Reset from the first.
but, I don't know how to remove replication either..

Please reply with any thougt...Use Replication menu option in EM. You can also check stored procedures that can be used to remove it manually (they are all executed in the background when you do it through GUI), but start with EM first.|||Use Replication menu option in EM. You can also check stored procedures that can be used to remove it manually (they are all executed in the background when you do it through GUI), but start with EM first.
I don't understand about EM..
Could you explain more detail..?|||EM is SQL Enterprise Manager.

-PatP

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 reflect schema changes at subscriber using transactional replication

Hi

I need to setup transactional replication for a production server.

The tables (articles) at publisher being replicated can expect schema changes.

Is there any way to reflect schema changes at subscriber using transactional replication.

Early Thanks,

Salman Shehbaz.

If this is SQL Server 2005, the schema changes at publisher can be automatically replicated to subscriber.

If this is SQL Server 2000, you should make schema changes through proc sp_repladdcolumn or sp_repldropcolumn when adding or dropping columns. Other schema changes can not be replicated in SQL Server 2000.

How to Reduce or Delete the Log file... Log file size creating problem

I am using Replication with two of my SQL Server Databases , One Db is Publisher and other one is Subscriber , and data is continously replicating after every 5 mins . Now Publisher Database Log File increased upto 2541 MB and its creating problem while having any transaction or having any operation with DB . It also turned Replication utility Off.

I tried to delete log file by turning SQL Server off , but it makes DB mode SUSPECT and UNACCESSBLE.

Plz help me out to delete or reduce the log file size by maintaining the state of data.

Also let me know wht is the method so that log file can automatically delete its contents when reach to certain limit.

Regards
Imran MalikWhy are risking by deleting the SQL system files.

Use DBCC SHRINKFILE to reduce the Tlog file size, refer to books online for more information.|||You haven't mentioned about the version of SQL used.

If its version 7 then enable 'trunc.log at chkpt.' on the database.
If its version 2K then use SIMPLE RECOVERY model.

For more information again refer BOL.:)|||By changing to the simple recovery model, your only backup mechanism is the full or differential backup, you can no longer perform transaction log backups. If you need to shrink the file, however, and maintain the ability to perform transaction log backups, there is a Stored Procedure I found at SQLServerCentral.com. It's called sp_force_shrink_log and I find it quite useful. You can find it at http://www.sqlservercentral.com/scripts/contributions/26.asp after you register with them.|||Thank You very much Satya and loach for telling me the way to reduce the size , I am using SQL Server 2K .

DBCC SHRINKFILE and sp_force_shrink_log are helpful for reducing file size but for log deletion wht I have done is just deattach the database , remove log file and and attach db again , it refreshed and made DB log again with 1 MB. (I tested this with dummy Dbs.)

and my Databases are also connected through replication utility , so it restricts me to deattach db using in replication , so I have to turned replication off to deattach and attach db . currently I am looking into procedure or way so that without disabling replication make log refresh coz it will take long process to disable and then again follow through steps for having last settings to turn replication ON between 2 databases.

Thanks u All

Regards
Imran|||How about the backups schedule interval for LOG?