May 30, 2015 at 4:27 pm
Hi,
We are using sql server 2008r2 standard edition.
We have replication set up. Publisher and distributor are on the same server, subscriber is in different server.
Suddenly the replication started failing and continued more than 12 hrs. When I tried to connect to the subscriber server, I am able to connect to the server but not able to run any queries or not able to open the error log from SSMS.
Is there any way to find from the default trace why the replication failed and the server is not responded?
What columns do I need to query from the trace?
May 31, 2015 at 3:12 am
Probably not, the error log would be a far more likely place to have that info.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 31, 2015 at 3:18 pm
I want to know is there some details from your experience.
SA account is enabled in both servers. I disabled the sa account in both publisher (Distributor) and Subscriber around 2 weeks ago.
Suddenly yesterday I saw message that couldn't able to connect the subscriber. After the 14 hrs, we restarted the subscriber because the subscriber is not responding yet all.
After the restart, I reinitialize the but still I am seeing the same error msg. Once I enabled SA account in subscriber, it started working the replication. The snapshot started applying @subscriber?
I have some basic questions here
1) How the SA account is linked with replication?
2) Why there was no issue from past 2 weeks
3) How the subscriber not responded suddenly after the replication failed?
May 31, 2015 at 4:10 pm
It's not, unless when you set the replication up, you configured it to use the sa account (which is not default iirc)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2015 at 8:41 am
How to find out that?
When I check on publication ppt, security it is showing use sql sever agent account.
Is the same thing do we need to look or different way?
June 1, 2015 at 9:45 am
I can see continously
A time-out occurred while waiting for buffer latch -- type 3 in the subscriber server before restart
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply