Replication failed

Hi,
We are using transactional replication and it failed and
showing following error
Error:
The process could not bulk copy into table 'TableName'.
Error Number:
22001
Category:ODBC
Source: ODBC
Full Message:
String data, right truncation
Is any one having solution for this?
Regards,
Manoj
Manoj,
can you check if the schemas are identical on publisher and subscriber if
you are doing a nosync initialization.
If you are sending over the table schema, can you ensure that you take the
collation.
Regards,
Paul Ibison

replication error while copy data

Hi,
I have a transactional replication between SQL Server and Oracle. We already have the schema exist in both databases. So the the snapshut I check the 'If the table exists, leave it unchanged' box. But when the data start to load for the intial snapshut, I
got an error saying' The process encountered invalid column data in bcp file ...' for an existing table. How can me trace down which column has error? What is the data type for the Rowguid in my subscriber ( I do not have a rowguid column setup in the su
bscriber)?
Thanks
Hong,
was this error encountered when creating the snapshot file or when
distributing it to Oracle?
You can get some more (hopefully useful) info by logging:
http://support.microsoft.com/?id=312292
HTH,
Paul Ibison
|||It is encountered when distributing it to Oracle.
Hong Wang
"Paul Ibison" wrote:

> Hong,
> was this error encountered when creating the snapshot file or when
> distributing it to Oracle?
> You can get some more (hopefully useful) info by logging:
> http://support.microsoft.com/?id=312292
> HTH,
> Paul Ibison
>
>
|||OK, then try the logging I mentioned but I had hoped that it was a snapshot
agent error, as this is almost certainly an Oracle issue - mapping of
datatypes etc. Anyway, let's see if the logging returns anything.
Regards,
Paul Ibison
sql

replication error - agent is suspect

Hi,
I have set up a replication and it was doing the bulk copy from SrvA to
SrvB when it says "The agent is suspect as there's no response for the last
10 mins" or something like that ?
what could be the problem here ?
however, after i refresh it , it keeps running though but i am unsure if the
data has been successfully replicated over as the processing's running
appreciate any advise
tks & rdgs
Hi,
See the previous posts:-
http://groups.google.co.in/group/mic...36c788aeacadb7
Thanks
Hari
SQL Server MVP
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:13D1D8DF-E095-4F6C-9CAB-06D63015A95D@.microsoft.com...
> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the
> last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if
> the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs
|||Hi ,
I have managed to resolve this issue by increasing the default 10 mins of
agent inactivity
tks & rdgs
"maxzsim" wrote:

> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs

replication error - agent is suspect

Hi,
I have set up a replication and it was doing the bulk copy from SrvA to
SrvB when it says "The agent is suspect as there's no response for the last
10 mins" or something like that ?
what could be the problem here ?
however, after i refresh it , it keeps running though but i am unsure if the
data has been successfully replicated over as the processing's running
appreciate any advise
tks & rdgsHi,
See the previous posts:-
http://groups.google.co.in/group/mi...936c788aeacadb7
Thanks
Hari
SQL Server MVP
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:13D1D8DF-E095-4F6C-9CAB-06D63015A95D@.microsoft.com...
> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the
> last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if
> the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs|||Hi ,
I have managed to resolve this issue by increasing the default 10 mins of
agent inactivity
tks & rdgs
"maxzsim" wrote:

> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the las
t
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if t
he
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs

replication error - agent is suspect

Hi,
I have set up a replication and it was doing the bulk copy from SrvA to
SrvB when it says "The agent is suspect as there's no response for the last
10 mins" or something like that ?
what could be the problem here ?
however, after i refresh it , it keeps running though but i am unsure if the
data has been successfully replicated over as the processing's running
appreciate any advise
tks & rdgsHi,
See the previous posts:-
http://groups.google.co.in/group/microsoft.public.sqlserver.replication/browse_thread/thread/45cba0e7e1543879/7936c788aeacadb7?q=replication+agent+is+suspect&rnum=2&hl=en#7936c788aeacadb7
Thanks
Hari
SQL Server MVP
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:13D1D8DF-E095-4F6C-9CAB-06D63015A95D@.microsoft.com...
> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the
> last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if
> the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs|||Hi ,
I have managed to resolve this issue by increasing the default 10 mins of
agent inactivity
tks & rdgs
"maxzsim" wrote:
> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs

Replication Error

I have a copy of a database "db_A" called "db_copy". When I try to alter
tables in the database, it complains that it is being used for replication.
It is not being used for replication, but the database that it was copied
from is.
Is there anything I can do to allow us to alter this database's tables?
Thanks
Sean
Sean,
there is a stored procedure to do this called sp_MSunmarkreplinfo which
takes a tablename as a parameter. Alternatively, setting replinfo to 0 in
sysobjects for the particular table should do it. Finally, running
sp_removedbreplication can be used to remove all traces of replication in
the database.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

