Replication in SQL: February 2012

Saturday, February 25, 2012

replication merge not put instantaneous time out

replication type merge
suscription two(a-b)
function suscription (a)
not function suscription (b)
What this is the problem !! Help
error: replication merge not put instantaneous time out
thanks!
Christian,
please can you post up the complete error text from the merge agent, and
also list any distinctions between subscriber a and b.
TIA,
Paul Ibison

Replication merge instance is not find in Performance Viewer

Hi all,
I set the configuration for Merge replication for Subscription on
one database and
I have created the Merge replication for publication on another
machine.
And I updated columns of subscription database table and I find
publication machine database table also updated with subscription
database table, here my problem starts,
My problem is when I run replication for merge transaction, I have to
find instance of the Windows on my machine in Performance Viewer (to
see performance viewer goto control panel ->Administrator->performance
in this select performance counter as SQL Server: Replication merge)
but I am not finding the instance
Please some body help me out.
RasheedI am not exactly sure what you mean here. In performance monitor the
counters are by instance. The option to select an instance or all instances
is grayed out. This is by design.
--
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
<sk.rasheedfarhan@.gmail.com> wrote in message
news:1163512500.562695.183350@.h48g2000cwc.googlegroups.com...
> Hi all,
> I set the configuration for Merge replication for Subscription on
> one database and
> I have created the Merge replication for publication on another
> machine.
> And I updated columns of subscription database table and I find
> publication machine database table also updated with subscription
> database table, here my problem starts,
> My problem is when I run replication for merge transaction, I have to
> find instance of the Windows on my machine in Performance Viewer (to
> see performance viewer goto control panel ->Administrator->performance
> in this select performance counter as SQL Server: Replication merge)
> but I am not finding the instance
> Please some body help me out.
> Rasheed
>|||thanks for resopnse Mrs. Hilary cotter
I will explain......i am using SQL Server 2000, when I run replication
(it may be transaction or merge replication) windows components will
run internally.
1) when I was running replication transaction I can see instances in
Performance
viewer but
2) when I was running replication merge I cant see instances in
Performance
viewer
so my doubt is for replication merge can we have the Instance or not ?

Replication merge instance is not find in Performance Viewer

Hi all,
I set the configuration for Merge replication for Subscription on
one database and
I have created the Merge replication for publication on another
machine.
And I updated columns of subscription database table and I find
publication machine database table also updated with subscription
database table, here my problem starts,
My problem is when I run replication for merge transaction, I have to
find instance of the Windows on my machine in Performance Viewer (to
see performance viewer goto control panel ->Administrator->performance
in this select performance counter as SQL Server: Replication merge)
but I am not finding the instance
Please some body help me out.
Rasheed
I am not exactly sure what you mean here. In performance monitor the
counters are by instance. The option to select an instance or all instances
is grayed out. This is by design.
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
<sk.rasheedfarhan@.gmail.com> wrote in message
news:1163512500.562695.183350@.h48g2000cwc.googlegr oups.com...
> Hi all,
> I set the configuration for Merge replication for Subscription on
> one database and
> I have created the Merge replication for publication on another
> machine.
> And I updated columns of subscription database table and I find
> publication machine database table also updated with subscription
> database table, here my problem starts,
> My problem is when I run replication for merge transaction, I have to
> find instance of the Windows on my machine in Performance Viewer (to
> see performance viewer goto control panel ->Administrator->performance
> in this select performance counter as SQL Server: Replication merge)
> but I am not finding the instance
> Please some body help me out.
> Rasheed
>
|||thanks for resopnse Mrs. Hilary cotter
I will explain......i am using SQL Server 2000, when I run replication
(it may be transaction or merge replication) windows components will
run internally.
1) when I was running replication transaction I can see instances in
Performance
viewer but
2) when I was running replication merge I cant see instances in
Performance
viewer
so my doubt is for replication merge can we have the Instance or not ?

Replication merge instance is not find in Performance Viewer

Hi all,
I set the configuration for Merge replication for Subscription on
one database and
I have created the Merge replication for publication on another
machine.
And I updated columns of subscription database table and I find
publication machine database table also updated with subscription
database table, here my problem starts,
My problem is when I run replication for merge transaction, I have to
find instance of the Windows on my machine in Performance Viewer (to
see performance viewer goto control panel ->Administrator->performance
in this select performance counter as SQL Server: Replication merge)
but I am not finding the instance
Please some body help me out.
RasheedI am not exactly sure what you mean here. In performance monitor the
counters are by instance. The option to select an instance or all instances
is grayed out. This is by design.
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
<sk.rasheedfarhan@.gmail.com> wrote in message
news:1163512500.562695.183350@.h48g2000cwc.googlegroups.com...
> Hi all,
> I set the configuration for Merge replication for Subscription on
> one database and
> I have created the Merge replication for publication on another
> machine.
> And I updated columns of subscription database table and I find
> publication machine database table also updated with subscription
> database table, here my problem starts,
> My problem is when I run replication for merge transaction, I have to
> find instance of the Windows on my machine in Performance Viewer (to
> see performance viewer goto control panel ->Administrator->performance
> in this select performance counter as SQL Server: Replication merge)
> but I am not finding the instance
> Please some body help me out.
> Rasheed
>|||thanks for resopnse Mrs. Hilary cotter
I will explain......i am using SQL Server 2000, when I run replication
(it may be transaction or merge replication) windows components will
run internally.
1) when I was running replication transaction I can see instances in
Performance
viewer but
2) when I was running replication merge I cant see instances in
Performance
viewer
so my doubt is for replication merge can we have the Instance or not ?

Replication Merge and Web Service

Hi,
how can I make it work the following procedure:
http://support.microsoft.com/default...b;en-us;319646
in a Web Service? Namely, the previous procedure should become a web
service... I have already tried to create a web service and copy almost all
the code... but after having referenced it as a web reference and then
colling the service, I got the following error:
An unhandled exception of type 'System.Web.Services.Protocols.SoapException'
occurred in system.web.services.dll
Additional information: System.Web.Services.Protocols.SoapException: Server
was unable to process request. -->
System.Runtime.InteropServices.COMException (0x80040E08): The process could
not connect to Distributor 'MYSQLSERVER'.
at SQLMERGXLib.SQLMergeClass.Initialize()
at tAIMx.Services.tAIMx_ReplicationServices.Merge(Str ing strPublisher,
String strDistributor, String strSubscriber, String strPublication, String
strPublisherDatabase, String strSubscriberDatabase) in
c:\inetpub\wwwroot\myservices\replicationservices. asmx.cs:line 97
-- End of inner exception stack trace --
If I run the code without copying it in a web service, it works very well!!
Please help me.
how are you connecting to your distributor? You might want to try using sql
authentication as this seems to be a authentication problem.
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
"Siu" <Siu@.discussions.microsoft.com> wrote in message
news:BD0D9A31-8E50-465A-BC8B-90D0223306F2@.microsoft.com...
> Hi,
> how can I make it work the following procedure:
> http://support.microsoft.com/default...b;en-us;319646
> in a Web Service? Namely, the previous procedure should become a web
> service... I have already tried to create a web service and copy almost
all
> the code... but after having referenced it as a web reference and then
> colling the service, I got the following error:
> An unhandled exception of type
'System.Web.Services.Protocols.SoapException'
> occurred in system.web.services.dll
> Additional information: System.Web.Services.Protocols.SoapException:
Server
> was unable to process request. -->
> System.Runtime.InteropServices.COMException (0x80040E08): The process
could
> not connect to Distributor 'MYSQLSERVER'.
> at SQLMERGXLib.SQLMergeClass.Initialize()
> at tAIMx.Services.tAIMx_ReplicationServices.Merge(Str ing strPublisher,
> String strDistributor, String strSubscriber, String strPublication, String
> strPublisherDatabase, String strSubscriberDatabase) in
> c:\inetpub\wwwroot\myservices\replicationservices. asmx.cs:line 97
> -- End of inner exception stack trace --
> If I run the code without copying it in a web service, it works very
well!!
> Please help me.
|||Hi Hilary,
thank you: I've used an NT_Authentication as you can see from the code...
I've discovered that if I run the code (.exe) as an administrator user, it
works, but under another user, it doesn't work. I don't know how to force the
user under who the code should run... can you help me again?
"Hilary Cotter" wrote:

> how are you connecting to your distributor? You might want to try using sql
> authentication as this seems to be a authentication problem.
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:BD0D9A31-8E50-465A-BC8B-90D0223306F2@.microsoft.com...
> all
> 'System.Web.Services.Protocols.SoapException'
> Server
> could
> well!!
>
>
|||is this user in the PAL?
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
"Siu" <Siu@.discussions.microsoft.com> wrote in message
news:DF5EEA36-9B95-4D13-AF5F-02CE6BD141BB@.microsoft.com...
> Hi Hilary,
> thank you: I've used an NT_Authentication as you can see from the code...
> I've discovered that if I run the code (.exe) as an administrator user, it
> works, but under another user, it doesn't work. I don't know how to force
the[vbcol=seagreen]
> user under who the code should run... can you help me again?
>
> "Hilary Cotter" wrote:
sql[vbcol=seagreen]
almost[vbcol=seagreen]
then[vbcol=seagreen]
strPublisher,[vbcol=seagreen]
String[vbcol=seagreen]
|||What is the PAL?
"Hilary Cotter" wrote:

