how to remove subscriptions items of sqlserver 2000

Sir,
I am unable to remove replication (subscriptions items) from subscriber
database which has been removed from publications database.
I would be very much grateful if anyone could help me.
with regards,
chewang dorjiIf the wizards did not drop subscriptions correctly and some items still
seem to be replicated and have subscribers, you will have to use system SPs
to do the job. Check the sp_removedbreplication, sp_droppullsubscription,
sp_dropsubscription and related procedures in Books OnLine. If you are
talking only about the tables created on the subscriber, you have to drop
them manually - use the Drop Table statement.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Chewang Dorji" <drukfood@.druknet.bt> wrote in message
news:u9CTafRbDHA.2372@.TK2MSFTNGP10.phx.gbl...
> Sir,
> I am unable to remove replication (subscriptions items) from subscriber
> database which has been removed from publications database.
> I would be very much grateful if anyone could help me.
> with regards,
> chewang dorji
>

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 replication?

i used to the sql built to remove replication,but after i remove all replication,operating table of the database still report having replication conflit.why and how to remove all replication clearly?
thanks.
If the database is no longer involved in replication as a publisher or a
subscriber then you can use sp_removedbreplication.
HTH,
Paul Ibison
|||Hello all,
I think we have the same or similar problem.
We have removed the replication by using the Enterprise Manager, but we are still not able to alter tables.
We also tried to use sp_removedbreplication, but received the same error message after trying to alter the table.
Is there any way to remove old replication information from the DB?
Regards,
Marc
/*
Tuesday, May 11, 2004 9:55:10 AM
User:
Server: XXXXXX
Database: meas
Application: MS SQLEM - Data Tools
*/
'tTestNode' table
- Unable to rename column from 'Name' to 'qName'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot rename the table because it is published for replication.
|||There is a stored procedure to do this called sp_MSunmarkreplinfo which
takes a tablename as a parameter. Alternatively, setting replinfo to 0 in
sysobjects for the particular table should do it.
Regards,
Paul Ibison
|||you can safely issue a drop table statement to remove these tables. I normally do this
select 'drop table '+name from sysobjects where type='u' and name like '_onflict%' and status<0
the in the results portion I will have the drop table statements to drop these objects. I paste this into qa and run them.
Do this only if you have no active merge, queued or immediate updating publications in the database.

How to remove replication objects from a restored database?

Hi,
I've restored a database that had replication on it to a different server
without replication. How can I remove the replication objects from this
database?
I've googled and found nothing so far...
Regards
paul
Paul,
please try this:
http://msdn.microsoft.com/library/de...repl3_1mlq.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||On Fri, 17 Feb 2006 17:11:33 -0000, Paul Ibison wrote:

> Paul,
> please try this:
> http://msdn.microsoft.com/library/de...repl3_1mlq.asp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
Cheers Paul, but I'd tried that one - which doesn't remove the objects for
me.
I have SPs of the name of FLTR_ etc... that are still there, as well as
views SYNC_
This database was a replication source on the orginal server, not a
subscriber database.
|||Paul,
this proc is the best we have out of the box. Hilary has a script he has
posted up a few times to remove orphaned records, or you could knock one
together yourself - either way you'll need a customised solution.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

How to Remove Merge Replication?

Hi All:
I have setup Merge Replication (Push) & we are using SQL2000 sp3.
After testing a few things, I disabled the Publication. This did not remove
Subscription on the other Server.
I have a task stuck in Subcriptions, under Replication on SQL.
It Shows the Task as 'Running' Status and Last Action as 'Syncronization in
Progress'
Now I am not able to delete the table in the subscriber also, as it says
'This table has been setup from Replication'
Please suggest.
Thanks,
Anukul
You can use sp_removedbreplication 'dbname' on publisher and subscriber to
remove the system tables associated with replication.
If needed, there is a stored procedure to remove the replication setting on
a table called sp_MSunmarkreplinfo which takes a tablename as a parameter.
Alternatively, setting replinfo to 0 in sysobjects for the particular table
should do it.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks Paul:
I did try this procedure & was able to remove the system tables, including
the Job I mentioned. But it was still not letting us alter the structure or
drop the tables on which Replication was setup.
Please let me know what am I doing wrong.
Regards,
Anukul
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OHL64kGAFHA.1396@.tk2msftngp13.phx.gbl...
> You can use sp_removedbreplication 'dbname' on publisher and subscriber to
> remove the system tables associated with replication.
> If needed, there is a stored procedure to remove the replication setting
on
> a table called sp_MSunmarkreplinfo which takes a tablename as a parameter.
> Alternatively, setting replinfo to 0 in sysobjects for the particular
table
> should do it.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Anukul,
did you try sp_MSunmarkreplinfo?
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul:
I did try that one out also & BTW I am now able to remove Subscriber.
Thanks a Lot for ur help.
Regards,
Anukul
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:155e01c5023b$3917e340$a501280a@.phx.gbl...
> Anukul,
> did you try sp_MSunmarkreplinfo?
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||I would be interested in hearing from the community if anyone is having the
same type of problems on SQL 2005. We added a force option to sp_removed
which more aggressively drops replication objects. Additionally, we now drop
any rowguid columns that were added in merge.
Philip Vaughn
Program Manager
SQL Server Replication
This message is provided "AS IS" with no warranties, and confers no rights.
"Anukul" <anukuls@.yahoo.com> wrote in message
news:OCJxPYmAFHA.1388@.TK2MSFTNGP09.phx.gbl...
> Hi Paul:
> I did try that one out also & BTW I am now able to remove Subscriber.
> Thanks a Lot for ur help.
> Regards,
> Anukul
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:155e01c5023b$3917e340$a501280a@.phx.gbl...
>