Replication between SQL and Access97?

I have an Access 97 database that I would like to "mirror" in my SQL server 2000 database.

Basically I would like SQL server to keep a current copy of an Access 97 database table which exists on remote machine on our network. Any time there is a change made to the Access table, I would like the SQL server to be updated automatically.

Is this something that is possible to do with replication/synchronization, or do I have to push the data up with another app?

ThanksTo my knowledge you can not set up relication from Access to SQL Server. Are you sure your tables are in Access? Or are you using an Access Data Project or tables linked into a mdb file?

If your tables are truly located locally in your access database the only way I can think of doing what you want to do is to link in your SQL Server tables and for every insert, update and delete you run the same queries against the SQL tables at the same time.

Why not just move your tables in your access application to SQL Server?|||The tables are definately in an Access 97.

I thought about moving the tables into the SQL database but I really need a copy locally in the event of a network failure. (The app which generates the data and fills the tables runs on the machine remote to the SQL database.)

Thanks for your suggestions.|||move the tables to sql. and then you can have DTS packages that push them down to your local access app.

Is'nt your SQL Server running backups on itself anyways?|||Depending on why you want to do this, you could
1)put a copy of sql server on the remote server and then use those tables in your access app. Replication to the other server is then easy if you still want this.
2)use dts packages to copy the data into your sql server tables using a scheduled job.
3)use heterogenous transactional replication but it looks a little complicated at first sight and I know nothing of the implications and practicality of implementing this type of replication|||I clearly need to bone this. I did find some info in the SQL Server Books Online under "Access Subscribers" which looks promising.

I believe this is item 3 refered to in the previous post.

Thanks for your help.sql

replication and lots of questions

I keep going in circles on this...
We are trying to scale our system out. We want to have a
copy of our database available on each of our servers.
One server acts as a load machine, the rest answer IIS
requests hitting their local SQL database. Client
requests are forwarded based off network load balancing.
Updates are not frequently made to the database, but they
do happen on occasion. These updates would be made on one
of the servers servicing the requests from the client
(could be any of say 5 servers). I need this change to
be updated immediately on all other servers services
client requests.
So how do I do this? I can setup triggers. A trigger
fire whenever an update is made to the database, updating
the data in all the coresponding tables on the other
servers. Does this lead to an infinite loop, where this
trigger, triggers the same trigger on another machine,
triggering the same update back?
Transactional Replication? Can you have each server be a
publisher and subscriber. Will there be the same problem,
with one replication triggering the other to replicate.
I could use an instead of trigger to make the changes on
a 'Master' server, that will then replicate the changes to
the rest of the servers. Could be the same problem
though?
Merge Replication... I could do this, but less frequently,
and updates would not be replicated very often.
Has anyone ever done this. Are there any better options.
I am rather new to sql server.
-Jackjackb
What is a size of your database?
Have you tried snapshot replication?
<jackb@.qsi.xxx> wrote in message
news:0b0a01c344b7$57c81460$a001280a@.phx.gbl...
> I keep going in circles on this...
> We are trying to scale our system out. We want to have a
> copy of our database available on each of our servers.
> One server acts as a load machine, the rest answer IIS
> requests hitting their local SQL database. Client
> requests are forwarded based off network load balancing.
> Updates are not frequently made to the database, but they
> do happen on occasion. These updates would be made on one
> of the servers servicing the requests from the client
> (could be any of say 5 servers). I need this change to
> be updated immediately on all other servers services
> client requests.
> So how do I do this? I can setup triggers. A trigger
> fire whenever an update is made to the database, updating
> the data in all the coresponding tables on the other
> servers. Does this lead to an infinite loop, where this
> trigger, triggers the same trigger on another machine,
> triggering the same update back?
> Transactional Replication? Can you have each server be a
> publisher and subscriber. Will there be the same problem,
> with one replication triggering the other to replicate.
> I could use an instead of trigger to make the changes on
> a 'Master' server, that will then replicate the changes to
> the rest of the servers. Could be the same problem
> though?
> Merge Replication... I could do this, but less frequently,
> and updates would not be replicated very often.
> Has anyone ever done this. Are there any better options.
> I am rather new to sql server.
> -Jack|||Writing a distributed transaction in a trigger might be a problem, because
if one server is down, updates will NOT be allowed on any server...
You might try transactional replication with queued updating subscribers...
That will give you near real time updates, but if the publisher server is
down, NO replication will occur, so you need to make sure you have good
uptime on that particular box..
<jackb@.qsi.xxx> wrote in message
news:0b0a01c344b7$57c81460$a001280a@.phx.gbl...
> I keep going in circles on this...
> We are trying to scale our system out. We want to have a
> copy of our database available on each of our servers.
> One server acts as a load machine, the rest answer IIS
> requests hitting their local SQL database. Client
> requests are forwarded based off network load balancing.
> Updates are not frequently made to the database, but they
> do happen on occasion. These updates would be made on one
> of the servers servicing the requests from the client
> (could be any of say 5 servers). I need this change to
> be updated immediately on all other servers services
> client requests.
> So how do I do this? I can setup triggers. A trigger
> fire whenever an update is made to the database, updating
> the data in all the coresponding tables on the other
> servers. Does this lead to an infinite loop, where this
> trigger, triggers the same trigger on another machine,
> triggering the same update back?
> Transactional Replication? Can you have each server be a
> publisher and subscriber. Will there be the same problem,
> with one replication triggering the other to replicate.
> I could use an instead of trigger to make the changes on
> a 'Master' server, that will then replicate the changes to
> the rest of the servers. Could be the same problem
> though?
> Merge Replication... I could do this, but less frequently,
> and updates would not be replicated very often.
> Has anyone ever done this. Are there any better options.
> I am rather new to sql server.
> -Jack|||about 50GB, so snapshot will not work so well
>--Original Message--
>jackb
>What is a size of your database?
>Have you tried snapshot replication?
><jackb@.qsi.xxx> wrote in message
>news:0b0a01c344b7$57c81460$a001280a@.phx.gbl...
>> I keep going in circles on this...
>> We are trying to scale our system out. We want to have
a
>> copy of our database available on each of our servers.
>> One server acts as a load machine, the rest answer IIS
>> requests hitting their local SQL database. Client
>> requests are forwarded based off network load balancing.
>> Updates are not frequently made to the database, but
they
>> do happen on occasion. These updates would be made on
one
>> of the servers servicing the requests from the client
>> (could be any of say 5 servers). I need this change to
>> be updated immediately on all other servers services
>> client requests.
>> So how do I do this? I can setup triggers. A trigger
>> fire whenever an update is made to the database,
updating
>> the data in all the coresponding tables on the other
>> servers. Does this lead to an infinite loop, where this
>> trigger, triggers the same trigger on another machine,
>> triggering the same update back?
>> Transactional Replication? Can you have each server be
a
>> publisher and subscriber. Will there be the same
problem,
>> with one replication triggering the other to replicate.
>> I could use an instead of trigger to make the changes on
>> a 'Master' server, that will then replicate the changes
to
>> the rest of the servers. Could be the same problem
>> though?
>> Merge Replication... I could do this, but less
frequently,
>> and updates would not be replicated very often.
>> Has anyone ever done this. Are there any better
options.
>> I am rather new to sql server.
>> -Jack
>
>.
>