> is this user in the PAL?
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:DF5EEA36-9B95-4D13-AF5F-02CE6BD141BB@.microsoft.com...
> the
> sql
> almost
> then
> strPublisher,
> String
>
>
|||Your Publication Access List. This is a list of accounts which can pull
subscriptions.
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
"Siu" <Siu@.discussions.microsoft.com> wrote in message
news:C39C0E46-E0AA-483B-BF8A-31E0127AA2B5@.microsoft.com...[vbcol=seagreen]
> What is the PAL?
> "Hilary Cotter" wrote:
code...[vbcol=seagreen]
user, it[vbcol=seagreen]
force[vbcol=seagreen]
using[vbcol=seagreen]
web[vbcol=seagreen]
System.Web.Services.Protocols.SoapException:[vbcol=seagreen]
process[vbcol=seagreen]
strPublication,[vbcol=seagreen]
very[vbcol=seagreen]
|||Thank you Hilary,
you gave me an idea how to find the problem which was the permission on the
replicated database: the user, under which the code runs, must have the owner
role of the database... now it works very well.
"Hilary Cotter" wrote:

> Your Publication Access List. This is a list of accounts which can pull
> subscriptions.
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:C39C0E46-E0AA-483B-BF8A-31E0127AA2B5@.microsoft.com...
> code...
> user, it
> force
> using
> web
> System.Web.Services.Protocols.SoapException:
> process
> strPublication,
> very
>
>

Replication merge

Hi All
Can i compress and cryptography data in the replication merge process of SQL
SERVER 2000?
Where can i find some informations?
Thanks Alex
What you can do is register your servers in client network utiltity with the force protocol encryption option.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Alex" wrote:

> Hi All
> Can i compress and cryptography data in the replication merge process of SQL
> SERVER 2000?
> Where can i find some informations?
> Thanks Alex
>
>

Replication mechanism

Hello,
My situation is as follows:
I use Replication in my Mobile Application and when the PocketPc is
connected via USB the replication works fine. But when I tried to synchonize
the data via WLAN it does not work. My quoted url in my code looks as follows:
oRpl.InternetUrl = "http://IP-Adress/HelpDesk/sscesa20.dll"; //I also tried
it to replace the IP-Address with the machineName of my Desktop but it does
also not work.
I also tried to type in this address in my PocketPc when the WLAN is
activated but it occurs always an error that this page could not be loaded.
Does anybody know what else could be go wrong?

thx
patrick
what is the error message you are getting?
Also what happens when you use IE to connect to this url from your PocketPC?
You should get a message saying SQL Server CE agent or something like that.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"pat" <pat@.discussions.microsoft.com> wrote in message
news:09678E54-FBB5-44EA-9327-6ED5FCBD28D7@.microsoft.com...
> Hello,
> My situation is as follows:
> I use Replication in my Mobile Application and when the PocketPc is
> connected via USB the replication works fine. But when I tried to
> synchonize
> the data via WLAN it does not work. My quoted url in my code looks as
> follows:
> oRpl.InternetUrl = "http://IP-Adress/HelpDesk/sscesa20.dll"; //I also
> tried
> it to replace the IP-Address with the machineName of my Desktop but it
> does
> also not work.
> I also tried to type in this address in my PocketPc when the WLAN is
> activated but it occurs always an error that this page could not be
> loaded.
> Does anybody know what else could be go wrong?

> thx
> patrick
|||That's the strange thing no error message occurs.

When it is possible to
call this url "http://IP-Adress/HelpDesk/sscesa20.dll"; with my PocketPc and
the SQL Server CE Agent message appears, does then the replication must work?
patrick
|||Not necessarily, all it means is that your Pocket PC can connect to the web
server and the virtual directory. I think it also means that your web server
security is set up correctly. Now check the underlying security of your
snapshot folder. Does this reflect read access for the anonymous account
(IUSER_MachineName, or whatever account you are authenticating with)?
Then you should run profiler to determine how far into the replication
process your pull is going. This will help to trouble shoot further.
What would be really helpful is if you could post the error message your
program is raising.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"pat" <pat@.discussions.microsoft.com> wrote in message
news:732A1E5F-E844-4D0C-B119-B75692989AF7@.microsoft.com...
>
> That's the strange thing no error message occurs.

When it is possible
> to
> call this url "http://IP-Adress/HelpDesk/sscesa20.dll"; with my PocketPc
> and
> the SQL Server CE Agent message appears, does then the replication must
> work?
> patrick

Replication mechanism

Hello,
Can anybody here explain me shortly how the mechanism of replication
generally works? (with SQL Server CE Agent, SQL Server Agent, etc.)
thx
robert
Robert,
the 'SQL Server CE documentation' has a good set of descriptions and BOL
will explain standard replication. Is there something specific you have in
mind?
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||With merger replication each row has a tracking column called a rowguid
column. Each row has a different value for this rowguid column, but
globally tables in the publisher and all subcribers which contain this
row will have the same value for this guid. This enables the merge
replication process to track changes to this row. This of it as a
Social Security Number, or Social Insurance Number (not sure what the
non American, non Canadian equivalents are).
Each table which is part of a merge publication has triggers of it, so
if one of the rows is modified tracking information is written to
tracking tables.
When the merge agent runs (run by SQL Server Agent) it consults these
tracking tables to determine what has changed since the last time it
has run. It has a counter called a generation which increments each
time the merge agent runs. It then gets a list of the rows which has
changed since the last time it ran and brings them to the publisher in
batches.
When the list of rows arrives at the publisher the publisher compares
its list with the list of changes it has and figures out what goes
where. If changes have to be made on the subsciber it fires procs there
to make these changes, if changes have to be made locally it uses sql
statements. If it detects that the same rows have changed on both the
subscriber and publisher it figures out who wins by using the conflict
resolution policy and logs the conflict info to conflict tracking
tables.
It then gets the next batch.
SQL CE does much the same thing - only it is done programmatically.
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

Replication Mechanism

Hello,
My Replication works fine when my PocketPc is connected via USB Cable with
the Desktop. Do I have to implement any additional things that the
Replication Mechanism also works with WLAN? (My PocketPc has WLAN). Is the
oRpl.InternetUrl the decisive factor? - because at this url I have stated the
following url: http://machineName/HelpDesk/sscesa20.dll.
thx
robert
That depends.
On your Publisher do this: http://machineName/HelpDesk/sscesa20.dll
I think this gives you a message saying something like "SQL Server Agent CE
Runnning" or something like this.
Then on your Subscriber issue the same query through the Ineternet Exporer
program. You should see the same result.
If you do, you have connectivity and your problem is likely with setting up
security in your script. If you can't you have to configure security on your
publisher.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"robert" <robert@.discussions.microsoft.com> wrote in message
news:770EC375-0C9F-4304-9D33-E03AE7583C48@.microsoft.com...
> Hello,
> My Replication works fine when my PocketPc is connected via USB Cable with
> the Desktop. Do I have to implement any additional things that the
> Replication Mechanism also works with WLAN? (My PocketPc has WLAN). Is the
> oRpl.InternetUrl the decisive factor? - because at this url I have stated
> the
> following url: http://machineName/HelpDesk/sscesa20.dll.
> thx
> robert
|||Okay thank you for your reply, unfortunately I have two more questions:
1)Do I not have to replace the machineName with my IP-Adress of the desktop
when I call this in the IE of the PocketPc?
2)And what can be the problem if this would not work, although with
connectivity of the USB it works?
thx
robert
|||1) You may have to. The pocket pc will attempt to do name resolution on its
own using a local broadcast. If the IP address works and the name doesn't
you have a problem with name resolution.
2) with the USB you have two options in active sync, connecting to the
INternet or work. If you were connected to work it will find your host no
problem as it is using USB. If not, it has to do the same name resolution as
it will using Wireless.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"robert" <robert@.discussions.microsoft.com> wrote in message
news:C6222C3B-F64B-4219-BF2C-2DFEB166EA93@.microsoft.com...
>
> Okay thank you for your reply, unfortunately I have two more questions:
> 1)Do I not have to replace the machineName with my IP-Adress of the
> desktop
> when I call this in the IE of the PocketPc?
> 2)And what can be the problem if this would not work, although with
> connectivity of the USB it works?
> thx
> robert

Replication Maintanance Issues!

Hi Guys/Gals,

Need some comments/ideas on the following scenario:

