Viewing 15 posts - 76 through 90 (of 196 total)
I see. I got in touch with these thougths several times with my own systems. If the subscriber get's offline "a long time" in my opinion there are 2 possibilities:
1)...
July 1, 2013 at 12:49 am
...almost identical code...
When I run it directly...
What exactly do you mean by these two points?
Post your "almost identical" code too.
June 30, 2013 at 12:46 am
one more thing: what is a replication DB for you? Published database or subscribed? Whatever, I don't think it's something specific with replication that causes your deadlocks. Replication is just...
June 30, 2013 at 12:34 am
Dealing with deadlocks is a very very very extensive topic.
For the beginning, try to get detailled information about each deadlock (for example use trace flag 1222).
Then have a look at...
June 30, 2013 at 12:30 am
Depends on what exactly you want to know.
You can either use SQL Profiler for tracing what is happening on the tempdb itself or you can use the Performance Monitor. Have...
June 30, 2013 at 12:27 am
• Query timeout expired (Source: MSSQLServer, Error number: HYT00)
Don't have a idea, but looking at this part of the error message: analyse the processes running on the subscriber. Seems that the...
June 30, 2013 at 12:25 am
extraction from books online for the sp_update_job-procedure
sp_update_job @job_name = 'JobName', @enabled = 0
June 28, 2013 at 11:16 am
Only one idea: did the password of the user change? If so you will have to update all the replication agents with the new password.
But, it could also be, that...
June 28, 2013 at 11:09 am
I don't think there is a comfortable way to do this. Fix the connection and let the replication do it's job.
Even if you woul transfer the commands manually, what if...
June 28, 2013 at 11:05 am
hi,
it's a little bit hard to understand you're question but I think I got it.
Let's have a look at your CREATE TABLE statement. You did not add the information...
June 28, 2013 at 10:55 am
I agree, do the rebuild in management studio and see what happens.
If still no usable result use the CHECKTABLE statement (have a look at books online). It's similar to CHECKDB...
June 28, 2013 at 10:35 am
I'm not talking about the cluster but about the always on availability groups!!! Like the times before
You defined your always on groups for doing backups on the secondary replica.
In the...
June 25, 2013 at 1:33 am
That's the way I understand. Unless you configure the availiability group for backups on secondary replicas too. Just guess that, having my first always on getting started these days 😉
June 24, 2013 at 11:43 am
Roust_m (6/20/2013)
The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information.
Locate the SQL-Job in management studio (not within the replication monitor)...
June 22, 2013 at 7:42 am
rajborntodare (6/21/2013)
June 22, 2013 at 1:37 am
Viewing 15 posts - 76 through 90 (of 196 total)