none
"Timeout Expired" in Sql Azure Data Sync wizard (November CTP download) RRS feed

  • Question

  • I've been experimenting with the Sql Azure Data Sync wizard as a means of getting data from our production database onto Sql Azure, and maintaining the DB in a "slave" mode until we fully "cut-over" to Azure.

    I pointed the wizard at my local instance, and pointed it at my sql azure server (which I confirmed by testing connections etc).  I selected my tables, and ordered them correctly.  However, moments after clicking the "Process" button, I get the error: "Timeout Expired.  The timeout period elapsed prioro to completion of the operation of the server is not responding".  There is no other error message that I can detect.

    I understand that this is a CTP, and I guess I would expect some caveats with the tool, but this does not seem like a complicated scenario - can anyone help?

    I also have some other feedback about the wizard:  On the "SQL Azure Database" page, it asks for server name, database name, admin user and password.  The dialog gives me the impression that a database with the specified name must already exist on the server, so I created my DB.  However if the DB exists when the "Process" button is pressed later, then the wizard fails.  Really, it should be a little more robust if this case happens.  Likewise, if the schema and tables exist in azure then that is recoverable error (in particular if the tables are empty). - IE I would like to be able to _add_ data syncing objects to an already existing (sqlazure, sqlserver) pair of databases.

    As it is at the moment, the tool not ready for production use.  Do you have any idea when an RTM version may be available or even if this CTP is being actively developed? (ie, should I be investing my time with an alternative tool - for example the Sql Azure Migration Wizard on CodePlex)

     

    Cheers

    Pete

    Friday, May 14, 2010 3:31 PM

Answers

  • Hi,

    Thanks for your feedback. We are working on the v1 release of this Sql Azure Data Sync applcation now, and we expect to release it the fourth quarter of this year. For the existing database behavior in the "SQL Azure Database" page, we are aware of it too and will provide a more clear user experience in the new release.

    For the Timeout Expired exception, I believe it is due to a bug in the provider. When one of your exsiting table have many rows when provisioning it for sync, the default 30 seconds SqlCommand timeout is not enough to finish the provision. We have a fix for it in the next Sync Framework release by dividing provisioning into multiple SqlCommands and allowing user to set the provision timeout value.

    Thanks,
    Dong


    This posting is provided AS IS with no warranties, and confers no rights.
    Friday, May 14, 2010 6:06 PM
    Moderator

All replies

  • Hi,

    Thanks for your feedback. We are working on the v1 release of this Sql Azure Data Sync applcation now, and we expect to release it the fourth quarter of this year. For the existing database behavior in the "SQL Azure Database" page, we are aware of it too and will provide a more clear user experience in the new release.

    For the Timeout Expired exception, I believe it is due to a bug in the provider. When one of your exsiting table have many rows when provisioning it for sync, the default 30 seconds SqlCommand timeout is not enough to finish the provision. We have a fix for it in the next Sync Framework release by dividing provisioning into multiple SqlCommands and allowing user to set the provision timeout value.

    Thanks,
    Dong


    This posting is provided AS IS with no warranties, and confers no rights.
    Friday, May 14, 2010 6:06 PM
    Moderator
  • OK - I was aware that the Sql Azure Data Sync wizard was a CTP, so a few rough edges are to be expected.  I'm afraid waiting until Q4 is not an option as we want to mograte our DB sooner - I'll just have to try another approach.  

    Thanks again.

    Pete

    Monday, May 17, 2010 8:59 AM
  • Any news on this issue? I am also getting timeout errors during provisioning. In my case I am not using Azure Sync however. I am doing a sync between SQL Server <-> SQL Server with the offline provider.

    Is there a release date for the new version?

    Tuesday, April 12, 2011 8:39 AM
  • if you're using the offline providers, am afraid this still remains an issue. and Sync Fx v4 is not going to be out in the foreseable future and am not sure the offline providers are being updated on it as well.

    If you shift to the collaboration providers (SqlSyncProvider), you can now set the CommandTimeout in v2.1

    Tuesday, April 12, 2011 4:32 PM
    Moderator