Current Situation:
-I have a PROD DB and a REPORTING DB( Separte Physical Servers).
-PROD DB replicates (Transactional) to REPORTING DB. ( Using only Replication Wizard to set up, quite easy)
-DB is for running shopfloor(manufacturing) applications, thus needs to be minimum downtime.
-Retention period for PROD DB data is 3 months ,Reporting DB is 3 years.

Future Problem that I will encounter:
-Purging of data in PROD DB will be replicated into Reporting.
-Schema change in PROD DB need to delete existing Publication before able to change schema.
-After schema change, need to recreate publication and rerun snapshot.

Questions:
-How to prevent the purging to be replicated to Reporting?
Switching off Replication when Purging takes place will not help. The only solution
I am thinking of is to alter the store procedure for replication during purging.
Is there any other "CLEANER" hassle free way?

- How to cater shema changes better?
Currently the data is not alot, but down the road, it might go to Terabytes, by then running a
snapshot will cost us alot. Is there any way not to redo a snapshot for this scenario?

Please give your comments/ideas/ .

Thanks.--> another thing I miss out, doing a snapshot again would clear any data
Reporting DB has stored. e.g. Prod DB( 3 months data) , Reporting DB(1 year data), do snapshot....all gone.|||Anyone...any suggestions?|||Patrick, have you thought about replication without snapshot? That will minimize the impact of snapshoting on publications.

Changing replication stored procs sounds the best way to avoid data changes on the subscribers. But it could go wild if you have a lot of sprocs to modify.|||replication without snapshot..hmmm...I'll check it out...
no idea as of how not to have a snapshot for now....can u give some highlights...

Anybody else? I'm sure other ppl would have the same senario as me....|||there was a thread a few days back that was talking about transactional replication without snapshot. check it out:
http://www.dbforums.com/showthread.php?p=3665793#post3665793

SQL Magazine also has an article on this.

I have used this technique for years. The key is to ensure publisher and subscriber are in sync without snapshoting. make sure no one can do transactions in the servers. break replication, dropping subscriber, articles etc, while the publisher and subscriber dbs are not modified. At the end when you reset up replication, click on the option that says "subscriber already has the data".

Replication Loop Back Detection Problems in SQL Server 2000

Hi,

I am monitoring my replication process and I have a problem with the loop detection, I can see origined transacctions in the server, executed in the same for the replication.

The subscriptions configuration is sp_helpsubscription

exec sp_addsubscription @.publication = N'PUBLICATION',
@.article = N'all',
@.subscriber = N'192.168.0.23',
@.destination_db = N'PRUEBABD',
@.sync_type = N'none',
@.update_mode = N'read only',
@.offloadagent = 0,
@.dts_package_location = N'distributor',
@.loopback_detection = 'true'
GO

I need for help.

Sorry, it's not clear to me what the problem is. Are you getting an error of some sort?|||

Yes, I have loops in the replication between the subscribers and too many deadlocks.

My topology is

Server A replicates to Server P,

the Server P replicates to Server A,

Server B replicates to Server P and

the Server P replicates to Server B.

I am using transactional replication,

|||sorry, i'm still not clear. what exactly is the error. if it's deadlock, what statements are deadlocking?|||My problem is that loop back detection is unless when I registed the subscriptions with IP. The publicator servers are registered for name.

Replication looking for errant sysserver links

We have replication successfully running but when I tried to set up a new test instance on completely different servers (Server A to Server B, say) the push agent to create the susbcription on Server B complains

'Could not find server 'Server C' in sysservers. Execute sp_addlinkedserver. . . .'

Server C was never configured as a subscriber for the publication in the first place. What's more, Server C is actually a working linked server and definitely is in sysservers for Server A.

I originally tried this on yet another server pair and got a similar message referencing a server name that no longer exists. I stopped messing with that one, figuring it was some historical naming issue I didn't want to mess with. But now I'm stumped and intrigued. Can anyone help?

Did you deploy your subscriber through a script? Perhaps you forgot to edit the script for the new topology.|||Unfortunately, no. I just used the Wizards, and specified everything. Bit bewildering.|||Do "select * from sysservers" to see if you have any rogue entries in there. You can remove the incorrect ones via sp_dropserver.|||

The supposedly unlinked server is definitely linked, and shows up correctly in the sysserver collection, which also looks fine.

It's wierd, but it's only a test instance I was trying to set up, Our live replication is working fine and we didn't really need the test this time.

I think these servers went through name changes. It probably had the server linked under its old name. Just a guess, but we had a lot of problems changing server names when our corporation was absorbed into a larger IT force and we had to follow a new naming convention. Replication broke, of course, and I recall we needed to clean out various tables before we could reimplement. So I'm guessing it's something along those lines.

Replication Logreader query

We had replication set up and working successfully for 2+ years between an intranet server and a webserver (offsite).

The web server was moved and the replication went out of sync. :mad:

Now when we try the replication it is trying to start from scratch and as you can imagine there is quite a lot of data after two years!

I have scheduled the logreader to run but after 8 hours it is still running is there any way to find out how long it should take?

We have removed any unnecessary data to try to help speed up the process.

Help appreciatedYou probably need the snapshot agent instead of the logreader agent. It takes the starting "snapshot" of the database to send to the subscriber, to restart replication.

-PatP|||We ran the snaphot first thing this morning - job outcome was successful.

Getting this message when we look at the snapshot step details for the run agent step:

"A snapshot was not generated because no subscriptions needed initialization. The step succeeded."

Any ideas on how to find out how long the logreader will take?|||Did you reinitialize the publications? That will flag the publication for a new snapshot. Just FYI, you probably want to script the indicies and the permissions on the subscriber, since the replicated tables will be destroyed and recreated as part of the process.

-PatP|||We have reinitialised the publications.

Thanks for the tip on indexes etc.

Any tips on finding out how long to complete the logreader and then distribution tasks? :confused:|||The logreader is eternal, if replication is going on, the logreader is running. The snapshot agent usually doesn't run too long, it simply copies the data from the published tables into flat files, but its performance is VERY dependant on your hardware (fast hardware/short runtime, slow hardware/well, you know that drill).

The distribution task depends on way too much stuff for me to take a guess at its performance... The network connection, the subscriber performance, the distributors disk, and about a half a gazillion other factors come into play.

Once the tasks start running, you can sometimes get better ideas about the performance, but knowing nothing about your configuration I can't even hazard a guess!

-PatP|||Pat

Distribution is executing - looks like it will be a long night :)

Thanks for your help - it is greatly appreciated

Cheers|||If you wander down to the distribution agents in your replication monitor (on the distributor), you can at least watch the "paint dry" via the status messages. It ain't much, but it is better than nothing!

-PatP

Replication LogReader

Once i configured the replication throwing the following error on logreader

2007-02-08 16:47:39.641 Status: 0, code: 1007, text: 'Another logreader agent for the subscription(s) is running or the server is working on a previous request by the same agent.'.
2007-02-08 16:47:39.641 Another logreader agent for the subscription(s) is running or the server is working on a previous request by the same agent.
2007-02-08 16:47:39.641 Status: 0, code: 22037, text: 'The last step did not log any message!'.

Please let me know if you have any solutions to fix this issue.

Can you provide more detail about your replication setup?

Gary

|||My guesss is you have two logreader agent jobs running against the same publisher db. Stop one of the jobs, then delete/disable it, you should have only one logreader agent job per published database. If you do not have two jobs, then somehow the logreader agent process when you ran it the first time did not shut down properly. THe safest way to clear this issue is to restart the SQL Server service on the distributor machine.|||

I have multiple publisher and multiple subscriber for same db.when i configure it this way it is thorowing the above error?

replication log reader failed

Hi all,
Sql server 7.0
I have replication jobs which replicates the data from one
server to another.
one of our server was down for some duration of time and
the replication job log reader has failed it gives the
error msg log reader agent: "the process could not
execute 'sp_repldone/sp_replcount".
pls help me in solving this problem.
TIA
Haseeb,
I thought these issues had been sorted in SP>=2. If you don't have it
installed it's worth putting on. Either way, you could try increasing the
Query timeout (default: 300 seconds) on the logreader by editing the
QueryTimeout option as this is I think the issue.
HTH,
Paul Ibison
|||I also had this problem and setting the QueryTimeout did not help. I tried everything in every posting I could find and nothing worked. I ended up deleting all my publications to reset the Log Reader Agent, then re-setup the publications and subscriptio
ns. Once the Log Reader was recreated, everything worked fine again.
"Paul Ibison" wrote:

> Haseeb,
> I thought these issues had been sorted in SP>=2. If you don't have it
> installed it's worth putting on. Either way, you could try increasing the
> Query timeout (default: 300 seconds) on the logreader by editing the
> QueryTimeout option as this is I think the issue.
> HTH,
> Paul Ibison
>
>

replication locking (sql2000 / transactional)

