fix merge replication?

I had merge replication setup between 2 servers. I then stopped and
removed replication, made some system changes, then setup replication
again.
But, it turns out all of the data from the publisher hadn't made it to
the subscriber before I removed replication.
Is there a command I can use on the publisher that tells it to look at
all tables and make sure the data between the two machines is
correct/identical. I know I can do a sp_mergedummyupdate, but that
requires I look at all tables and issue the command for each row in
question. I want the system to do it so it can get everything. I don't
want to do the reinitialize because that would take quite a while (the
data is about 1 gig over the internet transfer would be a day or so).
Any other suggestions?
TIA
Darin
*** Sent via Developersdex http://www.codecomments.com ***
Darin,
you could drop the subscription, use redgate's datacompare to synchronize
the data then add the subscriber as a nosync one.
Alternatively you could try sp_addtabletocontents.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I don't know if I did this correctly. I have a table on the distributor
that has 99000 records, on the subscriber there are only 98000. I did:
exec sp_addtabletocontents 'GLDistribution'
It sat for a while and then said it was successfull. But, the Enterprise
manager still says there is no data to merge, and the subscriber still
only has 98000 records.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||Darin,
I'd use a linked server to join the 2 tables based on guid. Make it a Left
Outer Join so you can find the publisher records not on the subscriber. As
there are only 1000 of these, you could then do a dummy update on each one
(use a cursor, or have query analyser create 1000 proc calls and run the
resulting script).
This still leaves the worrying issue of how the records got there in the
first place without firing the merge triggers. Check for bulk inserts or fast
loads in DTS which are the normal culprits.
Cheers,
Paul Ibison, SQL Server MVP
"Darin" wrote:

> I don't know if I did this correctly. I have a table on the distributor
> that has 99000 records, on the subscriber there are only 98000. I did:
> exec sp_addtabletocontents 'GLDistribution'
> It sat for a while and then said it was successfull. But, the Enterprise
> manager still says there is no data to merge, and the subscriber still
> only has 98000 records.
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>

FIRST REPLICATION

Hi all,
I've 2 servers with 2 db that must have the same data...
I'm studing how to make replication, but is very difficult
for a novice.
The connection between the servers is 24h.
There some good book with samples step by step (for
dummies)?
thanks for any idea
dipic
What type of replication r u looking for ? Whether one would be your live database and the other would be just for backup , is that the case then you can got for Transactional replication where incremenatal data would be copied on to other server
|||Dipic,
there aren't any books particular to sql server replication, although I have
heard there will be two volumes coming out in the near future...
For now, I'd use books-on-line as your main resource, and there is a lot of
useful information there.
You have to consider if the subscribers can change the data and the degree
of latency allowed/accepted. This will narrow down your choices. BTW,
replication is not the same as database mirroring (see SQL 2005), so there
will always be some latency involved.
Post up in this group as much as you can - there are plenty of people here
with a lot of experience, and this will speed up your learning.
HTH,
Paul Ibison
|||http://www.mssqlserver.com/replication
When you set this up, do everything on a single machine. Why? The two
things that cause the greatest problems with replication are security and
connectivity. You rule both out on a single machine and can spend your time
getting comfortable with replication before you move to a multi-machine
environment.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||Both dbase are alive... people work on the first and on
the second server, and all must have the same data every
12h ca.

>--Original Message--
>What type of replication r u looking for ? Whether one
would be your live database and the other would be just
for backup , is that the case then you can got for
Transactional replication where incremenatal data would be
copied on to other server
>.
>
|||I've both the dbase alive (people working on), and the
data must be replicated from server1 to server2 and vice
versa, every 12h ca... but I'm totally novice and I don't
know what I must do... I'm searching some example, a
suggestion or a guide...
thanks for your reply