How to remove a table after merge replication

I want to remove a table after merge replication, and i want to change the
identity range for replication
How can I modify the table or remove it from the Publication so that it can
be modified?
Regards
Srinivasan K
drop the subscriptions and run sp_dropmergearticle to drop the article.
If you are using automatic identity range management you will have to issue
the following commands.
sp_changemergearticle 'northwind','categories','pub_identity_range',300
go
sp_changemergearticle 'northwind','categories','identity_range',300
go
sp_changemergearticle 'northwind','categories','threshold',90
go
If you are not you can issue dbcc checkident to reseed the identity ranges
on both sides of the equation(s).
ie
dbcc checkident('categories',reseed,300)
Hilary Cotter
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
"Remove a table after merge replication" <Remove a table after merge
replication@.discussions.microsoft.com> wrote in message
news:F692A05B-5D94-46C7-96F0-6D7B06E07BBE@.microsoft.com...
> I want to remove a table after merge replication, and i want to change the
> identity range for replication
> How can I modify the table or remove it from the Publication so that it
can
> be modified?
>
> Regards
> Srinivasan K
>
>

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 tranactional replication

Hi,
Can any body tell me how to reinitialise a transactional replication.
Regards
Balaji.T
Go to your publication, right click and select reinitialize
That should do the trick.
Regards
"Prabbhu B T" wrote:

> Hi,
> Can any body tell me how to reinitialise a transactional replication.
> Regards
> Balaji.T
|||From the GUI as Zekske points out it is pretty straightforward. Using
scripts it'll be either sp_reinitsubscription or sp_reinitpullsubscription.
In all cases you'll need to subsequently run the snapshot agent then the
distribution agent to get the changes over.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

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 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?

How to recreate replication system objects?

Does anyone know what script I need to run to recreate the
replication system objects in MSSQL?
I believe it's in the Install Directory after installing SQL?
Will it destroy any existing publications/subscriptions on the server?
I have 2 other publications that are running I want to keep.
Thanks
RClick Replication component/ Generate SQL Script.
"Chris" <chriswinstone@.aol.com> wrote in message
news:1125399221.478160.216810@.o13g2000cwo.googlegr oups.com...
> Does anyone know what script I need to run to recreate the
> replication system objects in MSSQL?
> I believe it's in the Install Directory after installing SQL?
> Will it destroy any existing publications/subscriptions on the server?
> I have 2 other publications that are running I want to keep.
> Thanks
>
|||I'm guessing here, but did you have a failed installation? If so, then
reapplying sp4 should do the trick.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul
No I didn't have a failed installation as such. The replication was working
fine for about 18 months then all of a sudden I started getting errors from
the merge agent after executing sp_MSfetchidentityrange saying it could not
retrieve identity range resource for the table [TABLENAME].
A post from Hilary Cotter pointed me in the direction of the
msrepl_identity_range tables, however I decided to script the publication
for backup and try removing it. So I ran sp_removedreplication (probably too
hasty on that one!) then tried to run the puplication gen script thats when
I started getting the invalid object name 'syspublications' This is where I
am at at the moment. no replication at all! I can't even remove replication
manually - documented in Q324401!
I'm really stuck! Can't go forward or back! So I thought maybe recreating
the replication system objects would help me go in at least one direction!
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uyQXnTZrFHA.464@.TK2MSFTNGP15.phx.gbl...
> I'm guessing here, but did you have a failed installation? If so, then
> reapplying sp4 should do the trick.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Chris,
what about if you disable replication then reenable, then execute your
scripts?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul
How do you do this? In QA or EM?
Thanks
Paul Ibison wrote:
> Chris,
> what about if you disable replication then reenable, then execute your
> scripts?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
|||Chris,
in EM - 'Tools, Replication, Disable Publishing'.
HTH,
Paul Ibison
|||Thanks Paul
Thats worked!
I now have a problem when creating my scripted publication again! See later
post.
Thanks again!
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%236JW0YjrFHA.3060@.TK2MSFTNGP09.phx.gbl...
> Chris,
> in EM - 'Tools, Replication, Disable Publishing'.
> HTH,
> Paul Ibison
>

