replication SQLServer 2-way

We have 2 SQLServer-databases with the same table in it. In both databases the table can be updated by users.
Is is possible to replicate the updates in this table from the one database to the other and vice versa? We want to use transactional-replication.You can setup an updatable transactional replication. To do that, specify 'true' to the paramenter @.allow_sync_tran when you execute sp_addpublication. And @.update_mode = 'sync tran' when you execute sp_addsubscription.|||Just out of curiousity, why can't he use merge replication instead?
I'm still learning from this replication thing...is there any reasons for chosing transactional against merge for this purpose?|||My personal experience in both merge and updatable transactional is that merge is slower, and it take a lot more to setup and manage. You can treat updatable transactional just like the regular transactional replication with a couple of more parameters to setup. There are other minor reasons but the main thing is the simplicity and better performance of transactional replication.

Hope this helps.|||joejcheng,

We tried the solution you provided and it works fine now. Thank you for your information.

Replication problem...

Hi friends,
I have a problem with my Sql Server (Win2k Server, Sql Server SP3 updated)
replication. My replication stopped with "The process could not bulk copy
out of table '[dbo].[syncobj_...." message. What is wrong? Could anybody
help me?
Arda Han
Software Engineer
try to open up your sync object in EM and view all the rows.
"Arda Han" <arda@.han.com> wrote in message
news:unW6VnQMEHA.1032@.tk2msftngp13.phx.gbl...
> Hi friends,
> I have a problem with my Sql Server (Win2k Server, Sql Server SP3 updated)
> replication. My replication stopped with "The process could not bulk copy
> out of table '[dbo].[syncobj_...." message. What is wrong? Could anybody
> help me?
> Arda Han
> Software Engineer
>

Replication of DATABASES

I have a database that I cannot make creations of tables and or you consult.
would like to know how to create one replies of this updated database
(immediate or of times in times), and I will be able to in this new one to
create tables and querys.Frank,
You might want to check theReplication topics in Books OnLine.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Frank Dulk" <fdulk@.bol.com.br> wrote in message
news:u502LVUYDHA.1580@.tk2msftngp13.phx.gbl...
> I have a database that I cannot make creations of tables and or you
consult.
> would like to know how to create one replies of this updated database
> (immediate or of times in times), and I will be able to in this new one to
> create tables and querys.
>
>

Replication Model

Hello,
I am just playing about with replication and trying to work the best way
to keep a central database updated.
We have a laptop user who will need to be able to work in disconnected mode
(MSDE) then connect up and replicate changes back to a server from which
others can run reports. The server copy will never be updated besides from
the changes replicated down from the 1 laptop user.
What would be the best model for this? Seems I have a few options but was
hoping someone could point me in the right direction of which machine would
be the publisher, the type (merge, snapshot) and whether push or pull. I
understand the concepts of publisher, subscriber etc, but am just unsure of
how it all fits together.
Thanks is advance
- EdHi
It sounds like your application would probably be a candidate for merge
replication, especially if there is a future need for more than one client
updating the data and if you are replicating larger volumes of data.
Snapshot replication would be more applicable if the data was not updatable
and the frequency of replication low.
You don't say which version of SQL Server is running on the server, this may
effect how you administer the replication and you may want to check out the
topic "Understanding SQL Server 2000 Desktop Engine (MSDE 2000)" in Books
Online.
John
"Ed." wrote:
> Hello,
> I am just playing about with replication and trying to work the best way
> to keep a central database updated.
> We have a laptop user who will need to be able to work in disconnected mode
> (MSDE) then connect up and replicate changes back to a server from which
> others can run reports. The server copy will never be updated besides from
> the changes replicated down from the 1 laptop user.
> What would be the best model for this? Seems I have a few options but was
> hoping someone could point me in the right direction of which machine would
> be the publisher, the type (merge, snapshot) and whether push or pull. I
> understand the concepts of publisher, subscriber etc, but am just unsure of
> how it all fits together.
> Thanks is advance
> - Ed
>
>

Replication Model

Hello,
I am just playing about with replication and trying to work the best way
to keep a central database updated.
We have a laptop user who will need to be able to work in disconnected mode
(MSDE) then connect up and replicate changes back to a server from which
others can run reports. The server copy will never be updated besides from
the changes replicated down from the 1 laptop user.
What would be the best model for this? Seems I have a few options but was
hoping someone could point me in the right direction of which machine would
be the publisher, the type (merge, snapshot) and whether push or pull. I
understand the concepts of publisher, subscriber etc, but am just unsure of
how it all fits together.
Thanks is advance
- Ed
Hi
It sounds like your application would probably be a candidate for merge
replication, especially if there is a future need for more than one client
updating the data and if you are replicating larger volumes of data.
Snapshot replication would be more applicable if the data was not updatable
and the frequency of replication low.
You don't say which version of SQL Server is running on the server, this may
effect how you administer the replication and you may want to check out the
topic "Understanding SQL Server 2000 Desktop Engine (MSDE 2000)" in Books
Online.
John
"Ed." wrote:

> Hello,
> I am just playing about with replication and trying to work the best way
> to keep a central database updated.
> We have a laptop user who will need to be able to work in disconnected mode
> (MSDE) then connect up and replicate changes back to a server from which
> others can run reports. The server copy will never be updated besides from
> the changes replicated down from the 1 laptop user.
> What would be the best model for this? Seems I have a few options but was
> hoping someone could point me in the right direction of which machine would
> be the publisher, the type (merge, snapshot) and whether push or pull. I
> understand the concepts of publisher, subscriber etc, but am just unsure of
> how it all fits together.
> Thanks is advance
> - Ed
>
>

Replication Model

Hello,
I am just playing about with replication and trying to work the best way
to keep a central database updated.
We have a laptop user who will need to be able to work in disconnected mode
(MSDE) then connect up and replicate changes back to a server from which
others can run reports. The server copy will never be updated besides from
the changes replicated down from the 1 laptop user.
What would be the best model for this? Seems I have a few options but was
hoping someone could point me in the right direction of which machine would
be the publisher, the type (merge, snapshot) and whether push or pull. I
understand the concepts of publisher, subscriber etc, but am just unsure of
how it all fits together.
Thanks is advance
- EdHi
It sounds like your application would probably be a candidate for merge
replication, especially if there is a future need for more than one client
updating the data and if you are replicating larger volumes of data.
Snapshot replication would be more applicable if the data was not updatable
and the frequency of replication low.
You don't say which version of SQL Server is running on the server, this may
effect how you administer the replication and you may want to check out the
topic "Understanding SQL Server 2000 Desktop Engine (MSDE 2000)" in Books
Online.
John
"Ed." wrote:

> Hello,
> I am just playing about with replication and trying to work the best way
> to keep a central database updated.
> We have a laptop user who will need to be able to work in disconnected mod
e
> (MSDE) then connect up and replicate changes back to a server from which
> others can run reports. The server copy will never be updated besides from
> the changes replicated down from the 1 laptop user.
> What would be the best model for this? Seems I have a few options but was
> hoping someone could point me in the right direction of which machine woul
d
> be the publisher, the type (merge, snapshot) and whether push or pull. I
> understand the concepts of publisher, subscriber etc, but am just unsure o
f
> how it all fits together.
> Thanks is advance
> - Ed
>
>