Currently, we have a table replicated from one database to another on the
same server.
If I update 127 records based on the primary key, the subscription process
locks all the records until all the 127 commands have been executed.
Seamingly regardless of how they were updated.
eg.
CREATE TABLE Orgs ( OrganisationID INT PRIMARY KEY CLUSTERED ,
TimeLastUpdated DATETIME NOT NULL )
DECLARE @.SelectedOrgs ( OrganisationID INT PRIMARY KEY CLUSTERED )
/* ... insert 127 organisations to update here ... */
-- Process Type 1
UPDATE Orgs SET TimeLastUpdated = GETDATE()
FROM Orgs INNER JOIN @.SelectedOrgs SO ON Orgs.OrganisationID =
SO.OrganisationID
-- Process Type 2
WHILE ( blah )
BEGIN
-- one at a time in asc order
SELECT @.OrgID = OrganisationID FROM @.SelectedOrgs WHERE ( blah )
UPDATE Orgs SET TimeLastUpdated = GETDATE() WHERE OrganisationID =
@.OrgID
END
Using the default isolation level and no explicit transactions the table in
the subscriber database was locked until the commands had all been executed.
What gives - both types lock the whole table on the subscriber.
Surely it's not meant to use the same locks as were applied when the data
was updated?
Is there any to stop it locking the whole thing while it processes the
commands?
Ideally we'd upgrade to 2k5 and use row versioning... but that wont happen
for a while.

I need to implement a similar thing on a much larger database which needs to
be up 24/7 and can't be locked for long periods of time, mean while on the
publisher, 5% of the data may be changed in one go - but if we can't get it
to use optimistic locking on the subscriber we can't use replication.
Rebecca,
an update statement always has an implicit transaction. if you use
lumigent's Logexplorer you can see how this works. Your update statement will
be logged to the transaction log as :
BEGIN TRAN
Update Orgs SET TimeLastUpdated = GETDATE() where OrganizationID = 1
Update Orgs SET TimeLastUpdated = GETDATE() where OrganizationID = 2
..
..
..
Update Orgs SET TimeLastUpdated = GETDATE() where OrganizationID = 127
COMMIT TRAN
This is read by the log reader agent and converted to stored procedure
calls, but also with the transaction (AFAIR same XACT in msrepl_commands) .
The distribution agent applies it in the same way.
The table itself shouldn't be locked (lock escalation shouldn't occur on
such a low # rows), and inserting a record at the same time as the
distribution agent runs should prove this to be true.
Anyway, to answer your question more directly, -MaxCmdsInTran should allow
you to break the ACID properties and commit separate parts of the update as
separate transactions.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication Limiting Subscribers

How can we limit the number of anonymous merge subscribtions to a
given publication? Can we limit it by machine MAC address?
(Bump!)
Guys I really need an answer to this question.
How can we limit the number of anonymous merge subscribtions to a
given publication (assuming i can have only one sql account per
publication and no NT authentication)?
The problem with giving a set of sql accounts is that they can be
reused.
Can we limit it by machine MAC address?
Thanks,
Hananiel
hananiel@.yahoo.com (Hananiel) wrote in message news:<e338e321.0410130607.37e214d5@.posting.google. com>...
> How can we limit the number of anonymous merge subscribtions to a
> given publication? Can we limit it by machine MAC address?

Replication Limit?

Is there a limit to how many databases can be replicated in a MSDE 2000
environment? We have several servers with several replicated MSDE 2000
databases. It seems that we are hitting a limit because we cannot replicate
any more databases. Any ideas?
What kind of problems are you having?
Are you not able to setup anymore databases for replication or does the
replication just fail.
How many databases are you replicating on each server?
Have you off-loaded the distributor database to another server or does each
server act as its own distributor?
Jim
"VB Programmer" <growNO-SPAM@.go-intech.com> wrote in message
news:euv7a7jHEHA.2876@.TK2MSFTNGP09.phx.gbl...
> Is there a limit to how many databases can be replicated in a MSDE 2000
> environment? We have several servers with several replicated MSDE 2000
> databases. It seems that we are hitting a limit because we cannot
replicate
> any more databases. Any ideas?
>

Replication limit?

Is there a limit to how many databases can be replicated in a MSDE 2000
environment? We have several servers with several replicated MSDE 2000
databases. It seems that we are hitting a limit because we cannot replicate
any more databases. Any ideas?
there is a connection limit. MSDE is throttled to 8 simultaneous
connections. This might be what you are bumping into.
"VB Programmer" <growNO-SPAM@.go-intech.com> wrote in message
news:es6cv7jHEHA.3576@.TK2MSFTNGP10.phx.gbl...
> Is there a limit to how many databases can be replicated in a MSDE 2000
> environment? We have several servers with several replicated MSDE 2000
> databases. It seems that we are hitting a limit because we cannot
replicate
> any more databases. Any ideas?
>
|||Any way around that?
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23GwkWlkHEHA.3528@.TK2MSFTNGP09.phx.gbl...
> there is a connection limit. MSDE is throttled to 8 simultaneous
> connections. This might be what you are bumping into.
> "VB Programmer" <growNO-SPAM@.go-intech.com> wrote in message
> news:es6cv7jHEHA.3576@.TK2MSFTNGP10.phx.gbl...
> replicate
>
|||As Hilary mentionned, the limit is 8 simultaneous connections, and that
means CONCURRENT connections. So, by implementing schedules so that the
connections do not occur at the same time, I suppose you might work your way
out.
Raj Moloye

Replication latency

Hi,
I have set up a transactional replication on two SQL Server
2000 (SP3) machines.
How do I determine the time it passes between the
transaction was placed in the transaction log at the
Publisher and it has finished at the Subscriber?
--
Many thanks,
OskRun performance monitor... YOu should notice that there will now be new
counters for replication, one of which is latency...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Osk" <anonymous@.discussions.microsoft.com> wrote in message
news:2aa901c509c4$9d8b76d0$a501280a@.phx.gbl...
> Hi,
> I have set up a transactional replication on two SQL Server
> 2000 (SP3) machines.
> How do I determine the time it passes between the
> transaction was placed in the transaction log at the
> Publisher and it has finished at the Subscriber?
> --
> Many thanks,
> Osk

Replication Latency

Hi:
Latency is very high in replication monitor even though I don't see any
commands to be applied in sp_browsereplcmds. Do you know from where it gets
the latency number from in distribution database because it is misleading?
Thanks
IIRC it gets it from the table MSreplication_monitordata in the distribution
database.
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
"Sal" <Sal@.discussions.microsoft.com> wrote in message
news:ACB19921-E431-4DDE-A7EB-F2D1935E84D3@.microsoft.com...
> Hi:
> Latency is very high in replication monitor even though I don't see any
> commands to be applied in sp_browsereplcmds. Do you know from where it
> gets
> the latency number from in distribution database because it is misleading?
> Thanks
|||I can't find this table "MSreplication_monitordata" in distribution database.
"Hilary Cotter" wrote:

> IIRC it gets it from the table MSreplication_monitordata in the distribution
> database.
> --
> 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
>
> "Sal" <Sal@.discussions.microsoft.com> wrote in message
> news:ACB19921-E431-4DDE-A7EB-F2D1935E84D3@.microsoft.com...
>
>
|||You use the term replication monitor which is a tool in SQL 2005. What
version of SQL Server are you running?
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
"Sal" <Sal@.discussions.microsoft.com> wrote in message
news:565FB679-582F-4933-9E9D-F9CE558EACEA@.microsoft.com...[vbcol=seagreen]
>I can't find this table "MSreplication_monitordata" in distribution
>database.
> "Hilary Cotter" wrote:
|||I am using sql server 2000. Please let me know
"Hilary Cotter" wrote:

> You use the term replication monitor which is a tool in SQL 2005. What
> version of SQL Server are you running?
> --
> 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
>
> "Sal" <Sal@.discussions.microsoft.com> wrote in message
> news:565FB679-582F-4933-9E9D-F9CE558EACEA@.microsoft.com...
>
>
|||Don't forget to take into account the polling intervals of your
logreader and distribution agents. Even though theses agents seem to
run continuously they in fact do not. Check out BOL for the default
intervals. I think they are around 5secs. One way of reducing latency
is by reducing this refresh interval. Be careful though you need to
strike a balance between low latency and agent thrashing away trying
to get data all the time.
Regards,
Jim Katsos
http://jims-spanakopita.blogspot.com/

Replication latency

Hi,
I have set up a transactional replication on two SQL Server
2000 (SP3) machines.
How do I determine the time it passes between the
transaction was placed in the transaction log at the
Publisher and it has finished at the Subscriber?
Many thanks,
Osk
Run performance monitor... YOu should notice that there will now be new
counters for replication, one of which is latency...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Osk" <anonymous@.discussions.microsoft.com> wrote in message
news:2aa901c509c4$9d8b76d0$a501280a@.phx.gbl...
> Hi,
> I have set up a transactional replication on two SQL Server
> 2000 (SP3) machines.
> How do I determine the time it passes between the
> transaction was placed in the transaction log at the
> Publisher and it has finished at the Subscriber?
> --
> Many thanks,
> Osk