replication and data move

Hi,
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
--
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

replication and data move

Hi,
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin
> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

replication and data move

Hi,
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
--
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

REplication and BLOB tables

Anyone ever see this error:
The process could not bulk copy into table '"JobApplBlob200501"'.
Expected the text length in data stream for bulk copy of text, ntext, or
image data.
(Source: ELMER (Data source); Error number: 4813)
Elmer is the Subscribing system.
The only odd thing I can see is the publisher and subscriber are build 922.
The distribution host server is build 818. I have other BLOB fields going
from the same publisher to the same subscriber through the same distributor.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
Is this transactional replication ? Is this error during initial snapshot or
during intial load on the subscribers. I have included the replication group
'cos you have some experts in there like Hilary and Paul who can help
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:e20gvdqAFHA.2584@.TK2MSFTNGP09.phx.gbl...
> Anyone ever see this error:
>
> The process could not bulk copy into table '"JobApplBlob200501"'.
> Expected the text length in data stream for bulk copy of text, ntext, or
> image data.
> (Source: ELMER (Data source); Error number: 4813)
>
> Elmer is the Subscribing system.
> The only odd thing I can see is the publisher and subscriber are build
922.
> The distribution host server is build 818. I have other BLOB fields going
> from the same publisher to the same subscriber through the same
distributor.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
>

REplication and BLOB tables

Anyone ever see this error:
The process could not bulk copy into table '"JobApplBlob200501"'.
Expected the text length in data stream for bulk copy of text, ntext, or
image data.
(Source: ELMER (Data source); Error number: 4813)
Elmer is the Subscribing system.
The only odd thing I can see is the publisher and subscriber are build 922.
The distribution host server is build 818. I have other BLOB fields going
from the same publisher to the same subscriber through the same distributor.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.orgIs this transactional replication ? Is this error during initial snapshot or
during intial load on the subscribers. I have included the replication group
'cos you have some experts in there like Hilary and Paul who can help
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:e20gvdqAFHA.2584@.TK2MSFTNGP09.phx.gbl...
> Anyone ever see this error:
>
> The process could not bulk copy into table '"JobApplBlob200501"'.
> Expected the text length in data stream for bulk copy of text, ntext, or
> image data.
> (Source: ELMER (Data source); Error number: 4813)
>
> Elmer is the Subscribing system.
> The only odd thing I can see is the publisher and subscriber are build
922.
> The distribution host server is build 818. I have other BLOB fields going
> from the same publisher to the same subscriber through the same
distributor.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
>

