Comments
Sort by recent activity
Which redgate connection is timing out in this case (I gave you the stack trace). Also, what is the Redgate RegisterForDataCompare function supposed to be doing? That is where the timeout is occurring. I can't troubleshoot this function since there's no source for it. I really need your help to figure out why the exception is getting thrown in this function. I'm guessing the connection timeout is set to 100 minutes since no command is running...but I really need to verify. Please help me verify this. Thank you. / comments
Which redgate connection is timing out in this case (I gave you the stack trace). Also, what is the Redgate RegisterForDataCompare function supposed to be doing? That is where the timeout is occu...
I'm confused now. First, it was a connectivity issue where the connection was timing out (as shown in the stack trace). Now it's a command timeout? Wouldn't the exception get thown on a SQLcommand instead of a SQLconnection if this was the case?
Yes, I have used the sp_who2 and no sysprocesses are getting blocked when this is happening. However, there is no redgate SYSPROCESS to BLOCK anyway (unusual since there is always one running when everything is working correctly) during the period before the timeout eventually occurs. Again there is no select command that can get timed out since there is no redgate sysprocess running...so what does this exception mean anyway?
Anyway, it sounds like changing the connection timeout to 20 minutes will have no effect since the timeout occurs after 100 minutes. Correct? / comments
I'm confused now. First, it was a connectivity issue where the connection was timing out (as shown in the stack trace). Now it's a command timeout? Wouldn't the exception get thown on a SQLcomma...
Thanks, but it's timing out after 100 minutes (6002-6003 seconds) just for one table so will changing the timeout to 20 minutes help? Since we're currently not setting timeout for connection or command, what are the default values that redgate is using? / comments
Thanks, but it's timing out after 100 minutes (6002-6003 seconds) just for one table so will changing the timeout to 20 minutes help? Since we're currently not setting timeout for connection or co...
It's just one table. It is usually around 20,000 rows (it gets cleared out every hour after the data is moved to the destination server). The destination server isn't rebooted...SQL server is just stopped and restarted.
What connectivity problem are you referring to? / comments
It's just one table. It is usually around 20,000 rows (it gets cleared out every hour after the data is moved to the destination server). The destination server isn't rebooted...SQL server is jus...
Sorry about the "replication" terminology. Basically, we're only updating changed table rows using a lastUpdate field. I'm just trying to find out why the excute time is slowing down so much now. It's not consistent but when it's slow, it's sloooooooow. It sounds like there is just too much of a load on SQL server and there's nothing I can do with the redgate libraries to speed this up, would you agree? / comments
Sorry about the "replication" terminology. Basically, we're only updating changed table rows using a lastUpdate field. I'm just trying to find out why the excute time is slowing down so much now....
Restarting SQL was the only way I was able to stop getting the 2 hour timeouts trying to replicate the tables.
Yes, this is a live production system. Today, we had a record breaking 35 minutes to replicate 21 tables. Something is definately wrong. [image] / comments
Restarting SQL was the only way I was able to stop getting the 2 hour timeouts trying to replicate the tables.
Yes, this is a live production system. Today, we had a record breaking 35 minutes to ...
The timeout varies: anywhere between 6704-7647 seconds. This issue occurred throughout the long weekend (was logged) and wasn't resolved until I manually stopped and restarted SQL server earlier this week. Is there a better way to recover from this timeout phase?
When it doesn't time out, the replication time varies as well: between 730 seconds (122166 rows replicated) to 1822(984 rows replicated) seconds. Thankfully, today we're experiencing the lower part of this range (unlike earlier this week). The same set of tables is used in each case so there doesn't seem to be any rhyme or reason why the time varies. The only reason I can think of is the fact that since there was so many timeout issues over the weekend with the redgate replication, it caused subsequent extended time once SQL server was restarted. Would you agree? / comments
The timeout varies: anywhere between 6704-7647 seconds. This issue occurred throughout the long weekend (was logged) and wasn't resolved until I manually stopped and restarted SQL server earlier t...
Okay, so if I'm replicating 21 tables, I should have 210 minutes to replicate. Therefore, it must be timing out on of the tables and throwing an exception from the ExecuteBlock method. The more serious issue is the replication time increase since this used to be a lot faster last week. Even when there is a very low number of rows replicated, the time increase is doubled. Is there a way to speed this up again? / comments
Okay, so if I'm replicating 21 tables, I should have 210 minutes to replicate. Therefore, it must be timing out on of the tables and throwing an exception from the ExecuteBlock method. The more s...
Are you sure? I'm currently using the ExcecuteBlock method (not my own block executor) and my timeout is 2 hours (not 10 minutes). Maybe this is version specific (I'm using version 6)?
Also, in the past week I've notice the the replication time (when not timing out) has increased significantly. Our set of tables replicated in under 11 minutes last week. Currently, it's taking 20-25 minutes on a regular basis. Is there a reason this is happening (even when no new rows are being added to the table)? This is very difficult to troubleshoot since the code is hidden in the redgate DLLs. Could upgrading the libraries help (currently we're using version 6...not 8)? I'm afraid to upgrade them now if the timeout has been decreased to 10 minutes. / comments
Are you sure? I'm currently using the ExcecuteBlock method (not my own block executor) and my timeout is 2 hours (not 10 minutes). Maybe this is version specific (I'm using version 6)?
Also, in t...