Replication latency

Hi,
I have set up a transactional replication on two SQL Server
2000 (SP3) machines.
How do I determine the time it passes between the
transaction was placed in the transaction log at the
Publisher and it has finished at the Subscriber?
Many thanks,
OskRun performance monitor... YOu should notice that there will now be new
counters for replication, one of which is latency...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Osk" <anonymous@.discussions.microsoft.com> wrote in message
news:2aa901c509c4$9d8b76d0$a501280a@.phx.gbl...
> Hi,
> I have set up a transactional replication on two SQL Server
> 2000 (SP3) machines.
> How do I determine the time it passes between the
> transaction was placed in the transaction log at the
> Publisher and it has finished at the Subscriber?
> --
> Many thanks,
> Osk

Replication keeps failing after one failure

Hi,
We are running Merge Replication on Sql Server 2K with multiples MSDE 2K subsciber.The Replication is getting done through a Visual Basic Application and it works fine as long as it does not fail.Once the replication fails on the Clients machine then we always need to blow the Local Database on the Client's machine and then start the Merge Replication process again.I wonder Why?Any help is really appriciated.. :(It's necessary adjust the retry count for the merge agent, in the event it fails (e.g. remote computer is turned off, network failure etc.). Expand Replication monitor, expand agents, click on merge agents. A list of merge agents, corresponding to each location is listed on the right. To change retry count for a merge agent, highlight the merge agent, right click and select agent properties. Click on tab "Steps", Highlight ID 2 (step 2 - run agent), click on edit. Step name should say "Run agent". Click on Advanced tab, and adjust the retry count and retry interval.
:D|||Thanks for your reply and I will increase the Number of Retry but my question is still unanswered and that's Why the Replication keeps failing after one failure?Is this turning on some flag somewhere in the Sql Server after a failure?|||Ok, I'm confused.

Replication is done via a Visual Basic program?

Replication is a configuration of Sql Server. Has nothing to do with Visual Basic.

What kind of Merge replication is setup? Merge continuosly, or scheduled merge?

If Merge continuously, then the retry count and schedule HAS to be changed. The defaults will cause the agent to fail if the connection is down for just 10 minutes. (10 retries, at 1 minute intervals).

Also, when you say replication fails, there are error messages that can be viewed via replication monitor. The agent may try 10 times, and on failure display 1 message. That doesn't mean there were no retries.|||It's a Merge Replication which runs on Demand through Visual Basic Application.The process works fine 9/10 times but if its fails then it keeps failing and the error log says "The Process was Successfully Stopped".I also don't think that it involves any network issue as the subscriber is connected to the network all the time.
Also once the Synchronization fails then we need to set the Initial database at the subscriber(which involves defining the subscriber,creating the local DB,Copying Roles and creating a dynamic Merge Replication job) and then do the Regular Synchronization,which works fine thereafter.

I don't know Y?:confused:

Replication jobs owned by sa

The reason sa is often suggested as the owner of
replication jobs is that when the job runs, there is an
active directory lookup performed of the job owner. This
is the reason sa is used - no AD lookup required. The
jobs themselves are run under the authority of the sql
server agent so trusted/non-trusted security doesn't
really apply, as windows logins are always authenticated.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
So are you saying , that even when i change the authentication mode to
Windows only , the jobs will still run even if they are owned by sa
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:170001c4e8d4$3eea74c0$a501280a@.phx.gbl...
> The reason sa is often suggested as the owner of
> replication jobs is that when the job runs, there is an
> active directory lookup performed of the job owner. This
> is the reason sa is used - no AD lookup required. The
> jobs themselves are run under the authority of the sql
> server agent so trusted/non-trusted security doesn't
> really apply, as windows logins are always authenticated.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Correct. The owner of the job is not the login used to
run it, as this is a cmdexec type of job and therefore
runs as the agent.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

replication job failure

Our SQl Server 2000 was rebooted recently but when I check the management
section then jobs replication its registered as failed yet when checking the
history it is still executing step 2.
Yet when I check in the replication monitor in the distribution agents
replication is as normal do you know how I can get rid of the fail status if
it is still processing transaction replication that has been running for 3
days on step 2?
thanks for any help
Sammy
Sammy,
you could try stopping and restarting the job, then refresh.
Rgds,
Paul Ibison
|||Thanks Paul it worked
"Paul Ibison" wrote:

> Sammy,
> you could try stopping and restarting the job, then refresh.
> Rgds,
> Paul Ibison
>
>

Replication Job Failed. Unable to determine the owner

A former employee at my organization created a replication job to back up our database. The developer has since left and his windows account was deleted. I'm now receiving this error:

SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-05 15:40:00 - Message: The job failed. Unable to determine if the owner (username) of job Replication agents checkup has server access (reason: Could not obtain information about Windows NT group/user 'username', error code 0x534. [SQLSTATE 42000] (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error 3621)).

How can I fix this? I looked under the Replication folder but didn't see anything.

In Object Explorer, look at the job in SQL Server Agent to see who owns it, and verify the account is valid.

|||That's for the help. I changed the owner but am now getting this error:

SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-07 01:00:00 - Message: The job failed. The Job was invoked by Schedule 175 (Replication agent schedule.). The last step to run was step 1 (Run agent.).

When I executed the maintenance plan manually it worked, but it doesn't seem to work on the schedule. I've never created a maintenance plans so I'm going to look up some more information to see if I can figure out what is going to wrong.

Replication Job Failed. Unable to determine the owner

A former employee at my organization created a replication job to back up our database. The developer has since left and his windows account was deleted. I'm now receiving this error:

How can I fix this? I looked under the Replication folder but didn't see anything.

In Object Explorer, look at the job in SQL Server Agent to see who owns it, and verify the account is valid.

|||That's for the help. I changed the owner but am now getting this error:

Replication job does not end - even when its idle on the server