how to recover from suspect mode distribution database

Put the database into emergency mode and attempt to bcp the data out.
Hilary Cotter
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
"Kuba Guszkiewicz [cs]" <k.gluszkiewicz@.citysoftware.com.pl> wrote in
message news:%23Qw%23$mvZHHA.1388@.TK2MSFTNGP05.phx.gbl...
> Hi ng,
> during this night big (3GB) log file in my distribution database was
> corrupted,
> now my database is in suspect mode,
> is the any solution to recover database from this mode? for ex.: use bcp
> or something?
> i need this replication working...
> if anyone knows the solve please answer me,
> i will be very gratefull for step by step instructions
> thanks in advance
> kg
>
Try this, script out all publications and subscriptions. Then drop the
database, and recreate it.
Hilary Cotter
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
"Kuba Guszkiewicz [cs]" <k.gluszkiewicz@.citysoftware.com.pl> wrote in
message news:u3Sha4wZHHA.5020@.TK2MSFTNGP05.phx.gbl...
> Hilary,
> thanks, but what's next?
> i have to run bcp on each table or exist any bcp instuction which can i
> out all data?
> could you give me next step?
> i have to delete database?
> please help
> thanks
> --
> pozdrawiam
> Kuba Guszkiewicz
> k.gluszkiewicz@.citysoftware.com.pl
> tel. 509-650-351
> (22) 711-26-45
> (22) 711-26-46
> fax (22) 711-26-47
> Uytkownik "Hilary Cotter" <hilary.cotter@.gmail.com> napisa w wiadomoci
> news:O8T2vywZHHA.2432@.TK2MSFTNGP03.phx.gbl...
>
|||Ok, script out all your publications and subscriptions.
try to remove replication, by disabling it.
If this fails try the following:
sp_dropdistpublisher
if this doesn't work try it with sp_dropdistpublisher @.no_checks=1 and then
if this fails sp_dropdistpublisher @.no_checks=1 , @.ignore_distributor=1
Then
sp_dropdistributor
again if this fails try it with @.no_checks and then @.ignore_distributor
Then
sp_dropdistributiondb
Hilary Cotter
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
"Kuba Guszkiewicz [cs]" <k.gluszkiewicz@.citysoftware.com.pl> wrote in
message news:eitJ0fzZHHA.4136@.TK2MSFTNGP04.phx.gbl...
> thanks for any advice, but i need more detailed advice,
> Hilary could you help?
> Uytkownik "Hilary Cotter" <hilary.cotter@.gmail.com> napisa w wiadomoci
> news:%23Pgb$UxZHHA.3968@.TK2MSFTNGP06.phx.gbl...
>

How to read not for replication setting from meta info

Hello!
I am trying to read the not for replication setting of an identity
column from a Sql Server 7.0 database but I cannot find that piece of
information.
I check the information_schema tables that look approriate and the
sp_pkeys procedure. But no luck.
Has anyone an idea?
Thanks for you help. Take care, Peter.Hello again,
Sorry but I just found the solution: sp_help returns it.
Thanks, Peter.

How to query for records that have not been replicated

Hi,

I am using Merge Replication for synchronizing a bunch of laptops
running MSDE with a central SQL Server 2000 production server.

This database is used by an application that needs to know which
records have not yet been replicated, at any givem time.

Here's a simple scenario:

User A in laptop X starts his copy of the application. He syncs his
MSDE database through the application, to match the current central
servers' data. He then proceeds to add new records through the
application and, after he is done, he synchronizes his database with
the central server, through the application.

At any given time, the user might kill the application. He might add
some records today, a few more tomorrow or in a week and should be able
to change and delete records that have not yet been merged into the
production server.

The problem is that SQL Server does not have an easy way to tell which
records in the subscription tables have been inserted but not yet
replicated. I have been using the following query:

SELECT rowguid
FROM [MyTable]
INNER JOIN (
SELECT rowguid AS rep_id
FROM msmerge_contents
WHERE generation = joinchangegen AND generation = (
SELECT MAX(generation)
FROM msmerge_genhistory )
) dtable
ON rowguid_rep = dtable.rep_id

This query works for most cases but fails to identify the first record
created immediatly after a synchronization event.

What I would like to know is if there is a correct way of identifying
records which are "not-yet-replicated" on a given table that is part of
a merge replication process like the one described above.
Thanks in advance.<miltonmoura@.gmail.com> wrote in message
news:1104839914.237873.95740@.f14g2000cwb.googlegro ups.com...
> Hi,
> I am using Merge Replication for synchronizing a bunch of laptops
> running MSDE with a central SQL Server 2000 production server.

<snip
> What I would like to know is if there is a correct way of identifying
> records which are "not-yet-replicated" on a given table that is part of
> a merge replication process like the one described above.
> Thanks in advance.

I have no idea myself, but you might get a better response in
microsoft.public.sqlserver.replication.

Simon