Replication and SQL Server Authentication

I'm trying to use replciation between two computers that run SQL Server that
has been installed using mixed mode authentication, but the replciation
fails. Here are the details:
The Publisher/Distributer - I have installed SQL Server using mixed mode
authentication and used a blank password for user 'sa'. The Publisher has
registered the Subscriber succesfully using SQL Server authentication.
The Subscriber - The same as the Publisher.
I prepared a database for a merge publication and the snapshot agent
completed its job successfully.
When I push a new subscription to the publication, the merge agent fails
declaring that he couldn't connect to the subscriber as login for us 'sa'
fails because it is not associated with a trusted connection.
I knew form Microsoft SQL Server administration book that a trusted
connection is used for windows authentication.
I have reinstalled SQL Server on the Subscriber using Windows
authentication, the publisher remains the same, but te problem remains the
same.
Can a merge publication be used when both the publisher and the subscriber
use SQL Server authentication?!
Thanks in advance,
Shehab.
Go to Tools, Replication, Configure Publishers, Distributors and
Subscribers, and click on the Subscribers tab. Click the browse button to
the right of your subscriber, make sure you are using SQL Authentication
here and make sure the password is blank.
Actually you should not be using a blank password at all. Its a secuirty
risk.
Hilary
"Shehab Kamal" <ShehabKamal@.discussions.microsoft.com> wrote in message
news:527D5795-FA53-44D6-9C73-FD604698A5AA@.microsoft.com...
> I'm trying to use replciation between two computers that run SQL Server
> that
> has been installed using mixed mode authentication, but the replciation
> fails. Here are the details:
> The Publisher/Distributer - I have installed SQL Server using mixed mode
> authentication and used a blank password for user 'sa'. The Publisher has
> registered the Subscriber succesfully using SQL Server authentication.
> The Subscriber - The same as the Publisher.
> I prepared a database for a merge publication and the snapshot agent
> completed its job successfully.
> When I push a new subscription to the publication, the merge agent fails
> declaring that he couldn't connect to the subscriber as login for us 'sa'
> fails because it is not associated with a trusted connection.
> I knew form Microsoft SQL Server administration book that a trusted
> connection is used for windows authentication.
> I have reinstalled SQL Server on the Subscriber using Windows
> authentication, the publisher remains the same, but te problem remains the
> same.
> Can a merge publication be used when both the publisher and the subscriber
> use SQL Server authentication?!
> Thanks in advance,
> Shehab.

Replication and ReadOnly Database

Hi All,
Once i set the database to readonly mode, may i know if i can continue to
use trsnaction replication to replciation data from the readwrite db to the
readonly db?
Thx a lot
Regards.
NortnoNorton wrote:
> Hi All,
> Once i set the database to readonly mode, may i know if i can continue to
> use trsnaction replication to replciation data from the readwrite db to th
e
> readonly db?
> Thx a lot
> Regards.
> Nortno
>
Are you asking if you can make the subscriber database read-only?
Replication works by writing transactions to the subscriber database
that have been received from the publication database. If the database
is read-only, how's it going to write those transactions?
Sounds like you're trying to prevent users from changing data in the
subscriber database. If so, just deny them write access to the database
(db_denydatawriter).|||Thx a lot
^_^
"Tracy McKibben" <tracy@.realsqlguy.com>
'?:OVgWGGknGHA.3340@.TK2MSFTNGP02.phx.gbl...
> Norton wrote:
> Are you asking if you can make the subscriber database read-only?
> Replication works by writing transactions to the subscriber database that
> have been received from the publication database. If the database is
> read-only, how's it going to write those transactions?
> Sounds like you're trying to prevent users from changing data in the
> subscriber database. If so, just deny them write access to the database
> (db_denydatawriter).

replication

Hi,

I posted this in the repl section, but perhaps I should post it here as well. Say for example, with mirroring set to high-safety mode, if the mirror box goes down, replication stops flowing until the server comes back online? Or should replication continue to flow down to the subscribers since the primary server is still online, but the mirror is not.

Thanks

J

What you mean to say when mirror box goes down?

If the mirror server is unreachable or not available to connect on network then yes Replication will also be affected.