I am the two stored procedures below, used in a similar way, to add a
subscription. But for some reason, the replication completes but it does not
stop. If I add a subscription using Enterprise manager (EM), the job does
stop. I scripted out the subscription that EM had created and noticed that
extra code had been added to create the replication jobs (ie. if you generate
the script for a job, there is an option to "script creation of replication
jobs"). Do I need to do this too?
Any help would be very much appreciated.
ServerName...../
use NewTest
GO
exec sp_addpullsubscription @.publisher = @.@.ServerName, @.publisher_db =
'pubs',
@.publication = 'pubs', @.independent_agent = 'true',
@.subscription_type = 'anonymous', @.update_mode = 'read only',
@.immediate_sync = 1
GO
exec sp_addpullsubscription_agent @.publisher = @.@.ServerName, @.publisher_db =
'pubs', @.publication = 'pubs', @.distributor = @.@.ServerName,
@.subscriber_security_mode = 1, @.distributor_security_mode = 1, @.use_ftp =
'true', @.publication_type = 1
GO
/..... End: Script to be run at Subscriber: @.@.ServerName ...../
What does the replication job which does not stop say?
Scripting replication jobs is not necessary unless you have customized them.
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
""Julian Reed via droptable.com"" <forum@.droptable.com> wrote in message
news:50DAB174F7810@.droptable.com...
> I am the two stored procedures below, used in a similar way, to add a
> subscription. But for some reason, the replication completes but it does
not
> stop. If I add a subscription using Enterprise manager (EM), the job does
> stop. I scripted out the subscription that EM had created and noticed
that
> extra code had been added to create the replication jobs (ie. if you
generate
> the script for a job, there is an option to "script creation of
replication
> jobs"). Do I need to do this too?
> Any help would be very much appreciated.
> ServerName...../
> use NewTest
> GO
> exec sp_addpullsubscription @.publisher = @.@.ServerName, @.publisher_db =
> 'pubs',
> @.publication = 'pubs', @.independent_agent = 'true',
> @.subscription_type = 'anonymous', @.update_mode = 'read only',
> @.immediate_sync = 1
> GO
> exec sp_addpullsubscription_agent @.publisher = @.@.ServerName, @.publisher_db
=
> 'pubs', @.publication = 'pubs', @.distributor = @.@.ServerName,
> @.subscriber_security_mode = 1, @.distributor_security_mode = 1, @.use_ftp =
> 'true', @.publication_type = 1
> GO
> /..... End: Script to be run at Subscriber: @.@.ServerName ...../

Replication Job Cleanup

Over the past couple of years, I have added & removed publications &
subscriptions, usung the wizards the come with SQL 2000. Recently we
had a problem with the dBs getting backed up and when I peered into the
SQL Server Agent->Jobs folder, there were many many more jobs than I
had publications & subscriptions, in fact some for tables that no
longer existed.
So my question is this. Is there a SP somewhere that will clean up all
the 'old' stuff without messing up all the stuff that is currently
working.
AHIA,
Larry...
No. For the most part these objects consume very little space and
replication won't reuse them or get confused by their existence.
This being said you can query sysmergearticles and get an idea of what is
currently in use on your publisher/subscriber. Again I would be adverse to
touching a production system in case I whack something - unless of course I
am a consultant as this might mean considerable overtime for me when things
go south.
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
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1130949038.398739.282220@.g44g2000cwa.googlegr oups.com...
> Over the past couple of years, I have added & removed publications &
> subscriptions, usung the wizards the come with SQL 2000. Recently we
> had a problem with the dBs getting backed up and when I peered into the
> SQL Server Agent->Jobs folder, there were many many more jobs than I
> had publications & subscriptions, in fact some for tables that no
> longer existed.
> So my question is this. Is there a SP somewhere that will clean up all
> the 'old' stuff without messing up all the stuff that is currently
> working.
> AHIA,
> Larry...
>
|||Hillary,
What are you saying? What are you implying? Would a consultant
really do that? Who me? Never!!!!
As always, thanks for your impartial advice!!!
Larry...

Replication Isues After upgrading subscriber to 2005

Hi There

A while ago i migrated a 2000 database to a new instance of sql server 2005 and succesffully setup replication from a 2000 publisher.

However to experiment i took an existing 2000 instance with a subscriber databases and upgraded the default instance to 2005. (Upgraded from 2000 Enterprise to 2005 Enterprise)

After the upgrade the setup logs were all successful, i also run upgrade advisor before and made sure there were no issues.

To see what happens i did not drop the subscription before upgrade (is this an absolute neccessity ?)

All i did was stop the distribution agent before upgrade, to see what would happen, i did not expect it to work.

But since the upgrade i cannot delete the subscription on the subscriber after upgrade, i also cannot create a new subscriptions on the upgraded subscriber.

I get the following error:

Sql Server error 207: column job_step_uid not found.

I found the following link :

http://support.microsoft.com/kb/914781/en-us

but it only refers to desktop editions and express, they refer to the msdb database not upgrading, but the upgrades logs are clear i see no evidence of an issue when upgrading msdb.

What exactly is going on? How can i delete the old subsciption and start creating new ones in the upgraded subscriber ?

I have read the Upgrading replicated DB's topic in BOL, no mention of having to drop subscription before upgrade although i suspect so, all it mentions scripting out the replication , changing the scripts , dropping the subscription (no mention of before or after upgrade), and re-creating them. (all of these i am unable to do due to the above error.)

Please assist, thanx

Ok i have since ound out that job_step_uid is a new column on the MSdistribution_agents table in the distribution database.

But i have not upgraded the distributor and i dont have to, as mentioned i have setup replication successfully with a 2005 database to a 2000 publicationa nd distributor without any issues, i have no idea why this time is seem to think the distributor is 2005 ?

So i am still stumped i know where it thinks this column should be, but no idea why i am getting this error all of a sudden, no where during subscription setup is the publisher or distributor required to be 2005?

ANyone ?

|||I lost track - what version is your publisher, distributor and subscriber? The supported option is that the version of the distributor has to be greater than or equal to the version of the publisher. For Merge replication, it goes one step further, where the version of the publisher has to be greater than or equal to the subscriber. There's more information about this in Books Online.|||

Hi Greg

I have consequently found out through a microsoft case that sp_vupgrade_replication and sp_vupgrade_repl_metadata procs may have to be run after upgrade.

Will postback if this resolves the issue.

Thanx

|||Running these 2 procs resolved the issue.|||

greetings.

i am having the same problem you were facing. i am trying to re-setup a publication, but it will fail with an error 207, invalid column name 'job_step_uid'.

i have installed service pack 2, and it didn't solve anything. i was able to run the first proc mentioned, the second proc however, didn't seem to work (the text was black, as opposed to the other proc which was highlighted in crimson).

any ideas, guys?

thanks.

Replication Isues After upgrading subscriber to 2005

Hi There

A while ago i migrated a 2000 database to a new instance of sql server 2005 and succesffully setup replication from a 2000 publisher.

However to experiment i took an existing 2000 instance with a subscriber databases and upgraded the default instance to 2005. (Upgraded from 2000 Enterprise to 2005 Enterprise)

After the upgrade the setup logs were all successful, i also run upgrade advisor before and made sure there were no issues.

To see what happens i did not drop the subscription before upgrade (is this an absolute neccessity ?)

All i did was stop the distribution agent before upgrade, to see what would happen, i did not expect it to work.

But since the upgrade i cannot delete the subscription on the subscriber after upgrade, i also cannot create a new subscriptions on the upgraded subscriber.

I get the following error:

Sql Server error 207: column job_step_uid not found.

I found the following link :

http://support.microsoft.com/kb/914781/en-us

but it only refers to desktop editions and express, they refer to the msdb database not upgrading, but the upgrades logs are clear i see no evidence of an issue when upgrading msdb.

What exactly is going on? How can i delete the old subsciption and start creating new ones in the upgraded subscriber ?

Please assist, thanx

Ok i have since ound out that job_step_uid is a new column on the MSdistribution_agents table in the distribution database.

ANyone ?

Hi Greg

I have consequently found out through a microsoft case that sp_vupgrade_replication and sp_vupgrade_repl_metadata procs may have to be run after upgrade.

Will postback if this resolves the issue.

Thanx

|||Running these 2 procs resolved the issue.|||

greetings.

i am having the same problem you were facing. i am trying to re-setup a publication, but it will fail with an error 207, invalid column name 'job_step_uid'.

any ideas, guys?

thanks.

Replication issues with multiple databases

I am planning to use replication from 400 databases to the master database on
a periodic basis. Do you see any issues with that ?
All databases have the same structure
Alu,
this is a bit vague as it stands

but certainly this is 'possible'. In
this link they discuss scaling merge to 2000 subscribers:
http://www.microsoft.com/technet/pro...mergperf.mspx.
For your setup, the type of replication selected will have some
implications. There are also implications with the type of topology
selected, hardware available, bandwidth, data volume etc so really you just
have to implement it, monitor using Perfmon and then see how it goes. As an
aid to avoid contention (data and disk) you might need to consider
staggering synchronization.
Regards,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication issues with MSDE and SQL Server Enterprise

Hello--
I'm am having difficulty setting up what I thought would
be something relatively simple to accomplish. I have two
client computers running XP, each using a local copy of
MSDE2000 to store data. I also have a server running
Windows 2000 AS and SQL Server Enterprise.
What I'm trying to do is have the data that's logged on
the client computers replicate to the server. I have run
into a variety of issues, most seem to be related to
security problems. I have all SQL Server instances set up
to use TCP/IP and named pipes, and all set for mixed mode
authentication. I am not using the server as a domain
controller, but I have created matching user accouts with
administrator priviliges on each of the three computers in
question.
When I create a publication on one of the two client
computers, sometimes a snaphot is generated immediately,
sometimes it isn't. When I try to create a pull
subscription on the server, I typically get an error about
being unable to connect to the distributor (I presume
security-releated problems).
I feel as if I'm missing something obvious, because this
seem like a very straightforward setup. What am I doing
wrong?
Thanks in advance for any help.
Chris Langston
exactly how are you connecting to your Publisher? ActiveX, SQM DMO?
If you are using ActiveX controls you have to define the network method you
are using to connect to your publisher/distributor by using
PublisherAddress/PublisherNetwork and DistributorAddress/DistributorNetwork.
If you are pulling a subscription using UNC you will have to ensure that the
SQL Server agent account on the subscriber has rights to the network share
on the publisher. The easiest way to do this is to make sure that the SQL
Server agent account the subscribers run under is the same one that it runs
under on the Publisher and this account is in the local admin group. If you
can't make them the same domain account, give them the same name and
password.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Chris Langston" <clangst@.vectorcorporation.com> wrote in message
news:512901c4807f$6260a7c0$a401280a@.phx.gbl...
> Hello--
> I'm am having difficulty setting up what I thought would
> be something relatively simple to accomplish. I have two
> client computers running XP, each using a local copy of
> MSDE2000 to store data. I also have a server running
> Windows 2000 AS and SQL Server Enterprise.
> What I'm trying to do is have the data that's logged on
> the client computers replicate to the server. I have run
> into a variety of issues, most seem to be related to
> security problems. I have all SQL Server instances set up
> to use TCP/IP and named pipes, and all set for mixed mode
> authentication. I am not using the server as a domain
> controller, but I have created matching user accouts with
> administrator priviliges on each of the three computers in
> question.
> When I create a publication on one of the two client
> computers, sometimes a snaphot is generated immediately,
> sometimes it isn't. When I try to create a pull
> subscription on the server, I typically get an error about
> being unable to connect to the distributor (I presume
> security-releated problems).
> I feel as if I'm missing something obvious, because this
> seem like a very straightforward setup. What am I doing
> wrong?
> Thanks in advance for any help.
> Chris Langston
>
>

Replication issues with failed logins

I just applied instcat.sql to my SQL Srvr 2k sp4. At first it broke my replication with some cursor errors. Applying the latest instcat.sql fixed the problem, however one of the distribution agents would not start (i'm not sure if instcat had anything to do with it) giving me a "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. The process could not connect to distributor 'DistributorName'. The step failed." error.

Any suggestions would be greatly appreciated!

Thanks!

For those who experience similar problems: I simply ran distribution agent at Distributor. That fixed the issue.

Replication issues upgrade to SQL 2005.

Hi Everyone:

I am not sure if I should be posting this question in the setup forum. I apologise if this is the wrong forum. My question is simple and straightforward.

1). What are the things that I should consider while upgrading Replication from SQL 2000 to SQL 2005 Assuming

Case A : My SQL Server 2000 is the Publisher.

CASE B: My SQL Server 2000 is the Distributor

CASE C : My SQL Server 2000 is the Subscriber.

Any documents, whitepapers or KBs or related posts would be helpful. MS SMEs please share your thoughts.

Thanks

You can start with reading SQL 2005 Books Online. Search for "replication upgrade". You should find topics "Upgrading Replicated Databases", as well as read upon what new features exist, and what features are deprecated. i.e. "Breaking Changes in SQL Server 2005 Replication" and "Behavior Changes in SQL 2005 Replication".

you can also access SQL 2005 at http://msdn2.microsoft.com.

Replication issues between SQL mobile and SQL2k?

I meant to cross-post this over here, but not having much response in SQLCE
forum ...
I'm in the process of a 'forced' upgrade (my client bought newer PocketPCs).
Soooo .. what I would like to know is whether there are any issues
connecting SQL Mobile to SQL 2000 for replication. Currently, replication
works "as advertised" between SQLCE and SQL2000 (enterprise).
The models seem quite symmetrical. I have not had any problems ...yet.
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
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:eQT3Y76BGHA.1032@.TK2MSFTNGP11.phx.gbl...
>I meant to cross-post this over here, but not having much response in SQLCE
>forum ...
> I'm in the process of a 'forced' upgrade (my client bought newer
> PocketPCs).
> Soooo .. what I would like to know is whether there are any issues
> connecting SQL Mobile to SQL 2000 for replication. Currently, replication
> works "as advertised" between SQLCE and SQL2000 (enterprise).
>
|||We're using this setup in a production environment and so far things work in
a similar fashion to our SQL CE to SQL 2000 replication. And...we get the
added benefit of background or async replication, which is very nice.
- will
"Earl" wrote:

> I meant to cross-post this over here, but not having much response in SQLCE
> forum ...
> I'm in the process of a 'forced' upgrade (my client bought newer PocketPCs).
> Soooo .. what I would like to know is whether there are any issues
> connecting SQL Mobile to SQL 2000 for replication. Currently, replication
> works "as advertised" between SQLCE and SQL2000 (enterprise).
>
>

Replication issues after a Database Restore - Unable to drop or create Transactional Repli

Hi,

I have transactional replication set up on on of our MS SQL 2000 (SP4)
Std Edition database server

Because of an unfortunate scenario, I had to restore one of the
publication databases. I scripted the replication module and dropped
the publication first. Then did a full restore.

When I try to set up the replication thru the script, it created the
publication with the following error message

Server: Msg 2714, Level 16, State 5, Procedure SYNC_FCR To
GPRPTS_GL00100, Line 1
There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in the
database.

It seems the previous replication has set up these system views
SYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replication
module again to see if it drops the views but it didn't.

The replication fails with some wired error & complains about this
views when I try to run the synch..

I even tried running the sp_removedbreplication to drop the
replication module, but the views do not seem to disappear.

My question is how do I remove these system views or how do I make the
replication work without using these views or create new views.. Why
is this creating those system views in the first place?

I would appreciate if anyone can help me fix this issue. Please feel
free to let me know if any additional information or scripts needed.

Thanks in advance..

Regards,
Aravin Rajendra.you should be able to drop them using query analyzer.

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

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
"Query Builder" <querybuilder@.gmail.comwrote in message
news:1189702889.303360.189580@.o80g2000hse.googlegr oups.com...

Quote:

Originally Posted by

Hi,
>
I have transactional replication set up on on of our MS SQL 2000 (SP4)
Std Edition database server
>
Because of an unfortunate scenario, I had to restore one of the
publication databases. I scripted the replication module and dropped
the publication first. Then did a full restore.
>
When I try to set up the replication thru the script, it created the
publication with the following error message
>
Server: Msg 2714, Level 16, State 5, Procedure SYNC_FCR To
GPRPTS_GL00100, Line 1
There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in the
database.
>
It seems the previous replication has set up these system views
SYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replication
module again to see if it drops the views but it didn't.
>
The replication fails with some wired error & complains about this
views when I try to run the synch..
>
I even tried running the sp_removedbreplication to drop the
replication module, but the views do not seem to disappear.
>
My question is how do I remove these system views or how do I make the
replication work without using these views or create new views.. Why
is this creating those system views in the first place?
>
I would appreciate if anyone can help me fix this issue. Please feel
free to let me know if any additional information or scripts needed.
>
Thanks in advance..
>
Regards,
Aravin Rajendra.
>

|||Thanks for your response.. I tried dropping it thru QA.. Now the
replication doesn't show up on the publication. But the replication
monitor still has this replication with a failed status....

Can you please point me to the direction on safely removing all
components of a particular replication module (I have other publishers
in this server)..

Thanks again..

Aravin Rajendar.

On Sep 13, 2:37 pm, "Hilary Cotter" <hilary.cot...@.gmail.comwrote:

Quote:

Originally Posted by

you should be able to drop them using query analyzer.
>
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
>
Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
>
Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com"Query Builder" <querybuil...@.gmail.comwrote in message
>
news:1189702889.303360.189580@.o80g2000hse.googlegr oups.com...
>

Quote:

Originally Posted by

Hi,

Quote:

Originally Posted by

I have transactional replication set up on on of our MS SQL 2000 (SP4)
Std Edition database server

Quote:

Originally Posted by

Because of an unfortunate scenario, I had to restore one of the
publication databases. I scripted the replication module and dropped
the publication first. Then did a full restore.

Quote:

Originally Posted by

When I try to set up the replication thru the script, it created the
publication with the following error message

Quote:

Originally Posted by

Server: Msg 2714, Level 16, State 5, Procedure SYNC_FCR To
GPRPTS_GL00100, Line 1
There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in the
database.

Quote:

Originally Posted by

It seems the previous replication has set up these system views
SYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replication
module again to see if it drops the views but it didn't.

Quote:

Originally Posted by

The replication fails with some wired error & complains about this
views when I try to run the synch..

Quote:

Originally Posted by

I even tried running the sp_removedbreplication to drop the
replication module, but the views do not seem to disappear.

Quote:

Originally Posted by

My question is how do I remove these system views or how do I make the
replication work without using these views or create new views.. Why
is this creating those system views in the first place?

Quote:

Originally Posted by

I would appreciate if anyone can help me fix this issue. Please feel
free to let me know if any additional information or scripts needed.

Quote:

Originally Posted by

Thanks in advance..

Quote:

Originally Posted by

Regards,
Aravin Rajendra.

Replication Issues

Hi,

I have created a publication in Microsoft SQL server 2005 and the publication credentials are used by an application targeted for a windows mobile 5.0 which using RDA pulls the data from the Master data file and creates a local symbol data file, the first part is working fine, i.e RDA pull from Sql Server 2005 to the SQL CE,

Now i am trying to add features where in the changes made by the application in the sdf in the mobile device are to be pushed back to the Master data file, for that i tried to use the RDA push command and for using the push command the primary constraint was the table shoule be tracked on when the data is pulled initially(i.e in the first RDA pull. tracking mode should be seton) but that has a setback for me, for when the tracking is enabled i am getting these columns

_sysIG bigint
_sysCG bigint
_sysCD datetime
_sysP1 varbinary(8000)
_sysMC varbinary(8000)
_sysMCS varbinary(8000)
_sysSR varbinary(8000)

as additional columns in my sdf file and these increase the size of my sdf file, is there any way by which i can stop them from replicating in the symbol data file without affecting the tracking option, for without the tracking option the columns cannot be pushed back to the MDF, can anyone give me insights on this?

Regards,

Venkatesh.M

These columns are required for the tracking mechanism to work. Please see this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=509110&SiteID=1|||

ErikEJ wrote:
These columns are required for the tracking mechanism to work. Please see this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=509110&SiteID=1

Thanks for the insight Erik.. i have solved the issue.. thanks

Replication Issues

Hello,
I am replicating databases from a sql2000 server with a
seperate distributer running sql2000 server and a MSDE subscriber. I
am using merge replication. The subscribers pull a subscription.
We want to have this setup across the internet for multiple
subscribers
each of whom might be updating as frequently as 1 hour. There are a
couple of issues I would like to find out about.
1.Security: I understood that the initial snapshots can be
published via ftp ( or any other means ofcourse). Can the merge
process be accomplished via ftp too? i.e The merge agent running on
the subscriber, writes to the ftp space reserved for it and the
publisher uses these files to bring the publisher up to speed and put
the updates back to all the subscribers. (sounds very slow). What are
our options as far as channel security if we are not using ftp ( and
is it possible in the first place across the internet).If we use a
secure ftp site, can the agents manage that?
2.Load: Our publisher has about 20 databases right now, with a
total of 1Gig file space occupied by mdf and log files. One database
is being replicated. Its consuming 1Gig of RAM Memory. Is that normal?
Is it because of the replication. How can I find out? Can anybody with
experience in this area, tell how much more load we can expect to
see? How much processing is needed for 40 users each updating about
500KB of data every one hour?
Thanks a lot,
Hananiel
1) I'm confused by what you are referring to by ftp. Are you talking about
the ftp port (21) or the ftp service. IE can the merge agent download the
commands using FTP? The answer is no, only the snapshot. If you are talking
about using port 21 the answer is yes. The merge agent will connect to the
publisher/distributor/subscriber using port 1433 or whatever port your SQL
Server is configured to run on, which could be port 21.
2) SQL Server will consume as much memory as is accessible on the machine or
whatever you configure SQL Server to consume using sp_configure 'max server
memory (MB)'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Hananiel" <hananiel@.yahoo.com> wrote in message
news:e338e321.0409170710.68893ce9@.posting.google.c om...
> Hello,
> I am replicating databases from a sql2000 server with a
> seperate distributer running sql2000 server and a MSDE subscriber. I
> am using merge replication. The subscribers pull a subscription.
> We want to have this setup across the internet for multiple
> subscribers
> each of whom might be updating as frequently as 1 hour. There are a
> couple of issues I would like to find out about.
> 1.Security: I understood that the initial snapshots can be
> published via ftp ( or any other means ofcourse). Can the merge
> process be accomplished via ftp too? i.e The merge agent running on
> the subscriber, writes to the ftp space reserved for it and the
> publisher uses these files to bring the publisher up to speed and put
> the updates back to all the subscribers. (sounds very slow). What are
> our options as far as channel security if we are not using ftp ( and
> is it possible in the first place across the internet).If we use a
> secure ftp site, can the agents manage that?
> 2.Load: Our publisher has about 20 databases right now, with a
> total of 1Gig file space occupied by mdf and log files. One database
> is being replicated. Its consuming 1Gig of RAM Memory. Is that normal?
> Is it because of the replication. How can I find out? Can anybody with
> experience in this area, tell how much more load we can expect to
> see? How much processing is needed for 40 users each updating about
> 500KB of data every one hour?
> Thanks a lot,
> Hananiel
|||Hilary Thanks!,
Does SqlServer natively support encryption of
communication between its remote merge agents and itself? Or should we use a
tool like secure shell to make an encrypted connection?
Thanks,
Hananiel
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eXjhIAOnEHA.644@.tk2msftngp13.phx.gbl...
> 1) I'm confused by what you are referring to by ftp. Are you talking about
> the ftp port (21) or the ftp service. IE can the merge agent download the
> commands using FTP? The answer is no, only the snapshot. If you are
talking
> about using port 21 the answer is yes. The merge agent will connect to the
> publisher/distributor/subscriber using port 1433 or whatever port your SQL
> Server is configured to run on, which could be port 21.
> 2) SQL Server will consume as much memory as is accessible on the machine
or
> whatever you configure SQL Server to consume using sp_configure 'max
server
> memory (MB)'
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Hananiel" <hananiel@.yahoo.com> wrote in message
> news:e338e321.0409170710.68893ce9@.posting.google.c om...
>

