September 21, 2005 at 7:58 am
Hi all,
I implemented a transactional replication with 2 SQL Servers 2000. (works fine)
My problem is:
When the Publisher fails or the Server is down, I'm not possible to execute SQL statements on the slave Server (delete,update...) because it's locked for replication.
Any help would be greatly appreciated
Best regards
Jens
September 22, 2005 at 4:18 am
sounds like you are using immediate updating. Consider using bi-directional transaction, queued updating, or immeidate with queued failover and manually fail to queued, or merge replication.
September 22, 2005 at 5:10 am
Hi,
I just found out that it is normal for transactional replication that I cannot access the Subscriber any more.
My goal by creating a replication was to have a backup system.If my primary server crashes I can simply switch to my spare system.
Maybe this was not the right way to achieve this.
Do you have any better suggestions. I read something about Log Shipping. Is that the way to go?????
best regard
Jens
September 27, 2005 at 1:54 am
When I am creating Replication --> Publications
In Create Publication Wizard click on finish.
I am getting this error.
SQL Server Enterprise Manager could not configure ‘Server Name’ as the Distributor for ‘Server Name’
14114: '[null]' is not configured s a distributor
Please guide me
September 30, 2005 at 2:42 am
When I am creating Replication --> configuring publisher,distrbutor,etc
I am getting this error.
"error 18483 : could not connect to server g4b because 'distributor_admin' is not defined as a remote login at the server"
please help me
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply