How can we help you today? How can we help you today?

connection timeout registering remote database

Using SQL Compare 6 beta I get a timeout trying to register a database on a remote server. If I use SQL compare 5 instead, I can consistently register the same database on the remote server. I do not find an option to increase the timeout value for the connection. Did the timeout value change in SQL compare 6?
rbennet8
0

Comments

6 comments

Sort by
  • JonathanWatts
    Hi there,

    No we didn't change this value, I will have a word with the developers and see if we had added something that might have caused this.

    Is it happening all the time to all databases on this server?

    Regards,

    Jonathan
    JonathanWatts
    0
  • JonathanWatts
    Just out of interest, how large is the database you are trying to compare.
    JonathanWatts
    0
  • rbennet8
    Both PC's are my development servers. Yes it happens each time I try to compare between the databases on the different pcs using the beta version. the databases have just the schema with very little data. About 200 tables, 400 stored procs, and 20 functions.
    rbennet8
    0
  • JonathanWatts
    Hi there,

    We have a similar size database on out test systems here, and we don't have any problems with timeouts, so it is likely to be an object in your database that SQL Compare is processing is causing problems rather than the size of the database.

    What is the last message displayed in the progress dialog before this error occurs?

    Can you run a trace on the effected server whilst running SQL Compare? Then locate the last query in the trace that was run with an application name of "Red Gate Software - SQL Tools". If you could run this query in SSMS or QA and let us know the average execution time that too would be useful as would the trace itself.


    Regards,

    Jonathan
    JonathanWatts
    0
  • rbennet8
    For now I am going to pass it off as a network problem on the day it consistently failed to register. Today, it does not fail to register and compare the remote server database.

    On the days that it failed, it was during the registration phase. It never started reading the objects which is why I suspected the timeout value had changed. It seemed strange that the beta version failed during registration and the SQL compare 5 did not when trying to connect to the same server and database.
    rbennet8
    0
  • JonathanWatts
    That is good news, you had me worried there for a day.

    We don't think that we made SQL Compare 6 less tolerant to network issues, but if you could keep us posted about this that would be useful.

    Thanks.

    Regards,

    Jonathan
    JonathanWatts
    0

Add comment

Please sign in to leave a comment.