Replication Question

I need an expert opinion in SQL Server 2005 replication.
Is it possible to do a bi-directional replication ?. Here is what we want to
do:
We have a third party appliation with a database back-end. We want to have a
Server SQL_A with the database on it and another Server SQL_B with the copy
of the same database.
SQL_A server will be used by our company people and the SQL_B will be used
by the clients. Can we have bi-directional replication between the SQL_A and
SQL_B ?
The reason for this is the security concerns. Thanks for any Expert opinion
:).Search on "merge replication" in BOL. I suspect that it will be quite a
project to setup though.
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:8D66E1E9-61F2-4F0A-8E2C-6DE43007111E@.microsoft.com...
>I need an expert opinion in SQL Server 2005 replication.
> Is it possible to do a bi-directional replication ?. Here is what we want
> to
> do:
> We have a third party appliation with a database back-end. We want to have
> a
> Server SQL_A with the database on it and another Server SQL_B with the
> copy
> of the same database.
> SQL_A server will be used by our company people and the SQL_B will be used
> by the clients. Can we have bi-directional replication between the SQL_A
> and
> SQL_B ?
> The reason for this is the security concerns. Thanks for any Expert
> opinion
> :).
>|||You may want to take a look at the following documents:
How To Implement Bidirectional Transactional Replication
http://support.microsoft.com/kb/820675
Bidirectional Transactional Replication
http://msdn2.microsoft.com/en-us/library/ms151855.aspx
--
Ekrem Ã?nsoy
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:8D66E1E9-61F2-4F0A-8E2C-6DE43007111E@.microsoft.com...
>I need an expert opinion in SQL Server 2005 replication.
> Is it possible to do a bi-directional replication ?. Here is what we want
> to
> do:
> We have a third party appliation with a database back-end. We want to have
> a
> Server SQL_A with the database on it and another Server SQL_B with the
> copy
> of the same database.
> SQL_A server will be used by our company people and the SQL_B will be used
> by the clients. Can we have bi-directional replication between the SQL_A
> and
> SQL_B ?
> The reason for this is the security concerns. Thanks for any Expert
> opinion
> :).
>

Replication problem(integrity violation) - Cannot Sync up emul

Hi
Unfortunately I am not an expert on replication!
Hilary Cotter who has replied in microsoft.public.sqlserver.replication
knows alot more about replication than I.
John
"steroche" wrote:

> Im afraid not. I have tried everything at this stage and its driving me
> crazy!!!!!
> I have re-published my database about 10times i'd say and i always get
> an error.
> Generally I get one of 2 errors. If i have already created the database
> the errors are:
> Message "Row data cannot be set. [,,,,,]"
> NativeError 28572
> and
> Message "Invalid row handle"
> NativeError 0
> However if i dont have it created previous to running it and it creates
> it itself I get the error:
> message "Run"
> NativeError 28557
> Message "The row update or insert cannot be reapplied due to an
> integrity violation. [,,,,,]
> NativeError 28549
> What the hell is going on' I have checked all the tables to make sure
> that the checkbox "Enforce Relationship for replication" IS checked so
> the NOT FOR REPLICATION bug doesn't apply here.
> I have checked over all my datatypes and relationships and the data
> that they contain to ensure that there can be no FK conflicts.
> I know the table is being created as i can see it on the CE Query
> analyser but it contains no tables so this probably gives rise to the
> second error but why is it not creating the db properly in the first
> place'
> I heard that compacting the db might help - how do i do that'
>Check that your subset filters and merge filters in the publication are
correctly constructed.
You are potentially sending down some data on a foreign key that is getting
filtered out.
Rob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:F13AC93E-5354-4A2F-A066-2B3D22AA6D8F@.microsoft.com...
> Hi
> Unfortunately I am not an expert on replication!
> Hilary Cotter who has replied in microsoft.public.sqlserver.replication
> knows alot more about replication than I.
> John
> "steroche" wrote:
>sql