Queries on SQL Data Sync

Hi,
One of our customers had the following query on SQL Data Sync
1. ALter database permission is required during setup of sync services and it switches ON the SNAPSHOT ISOLATION level on our on premise DB. what is the impact of it?
2. After setting up the SNAPSHOT ISOLATION LEVEL ON, it creates tracking tables, some SPs, and triggers and set read commited isolation level multiple times. Is there a way that these
objects will be created in some other DB and not on the main OLTP so that we can avoid cluttering the main DB with tracking tables, triggers, SPs ets?
3. As the SNAPSHOT isolation level is introduced in SQL 2005 onwards and is for maintaining row versions in TEMP DB. Does it mean switching it on at DB level, it's going to maintain the
row and transaction version for all DB objects in TEMP DB , irrespective of whether they are part of sync group or not?
Any pointers on this would be appreciated.
Cheers!

Hi Harish,
For the knowledge about SNAPSHOT ISOLATION, please check the detail here:
http://msdn.microsoft.com/en-us/library/tcbchxcb(v=vs.110).aspx
For the objects created on the database, they cannot be created on other database since the objects need to visit the source database data.
Actually those objects are required by sync framework, you can find more details here:
http://msdn.microsoft.com/en-us/library/ee617382(v=sql.110).aspx
Regards,
Bowen