>--Original Message--
>http://www.mssqlserver.com/replication
>When you set this up, do everything on a single machine.
Why? The two
>things that cause the greatest problems with replication
are security and
>connectivity. You rule both out on a single machine and
can spend your time
>getting comfortable with replication before you move to a
multi-machine
>environment.
>--
>Mike
>Principal Mentor
>Solid Quality Learning
>"More than just Training"
>SQL Server MVP
>http://www.solidqualitylearning.com
>http://www.mssqlserver.com
>
>.
>
|||http://www.mssqlserver.com/replication
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

firewalls? port numbers? ancient curses cast upon my servers?

Hello All,
Hopefully someone has come across this...

I have the client side of my application installed in the US,
with the application and the database servers running in london.

The program language is C#, all built in .net, with the .net installer.
When the user in the US runs the program and it gets to the
import progress part (background processing occurring on London servers),
they are getting no feedback as to the progress of the import.
ie, nothing is being sent to the US from the london server.
But everything runs smooth the other way, ie, tables are written to
the sql db's in london etc... And I get data sending and receiving
here in london when i run the client app on my machine and send to
the servers here, so its some problem with the connection with the US....
firewalls? port numbers? ancient curses cast upon my servers?

Cheers mike

Is this using SQL Server Integration Services (the SQL Server 2005 replacement for DTS)?
(In any case, if the "import" part isn't giving feedback, you probably should investigate the "import" part, to see what it does, and revise it to give feedback -- it may be hard for anyone here to know what this "import" part is -- if you suspect a connection problem, network sniffing, or even simple use of sysinternals tcpview may be helpful.)

firewalls? port numbers? ancient curses cast upon my servers?

Hello All
I have the client side of my application installed in the US, with the
application and the database servers running in london.
The program language is C#, all built in .net, with the .net installer. When
the user in the US runs the program and it gets to the import progress part
(background processing occurring on London servers), they are getting no
feedback as to the progress of the import. ie, nothing is being sent to the
US from the london server. But everything runs smooth the other way, ie,
tables are written to the sql db's in london etc... And I get data sending
and receiving here in london when i run the client app on my machine and send
to the servers here, so its some problem with the connection with the US...
firewalls' port numbers' ancient curses cast upon my servers' anyone come
across anything like this?
Cheers mikeHave you tested access with Query Analyzer to see if you can connect, access
the database from both places and perform the import tasks? It's unclear
from your post whether you're just having problems with the import task or
if it's even connecting.
joe.
"blomm via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:54B0800E732D8@.SQLMonster.com...
> Hello All
> I have the client side of my application installed in the US, with the
> application and the database servers running in london.
> The program language is C#, all built in .net, with the .net installer.
> When
> the user in the US runs the program and it gets to the import progress
> part
> (background processing occurring on London servers), they are getting no
> feedback as to the progress of the import. ie, nothing is being sent to
> the
> US from the london server. But everything runs smooth the other way, ie,
> tables are written to the sql db's in london etc... And I get data
> sending
> and receiving here in london when i run the client app on my machine and
> send
> to the servers here, so its some problem with the connection with the
> US...
> firewalls' port numbers' ancient curses cast upon my servers' anyone
> come
> across anything like this?
> Cheers mike|||"It's unclear
from your post whether you're just having problems with the import task or
if it's even connecting."
Sorry, i will try and clarify:
it is connecting, theres problems with the callback functionality i think, if
that means anything to you.
okay, thanks for your pointers, i'm off to follow them up.
m

Firewall in Replication

Hi,
We are using SQL Server 2000. We need to setup merge replication between
server A & B using TCP/IP.
These servers are behind a firewall. The connection
between these servers can be done only using IP (class C)
How to configure this.
rgds,
Soura
Basically with SQL 2000 you need to allow inbound connections on port 1433
and 21 from the device doing the pull. Download the snapshot using ftp. If
this is not possible upgrade to SQL 2005 and do web synchronizations.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:134C38E0-CAAF-44C6-AD2B-1D525DB5BB0D@.microsoft.com...
> Hi,
> We are using SQL Server 2000. We need to setup merge replication between
> server A & B using TCP/IP.
> These servers are behind a firewall. The connection
> between these servers can be done only using IP (class C)
> How to configure this.
> rgds,
> Soura
>
>