REplication and BLOB tables

Anyone ever see this error:
The process could not bulk copy into table '"JobApplBlob200501"'.
Expected the text length in data stream for bulk copy of text, ntext, or
image data.
(Source: ELMER (Data source); Error number: 4813)
Elmer is the Subscribing system.
The only odd thing I can see is the publisher and subscriber are build 922.
The distribution host server is build 818. I have other BLOB fields going
from the same publisher to the same subscriber through the same distributor.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.orgIs this transactional replication ? Is this error during initial snapshot or
during intial load on the subscribers. I have included the replication group
'cos you have some experts in there like Hilary and Paul who can help
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:e20gvdqAFHA.2584@.TK2MSFTNGP09.phx.gbl...
> Anyone ever see this error:
>
> The process could not bulk copy into table '"JobApplBlob200501"'.
> Expected the text length in data stream for bulk copy of text, ntext, or
> image data.
> (Source: ELMER (Data source); Error number: 4813)
>
> Elmer is the Subscribing system.
> The only odd thing I can see is the publisher and subscriber are build
922.
> The distribution host server is build 818. I have other BLOB fields going
> from the same publisher to the same subscriber through the same
distributor.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
>

replication & log shipping

Has anyone tried to do replication or log shipping on the same server? The
reason being I need a replica copy to server the reporting service so that
heavy loaded queries won't impact the online processing.
Thanks for any advice.
Joseph,
I regularly set up replication on the same server for testing purposes and
have not had any problems. If you haven't yet seen it, have a look at the
article here which describes the pros and cons of log shipping and
transactional replication for setting up a reporting server:
http://www.replicationanswers.com/Standby.asp
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication - general question

I have a database that I need to have replicated to another server - the server I need it replicated too already has a copy of the database. Is it possible to set up a replication and when replicating - keep it from the copy that is there? The copy that is there has a column that isn't set up on the main one.

Thanks!

Absolutely. You can specify which articles you want to replicate, and for tables, down to the columns.

Replication

I need to copy 10 Databases (150GB) to another SQL machine.
Now I need the destination machine to be updated every 24 hours.
Transcational replication is not helping me - cause it doesn't copy tables
without primary keys.
Snapshot replication is not helping me either - cause i can't transfer every
24 hours 150GB.
Help me please,
Aviad Avi.
You can use merge and configure it to only move the data one way. Add the
ExchangeType parameter to the merge agent with a value of 2.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||It seems you on something.
Can you please explain what do you meen by adding the ExchangeType parameter
with a value of 2?
Where should i configure the Merge?
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:QQXX4wl1EHA.768@.cpmsftngxa10.phx.gbl...
> You can use merge and configure it to only move the data one way. Add the
> ExchangeType parameter to the merge agent with a value of 2.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||Why does it called merge? because the uniqueidentifier colum that is added?
"Aviad Avi" <aviad00001@.yahoo.ca> wrote in message
news:%23RWGK1l1EHA.304@.TK2MSFTNGP11.phx.gbl...
> It seems you on something.
> Can you please explain what do you meen by adding the ExchangeType
parameter[vbcol=seagreen]
> with a value of 2?
> Where should i configure the Merge?
> "Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
> news:QQXX4wl1EHA.768@.cpmsftngxa10.phx.gbl...
the[vbcol=seagreen]
rights.
>
|||Moreover,
I think I need to run it with 1 value = push
don't I?
"Aviad Avi" <aviad00001@.yahoo.ca> wrote in message
news:%23RWGK1l1EHA.304@.TK2MSFTNGP11.phx.gbl...
> It seems you on something.
> Can you please explain what do you meen by adding the ExchangeType
parameter[vbcol=seagreen]
> with a value of 2?
> Where should i configure the Merge?
> "Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
> news:QQXX4wl1EHA.768@.cpmsftngxa10.phx.gbl...
the[vbcol=seagreen]
rights.
>
|||In the merge agent job, on the middle step, add -
ExchangeType 2 to the parameters list. This is one of
those cases where the parameter needs adding here rather
than to the profile. The values according to BOL are :
UPLOAD 1 Only merge Subscriber changes with the
Publisher.
DOWNLOAD 2 Only merge Publisher changes with the
Subscriber.
BIDIRECTIONAL 3 Merge all changes between the Publisher
and Subscriber (default).
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Snapshot and Transactional in their plain forms are
essentially unidirectional. Merge is bidirectional, and
the subscriber can change data offline, so there is the
potential that data can conflict. However, in certain
configurations a change to a different column on the same
row is not treated as a conflict and the changes
are 'merged'.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)