Replication issues

Hi All ,
I have some concerns with replication
1. if the replication fails 1/2 way , does that mean some data is being
replicated across alrdy or it'll do a roll-back to ensure either it's a
complete replication or no replication ?
2. previously i have already set up the application but in EM , i went to
Replication --> Publications and delete the publication instead of going to
the Replication Monitor --> Publishers --> to delete the publication and
found that i couldn't delete the publication in Replication Monitor -->
Publishers any more
which sp can i used to delete ?
3. i got the error from replication "the subscription has been marked and
must be reintialized . No Sync subscriptions will need to be dropped and
recreated?
- why this error occured , i have set for replication for 72 hours
Kindly advise
tks & rdgs1) this depends. If there is a problem deploying the snapshot, it will be
reapplied, but not rolled back. So if you don't reapply the snapshot after
failure your subscriber database will have some of the replicated objects
and replication metadata in place. If the merge or distribution agent fails
midway it depends on the transactional boundary. Transactional replication
replicates transactions transactionally. So if a transaction with 200
commands (for instance a transaction which updates 200 rows) fails, it will
be completely rolled back. If you are replicating a transaction which causes
a cascading update/delete on the publisher and you have enforced this
cascade for replication, and this transaction fails, it will be rolled back.
For merge replication, if a child record is applied before the corresponding
parent record and the parent is not part of the batch, the agent will fail
and this row will be rolled back, but the successfully applied rows in the
batch will remain. Next time you run the merge agent, this transaction
should succeed if the parent record comes over in the next batch. Merge
replication does not guarantee durability.
2) try sp_droppublication 'publicationname' in the publication database.
3) You should set your history retention to the same value of your
transaction retention (right click on replication monitor, select
distribution properties, and click on the properties button, and set it
there).
--
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
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:6A1D3EAE-EE3A-4824-8A97-ACFF7521CEF5@.microsoft.com...
> Hi All ,
> I have some concerns with replication
> 1. if the replication fails 1/2 way , does that mean some data is being
> replicated across alrdy or it'll do a roll-back to ensure either it's a
> complete replication or no replication ?
> 2. previously i have already set up the application but in EM , i went to
> Replication --> Publications and delete the publication instead of going
to
> the Replication Monitor --> Publishers --> to delete the publication and
> found that i couldn't delete the publication in Replication Monitor -->
> Publishers any more
> which sp can i used to delete ?
> 3. i got the error from replication "the subscription has been marked and
> must be reintialized . No Sync subscriptions will need to be dropped and
> recreated?
> - why this error occured , i have set for replication for 72 hours
>
> Kindly advise
> tks & rdgs|||Hi,
I have tried sp_droppublication on the publication db but there's no such
publication to be dropped
when i tried deleting from the replication monitor i got the following
error :
SQL server Enterprise Manager could not retrieve information about
publication 'publication1'
Error 21776 the name 'publication1' was not found in the TransPublication
collection. if the name is a qualified name use [] to seperate various parts
of the name and try again
how could i resove this ?
kindly advise
tks & rdgs
"Hilary Cotter" wrote:
> 1) this depends. If there is a problem deploying the snapshot, it will be
> reapplied, but not rolled back. So if you don't reapply the snapshot after
> failure your subscriber database will have some of the replicated objects
> and replication metadata in place. If the merge or distribution agent fails
> midway it depends on the transactional boundary. Transactional replication
> replicates transactions transactionally. So if a transaction with 200
> commands (for instance a transaction which updates 200 rows) fails, it will
> be completely rolled back. If you are replicating a transaction which causes
> a cascading update/delete on the publisher and you have enforced this
> cascade for replication, and this transaction fails, it will be rolled back.
> For merge replication, if a child record is applied before the corresponding
> parent record and the parent is not part of the batch, the agent will fail
> and this row will be rolled back, but the successfully applied rows in the
> batch will remain. Next time you run the merge agent, this transaction
> should succeed if the parent record comes over in the next batch. Merge
> replication does not guarantee durability.
> 2) try sp_droppublication 'publicationname' in the publication database.
> 3) You should set your history retention to the same value of your
> transaction retention (right click on replication monitor, select
> distribution properties, and click on the properties button, and set it
> there).
> --
> 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
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:6A1D3EAE-EE3A-4824-8A97-ACFF7521CEF5@.microsoft.com...
> > Hi All ,
> >
> > I have some concerns with replication
> >
> > 1. if the replication fails 1/2 way , does that mean some data is being
> > replicated across alrdy or it'll do a roll-back to ensure either it's a
> > complete replication or no replication ?
> >
> > 2. previously i have already set up the application but in EM , i went to
> > Replication --> Publications and delete the publication instead of going
> to
> > the Replication Monitor --> Publishers --> to delete the publication and
> > found that i couldn't delete the publication in Replication Monitor -->
> > Publishers any more
> > which sp can i used to delete ?
> >
> > 3. i got the error from replication "the subscription has been marked and
> > must be reintialized . No Sync subscriptions will need to be dropped and
> > recreated?
> > - why this error occured , i have set for replication for 72 hours
> >
> >
> > Kindly advise
> > tks & rdgs
>
>

Saturday, February 25, 2012

Blog Archive

About Me