Similar Messages

  • SQL Data Sync - column type invalid for use as a key column

    Hello,
    our sync group is failing to do the sync. Here's a tracingID:
    For more information, provide tracing ID ‘e3e568b5-140a-4ae5-a4c8-c178c6bf805d’ to customer support.
    I must say, that the column in DB is not a PK or INDEX-ed, it was initially VARCHAR(MAX), after some reading I changed it to VARCHAR(200) and later to TEXT, but the result of syncing is still the same.
    Thank you,
    Bojan

    Hi Bojan,
    The error “column type invalid for use as a key column” could be due to the existence of unsupported data types or column properties when implementing the synchronization. I recommend you check your database according to this article:
    SQL Database Data Types supported by SQL Data Sync.
    Besides, before you design and implement a data synchronization plan, please check the following articles about system requirements for SQL Data Sync and so on.
    System Requirements for SQL Data Sync
    https://msdn.microsoft.com/en-us/library/azure/jj127278.aspx
    Known SQL Data Sync Limits
    https://msdn.microsoft.com/en-us/library/azure/jj590380.aspx
    SQL Data Sync Best Practices
    https://msdn.microsoft.com/en-us/library/azure/hh667328.aspx
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Azure SQL Data Sync, LINQ optimization bug

    How can I report the following Bug ?
    var empty = new Set<int>();
    var query = storage.table.Where(item => empty.Contains(item.id));
    // Entity Framework Extended
    query.DeleteAsync()
    The query is optimized to something like this, because the set is empty, and therefore the result set is always empty:
    SELECT
    CAST(NULL AS uniqueidentifier) AS [C1],
    CAST(NULL AS uniqueidentifier) AS [C2],
    CAST(NULL AS int) AS [C3],
    CAST(NULL AS int) AS [C4],
    CAST(NULL AS datetime2) AS [C5],
    CAST(NULL AS varchar(1)) AS [C6],
    CAST(NULL AS int) AS [C7]
    FROM ( SELECT 1 AS X ) AS [SingleRowTable1]
    WHERE 1 = 0
    Now the problem is that update and delete trigger, introduced by Azure SQL Data Sync, will fail because they require the primary key, which is not part of the optimized query. Meaning that when the set is empty the triggers will fail, but if the set contains
    an id, the query is not optimized and therefore will succeed.
    (SELECT [i].[PrimaryKeyId] FROM DELETED AS [i])
    Notice, the problem here is not Entity Framework Extended from my perspective, but the Azure SQL Data Sync Triggers! 

    not sure if i understood your post correctly, but the columns available in the logical inserted and deleted tables available in the trigger are the actual columns of the table itself, not the columns in the query that caused the trigger to fire.

  • SQL Data Sync Agent can not start - Debug error in windows 7 x86

    Log file as per below
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:Main,
    message:Microsoft SQL Data Sync Windows service is starting as a Windows Service.
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
    message:Microsoft SQL Data Sync Windows service starting.
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
    message:Starting a service worker thread.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:OnStart,
    message:Started a service worker thread.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:OnStart,
    message:Microsoft SQL Data Sync Windows service started successfully.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartUxWcfService,
    message: Namedpipe bd54233d-16ce-46d3-8858-5e564732b21c, BaseAddress net.pipe://localhost/bd54233d-16ce-46d3-8858-5e564732b21c
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartUxWcfService,
    message: Opened WCF Host
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartServiceThread,
    message: GetEntryAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, GetExecutingAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, Process.GetCurrentProcess().StartInfo.WorkingDirectory:
    LocalAgentHost 1/3/2013 11:55:37 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:AgentConfigDataManager.DownloadAndCacheServiceUrisFromLocator,
    message:Scale unit found
    AgentCore 1/3/2013 11:55:40 AM  id:AgentCore_InstanceStarted, rId:, sId:65915150-1284-4a17-9c13-d58e2830fcd9, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0
    ThreadId:40. Dispatcher started. Waiting
    ThreadId:43. GetRequest started.
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:46. GetRequest started.
    ThreadId:41. GetRequest started.
    ThreadId:48. GetRequest started.
    ThreadId:45. GetRequest started.
    ThreadId:42. GetRequest started.
    ThreadId:47. GetRequest started.
    ThreadId:44. GetRequest started.
    ThreadId:49. GetRequest started.
    ThreadId:50. GetRequest started.
    ThreadId:51. GetRequest started.
    ThreadId:52. GetRequest started.
    ThreadId:53. GetRequest started.
    ThreadId:54. GetRequest started.
    ThreadId:55. GetRequest started.
    ThreadId:56. GetRequest started.
    ThreadId:57. GetRequest started.
    ThreadId:58. GetRequest started.
    ThreadId:59. GetRequest started.
    ThreadId:60. GetRequest started.
    ThreadId:61. GetRequest started.
    ThreadId:62. GetRequest started.
    ThreadId:63. GetRequest started.
    ThreadId:64. GetRequest started.
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest

    Hi,
    I believe that your issue is resolved by now. Please try this step is the issue still persists.
    its security issues and re-install the data sync with domainname\Myaccount user and give the user as adminitsrator privileges and change the time of your system.
    http://social.technet.microsoft.com/wiki/contents/articles/2655.sql-azure-data-sync-troubleshooting-guide.aspx
    Girish Prajwal

  • SQL Data Sync - error during sync. Unable to diagnose the problem.

    I have 2 SQL data sync groups setup
    First one does a 1 way sync from azure to local db. Sync's only 1 table.
    Second one does a 1 way sync from local db to the azure. Syncs 2 tables.
    After setting it up and getting a few sync errors I was able to figure out what's wrong by checking the logs and fixing the problems. It was all running fine for a while and now it broke down.
    I got a sync error every time sync is attempted - however this time I'm not able to fix anything because I don't have any visibility on what's wrong - when I click on the Log tab in the Azure Management portal it just stays blank - no details come up.
    I click [Logs] Wait spinner comes up 
    And then it looks like this: 
    Another detail worth mentioning is that the error only occurs for the Second sync group that I have.
    Here's what I've attempted so far
    I poked around the azure management portal to try to find another way of looking at the logs - looking for something like ftp access to the log file - couldn't find anything like that.
    I refreshed schema in the sync rules tab.
    Used the SQL Data Sync agent tool on the premise to do the ping operation. Restarted the sql data sync windows service.
    Made sure I have the latest SQL Data Sync Agent installed.
    I'm wondering what are my options from here...
    I'm close to trying to deleting and recreating the sync group... I'm not too comfortable doing this because I know there are some sql tables that get created in the local db to support the operation of the sync - so if I delete the sync group would that automatically
    drop those helper tables as well or would I have to drop those manually - If I do drop those then that will obviously brake the other sync group that works fin as well..
    Any advice is appreciated. Thanks

    hi,
    According to your description, it seems the issue is related to SQL Azure, I will move this thread to SQL Azure Discussions forums to get a better support.
    Regards,
    Will
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Data sync to external SQL from Access Web App

    Hi all
    Am I dreaming or does creating a table in an Access Web app based on an external SQL Azure database table (not the intrinsic one) end up being an import not a sync?  It doesn't even seem to update when i open the external table and refresh it?
    I am adding new records at the external SQL source and they are not updating in the table in the WebApp
    Is anyone having similar problems?
    Cheers
    Sally

    Hi Sally,
    >> I am adding new records at the external SQL source and they are not updating in the table in the WebApp
    Do you mean that you import a table from an external SQL Azure database into Access Web app, the data in Access Web app did not update after you change the an external SQL Azure database data? In my option, this is expected behavior if you are using import
    table. Importing from another database would not achieve that, and it only achieves copying data from another database. I am afraid that you could not achieve your requirement from Access Web app.
    As far as I know, the database of Access web app is Azure DB, I think you could sync the Access web app Azure DB and External Azure DB, you could refer the link below for more information.
    Reference:
    http://azure.microsoft.com/en-us/documentation/articles/sql-database-get-started-sql-data-sync/
    I am not familiar with Azure DB, and if you have issues about Azure DB, I will recommend you go to the link below for help.
    Reference:
    http://social.technet.microsoft.com/Forums/en-US/home?forum=ssdsgetstarted
    Thanks for your understanding.
    Best Regards,
    Edward
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • SQL Azure Data Sync stuck in Processing State since 14 Sep 2014

    Hi,
    I've a sync group stuck in "processing" state since 14 Sep 2014, have tried to restart the client PC, restarted the sync service and also tried to regenerate the sync agent key, but still in vain. Would anyone please help me to figure it out what's
    the problem? This problem happened across my sync group very frequent recently (they're located in different physical locations), but still no workaround or the root cause :(
    Here's the sync group details:
    Sync group name:  ew_sync_a069
    Status
    Processing
    LAST SYNC
    9/14/2014 11:11:22 PM
    Sync Group ID
    4a604aad-e318-469d-adde-9ed4e1d52ead_East Asia
    Location
    East Asia
    Subscription Name
    Solo Customer Batch 3
    Subscription ID
    a68811f9-f82a-4e7c-b93c-d1bee226f84b
    Conflict Resolution
    Client Wins
    Thanks
    for your help.
    Best regards,
    Michael Yung

    As the client need the sync to be fixed ASAP, cannot wait for the answer / help, I've removed the sync agent, compare the data (what data need to download from Azure to client, what data need to upload from client to Azure) and recreate back the sync group.
    Hi Micheal,
    Is this the workaround in your scenario? Since the Azure SQL Data Sync failed, the Microsoft support engineer will help to solve the problem from backend based on your subscription ID and Sync Group ID. Sometime delay might be expected. Your patience is
    greatly appreciated. Thank you for your understanding and support.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Azure Data Sync Log Take Too Much Time to Load

    Hi,
    I've found that the Azure Sync Log inside the Portal take too much time to load if my sync group was created long time ago. i.e. for those new sync group with only a few logs, it will take around 5 seconds for loading. However, I've many sync group created
    more than 1 year, and it will take me up to 10 minutes for viewing the first page of the logs.
    It seems the Portal will download ALL the logs to my browser even I just want to view the most recent logs (maybe I just want to view the last 10 records, but it will download the whole 5000 pages?)
    It will be great if the Portal only fetch the data of the page I am currently viewing, instead of fetching all the logs.
    Is there any ways to speed up the log loading time?
    Michael Yung

    Hello,
    I suggest you post a feedback on
    Azure SQL Data Sync feedback forum.
    All of the feedback you share in the forum will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • Data Sync stuck in processing

    Can you please delete my data sync? I tried to cancel the data sync, so I could delete it but it has been stuck in processing for almost 24 hours now. The subscription id is 2b362515-3f77-44fc-9803-08334705d01a and the sync group is called DevSyncGroup.

    Hi CpAtMtb,
    Thanks for your information about  subscription ID.
    The Microsoft support engineer will help to solve the problem from backend. Sometime delay might be expected. Your patience is greatly appreciated. Thank you for your understanding and support.
    Besides, any of the following can result in a sync group being stuck in the processing state.
    • The client agent is offline.
     Be sure that the client agent is online then try again.
    • The client agent is uninstalled or missing.
     If the client agent is uninstalled or otherwise missing:
        1. Remove agent XML file from the SQL Data Sync (Preview) installation folder if the file exists.
        2. Install the agent on same/another on-premise computer, submit the agent key from the portal generated for the agent that’s showing offline.
    • The SQL Data Sync (Preview) service is stopped.
        1. In the Start menu, search on Services.
        2. Click Services in the Programs section of the search results.
        3. Find the SQL Data Sync (Preview) service.
        4. If the service status is Stopped right-click the service name and select Start from the dropdown menu.
    Reference :  http://msdn.microsoft.com/en-us/library/azure/hh667321.aspx#ProcessingError
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Data sync between on-premise and azure database

    HI, I am not able to setup data sync between my on-premise database and azure database. Following is the error I am getting after it ran for almost 36 hours...
    Sync failed with the exception "GetStatus failed with exception:Sync worker failed, checked by GetStatus method. Failure details:An unexpected error occurred when applying batch file C:\Resources\directory\4c6dc848db5a4ae88265ee5aa1d44f40.NTierSyncServiceWorkerRole.LS1\DSS_7b1d73b4-d125-466f-94ab-eaa4553ea0ae\ed19f805-3d50-466a-96b3-861c4f22d8a4.batch.
    See the inner exception for more details.Inner exception: Failed to execute the command 'UpdateCommand' for table 'dbo.Transactions'; the transaction was rolled back. Ensure that the command syntax is correct.Inner exception: SqlException Error Code: -2146232060
    - SqlError Number:10054, Message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) "    For more information,
    provide tracing ID ‘e6a1fad1-f995-4ffe-85db-0c6dc02423f1’ to customer support.

    Hi, sorry it has been a long time since your last post. Are you still using SQL Data Sync and hitting any issue which we could help with?
    Linda

  • Data Sync logs not showing in Azure Portal

    The Data sync Logs are no longer showing in the Azure Portal.  this started about a month ago.  Please help.   I opened a support ticket with Azure Support and they suggest the Logs Storage may have become full.
    LAST SYNC
    12/30/2014 7:28:22 AM
    SYNC GROUP ID
    ac33f15d-40c7-4e11-9f8c-c840c8cd1732_East US
    LOCATION
    East US
    SUBSCRIPTION NAME
    GEX-Azure-1
    SUBSCRIPTION ID
    653e04dd-c69f-4b16-8fd3-5efa954a6132
    CONFLICT RESOLUTION
    Hub Wins
    James Glenn

    Hi James,
    If there is on-premise database in the sync group,  you can use the following methods to check the log.
    • Check the Event Log entries on the box where you installed the SQL Data Sync Agent.
    Event Viewer->Applications and Services Logs->SQL Azure Data Sync Preview or Event Viewer->Applications and Services Logs->Data Sync Service
    • Turning logging in verbose mode. Open LocalAgentHost.exe.config in notepad. This file should be present in your installation directory.
    a) Uncomment the section that is currently commented < !-- < switches> < add name="SyncAgentTracer" value="4" /> < /switches> < trace autoflush="true" indentsize="4"> < listeners> <
    add name="myListener" type="Microsoft.SqlAzureDataSync.ClientLogging.DSSClientTraceListener, Microsoft.SqlAzureDataSync.ClientLogging, Version=2.0.0.0" initializeData="DSSAgentOutput.log" /> < remove name="Default"
    /> < /listeners> < /trace> -->
    b) Stop and restart SQL Azure Data Sync Preview Windows Service. Now you would find the detailed logs in files named DSSAgentOutput*.log
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • SQL Azure Sync Agent

    Hi,
    Anyone can share on the network port and IP address requirement for the SQL Database sync? 

    1433 is between the Data Sync Agent and your SQL Server.  443 is bidirectional for Data Sync Agent to connect to Azure Data Sync Service.
    the Data Sync Service itself do not connect to your on-premise SQL Server directly. Neither does the Data Sync Agent connect to the Azure SQL Database Correctly.
    to illustrate 
    on-premise SQL <-> Data Sync Agent <-> Azure Data Sync Service <-> Azure SQL Database

  • ADF mobile Data sync and sql lite usage

    Hi,
    We are working on ADF mobile POC.(Jdev version 11.1.2.3.0)
    Following Oracle mobile developer guide we generated "Webservice data control" which creates process(object) method to work with Webservice. We created the data-controls and used them in our Java code and are able to get the Webservice response also.
    However we want to implement the offline mode feature and for this we are not able to get any document reference for implementation.
    With offline mode support is it the application's responsibility to store the data locally using SQL Lite and do the data sync (using Web Service) OR will the framework would do the data sync automatically. Can someone please provide the implementation hint on how to do the Offline mode support in the mobile application using ADF.
    Thanks
    Pavan

    Hi,
    With offline mode support is it the application's responsibility to store the data locally using SQL Lite and do the data sync (using Web Service) OR will the framework would do the data sync automatically.
    This is all you. In this version of ADF Mobile there is no automatic data synchronization between local data and the server side. The sample that come with the ADF Mobile extension have a SQLLIte example as well, which is in the HR application. Look for the "DBConnectionFactory" file
    package application;
    import java.sql.Connection;
    import java.sql.SQLException;
    import oracle.adfmf.framework.api.AdfmfJavaUtilities;
    public class DBConnectionFactory {
        public DBConnectionFactory() {
            super();
        protected static Connection conn = null;
        public static Connection getConnection() throws Exception {
            if (conn == null) {
                try {
                    // create a database connection
                    String Dir = AdfmfJavaUtilities.getDirectoryPathRoot(AdfmfJavaUtilities.ApplicationDirectory);
                    String connStr = "jdbc:sqlite:" + Dir + "/HR.db";
                    conn = new SQLite.JDBCDataSource(connStr).getConnection();
                } catch (SQLException e) {
                    // if the error message is "out of memory",
                    // it probably means no database file is found
                    System.err.println(e.getMessage());
            return conn;
    }The LifeCycleListenerImpl class in the same demo shows how to use this SQL Lite connection
    package application;
    import java.io.BufferedReader;
    import java.io.InputStream;
    import java.io.InputStreamReader;
    import java.sql.Connection;
    import java.sql.ResultSet;
    import java.sql.SQLException;
    import java.sql.Statement;
    import java.util.ArrayList;
    import java.util.List;
    import javax.el.ValueExpression;
    import oracle.adfmf.application.LifeCycleListener;
    import oracle.adfmf.framework.api.AdfmfJavaUtilities;
    public class LifeCycleListenerImpl implements LifeCycleListener {
        public LifeCycleListenerImpl() {
         * The start method will be called at the start of the application. Only the
         * Application Lifecycle Event listener will be called on start up.
        public void start() {
            System.out.println("!!!!!!!!!!!!!! App Start !!!!!!!!!!!!!!");
            //InitDB();
            try {
                Statement stat = DBConnectionFactory.getConnection().createStatement();
                ResultSet rs = stat.executeQuery("SELECT * FROM EMPLOYEES;");
            } catch (SQLException e) {
                // if the error message is "out of memory",
                // it probably means no database file is found
                System.err.println(e.getMessage());
                System.out.println("Database does not exist, creating it");
                InitDB();
            } catch (Exception e) {
                System.err.println(e.getMessage());
            System.out.println("!!!!!!!!!!!!!! Done App Start !!!!!!!!!!!!!!");
         * The stop method will be called at the termination of the application. Only
         * the Application Lifecycle Event listener will be called on start up.
         * NOTE: Depending on how the application is being shutdown, this method may
         * or may not be called. Features should save off their state in the deactivate
         * handler.
        public void stop() {
            // Add code here...
         * The activate method will be called when the feature is activated. The
         * Application Lifecycle Event listener will be called on application
         * being started and resumed.
        public void activate() {
            // Add code here...
         * The deactivate method will be called when the feature is deactivated. The
         * Application Lifecycle Event listener will be called on application
         * being hibernated.
        public void deactivate() {
            // Add code here...
        private void InitDB() {
            try {
                System.out.println("!!!!!!!!!!!!!!InitDB Start!!!!!!!!!!!!!!");
                ClassLoader cl = Thread.currentThread().getContextClassLoader();
                InputStream is = cl.getResourceAsStream(".adf/META-INF/hr.sql");
                if (is == null) {
                    System.err.println("###### Could not look up : /META-INF/hr.sql");
                    return;
                BufferedReader bReader = new BufferedReader(new InputStreamReader(is));
                List stmts = new ArrayList();
                String strstmt = "";
                String ln = bReader.readLine();
                while (ln != null) {
                    if (ln.startsWith("REM") || ln.startsWith("COMMIT")) {
                        ln = bReader.readLine();
                        continue;
                    strstmt = strstmt + ln;
                    if (strstmt.endsWith(";")) {
                        System.out.println(strstmt);
                        stmts.add(strstmt);
                        strstmt = "";
                        ln = bReader.readLine();
                        continue;
                    ln = bReader.readLine();
                DBConnectionFactory.getConnection().setAutoCommit(false);
                for (int i = 0; i < stmts.size(); i++) {
                    Statement pStmt = DBConnectionFactory.getConnection().createStatement();
                    pStmt.executeUpdate((String)stmts.get(i));
                DBConnectionFactory.getConnection().commit();
                System.out.println("!!!!!!!!!!!!!!InitDB Done!!!!!!!!!!!!!!");
            } catch (Exception e) {
                e.printStackTrace();
    }Hope this is what you were looking for
    Frank

  • Data sync between oracle and sql server

    Greetings Everyone,
    Your expert views are highly appreciable regarding the following.
    We at work are evaluation different solutions to achieve data synchronization between oracle and sql server data bases. Data sync i mentioned here is for live applications. We are runnign oracle EBS 11i with custom applications and intending to implement a custom software based on .NET and SQL Server. Now the whole research is to see updates and data changes whenever happens between these systems.
    I googled and found Oracle Golden Gate, Microsoft SSIS, Wisdom Force from Informatica....
    If you can pour in more knowledge then it's great.
    Thank You.

    Most of the work involved has to be done through scripts and there is no effective GUI to implement OGG.However using commands is not vey togh and they are very intutive.
    These are the steps, from a high level:
    1.Get the appropriate GG Software for your source and target OS.
    2.Install GG on source and target systems.
    3.Create Manager and extract processes on source system
    4.Create Manager and replicat processes on target system
    5.Start these processes.
    First try to achieve uni-directional replication. Then Bi-directional is easy.I have implemented bi-directional active active replication using Oracle DBs as source and target. Refer to Oracle installation and admin guides for more details.
    Here is a good article that may be handy in your case.
    http://www.oracle.com/technetwork/articles/datawarehouse/oracle-sqlserver-goldengate-460262.html
    Edited by: satrap on Nov 30, 2012 8:33 AM

  • SQL Azure Data Sync 'Refresh Schema' Not Working

    I am trying to setup SQL Azure sync from my core database to a reporting database (both SQL Azure).  I successfully setup sync with my secondary (and smaller schema) database.  When I try to define the Sync rules and hit Refresh Schema it never
    finishes.  I've been trying to do this off/on for the last ~3 months so I don't think it is an intermittent issue.
    SyncGroup - 9ea034c4-8fc6-43e8-a12f-a1e3d1479e25_EastUS
    When I look at my web console I see:
    Failed to load resource: the server responded with a status of 500 (Internal Server Error): https://manage.windowsazure.com/DataSync/RefreshCloudDbSchema
    Similar (same issue?) from Sept 20, 2013
    http://www.networksteve.com/forum/topic.php/SQL_Azure_Data_Sync_%27Refresh_Schema%27_Not_Working/?TopicId=41473&Posts=0
    Thanks, Aaron

    Per https://msdn.microsoft.com/en-us/library/azure/jj590380.aspx?f=255&MSPPError=-2147217396 I had (2) columns that had over 50 characters in length preventing the page from loading.
    Once they were removed the schema was able to refresh.

Maybe you are looking for