Will SqlDependency work on Sql Azure?

Hi;
I was told that I cannot get notifications in my C# code when the database
changes. However, SqlDependency looks like it does provide that functionality. So, what's the actual story - will this work?
thanks - dave
What we did for the last 6 months -
Made the world's coolest reporting & docgen system even more amazing

Hi Dave,
SQL Azure currently doesn't support Service Broker functionality. For full list of unsupported functionality, please refer :
http://msdn.microsoft.com/en-us/library/ee336250.aspx
Regards,
Mekh.

Similar Messages

Sql Azure Error :Failed to establish a MARS session in preparation to send the request to the server.

Hi All,
I have a small C# console app.
I have been facing some timeout issue with Sql Azure for a while now.
I now decided to use the retry logic and Reliable connections - using the
TransientFaultHandling Enterprise lib
RetryPolicy myretrypolicy = new RetryPolicy<SqlAzureTransientErrorDetectionStrategy>(3, TimeSpan.FromSeconds(3));
What should be the correct max tries and interval that actually works for SQL AZURE?
The issue i have is when i use this lib i keep getting error :
Failed to establish a MARS session in preparation to send the request to the server.
As anyone used this library successfully in a console app before.If yes can you share some resources or some sample snippet code.
Cheers

Hey there and apologies for the slow response. Is this still an issue for you? And do you still need help?
Thanks Guy

ColdFusion8 works with SQL Server 2008 compatibility level 90?

We're currently is using ColdFusion8 and need to upgrade the database from SQL Server 2000 to 2008. Will ColdFusion8 work with SQL Server 2008 compatibility level 90?

Hi,
ColdFusion 8 is not supported with SQL Server 2008. A list of supported environment is available at http://www.adobe.com/products/coldfusion/pdfs/cf8_systemsupportmatrix.pdf
Regards,
Anit Kumar

Error deploying data tier application to SQL Azure at "Registering metadata for database" step ... should I care?

I'd like to move an on-premesis SQL Server Database to SQL Azure. I've used SQL Mgmt Studio to Extract Data Tier Application and save my db as a dacpac file. Now I'm connected to my Azure server and I've chosen to Deploy Data Tier Application. I select my
dacpac and the deploy starts but then on the last step "Registering metadata for database" it times out. I've tried it a couple of times and each time the deployed database is there and appears to be fully populated, but I'm not sure if I can ignore
that error and continue. What is supposed to happen in that step, and should I expect it to fail when deploying to SQL Azure?
I'm following the steps here http://msdn.microsoft.com/en-us/library/hh694043.aspx in the Using Migration Tools > Data-tier Application DAC Package section, except that to deploy there's no SQL Mgmt Studio > Object Explorer [server]
> Management >"Data Tier Applications" node, so I'm deploying by right-clicking on the server name and choosing "Deploy Data-tier Application".
My (total) guess here is that it's deployed the database fine and it's doing whatever magic happens when you register a data tier application, except that it's not working for SQL Azure.
I'm running against a server created for the new Azure service tiers, not against a Web/Business edition server.
The full details of error I get are below.
thanks,
Rory
TITLE: Microsoft SQL Server Management Studio
Could not deploy package.
Warning SQL0: A project which specifies SQL Server 2008 as the target platform may experience compatibility issues with SQL Azure.
(Microsoft.SqlServer.Dac)
ADDITIONAL INFORMATION:
Unable to register data-tier application: Unable to reconnect to database: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft.Data.Tools.Schema.Sql)
Unable to reconnect to database: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft.Data.Tools.Schema.Sql)
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.9213&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
The wait operation timed out
BUTTONS:
OK

Hello,
The registration process creates a DAC definition that defines the objects in the database, and register the DAC definition in the master system database in Windows Azure SQL Database.
Based on the error message, there is timeout error when connect to SQL Database. Did you deploy a large database? When move large data to Azure SQL Database, it is recommended to use SQL Server Integration Services (SSIS) and BCP utility.
Or you can try to create a client application with the Data-Tier Application Framework (DACFx) client tool to import database and handle connection loss it by re-establish the connection.
Reference: http://sqldacexamples.codeplex.com/
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Mangage SQL Azure is not working

Hi Azure team,
I have installed Google chrome in my laptop, but i cant open sql azure using management portal in azure.
I verified silver light is enabled in chrome.
Kindly let me know what will be the issue and how to open SQL azure from manage portal ?

Hi Saravanabharathi,
According to your description, you could not open SQL Azure via Windows Azure Platform Management Portal in Google chrome. In theory, because the Windows Azure Platform Management Portal
is built on Silverlight, you can view, monitor and manage the exposed aspects of SQL Database with any browser using the web management tool.
You need to first sign in with the Windows Live ID that you’ve associated to your Windows Azure account. You can post error message or detail for analysis. Or
I recommend you try to open the Management Portal by using Internet Explorer (IE) 10.0 or higher version of IE. By default, Internet Explorer displays automatically pop-ups that appear as a result of you clicking a link or button.
Now, to reach the new management portal, you need go to:
http://windows.azure.com .
For more information about using the Database Manager from the Management Portal, you can review the following articles.
http://blogs.msdn.com/b/sqlazure/archive/2010/12/01/10099203.aspx
https://social.technet.microsoft.com/wiki/contents/articles/4723.getting-started-with-windows-azure-sql-database-development.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

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.

SQL Azure - Intermittent The wait operation timed out

I have a website engine which runs a few hundred "white label" sites. It's hosted on Azure with a SQL Azure Business database. Generally everything is fine - it all works and runs at a good speed.
However, throughout the day I get maybe 40 or 50 of the error:
System.ComponentModel.Win32Exception: The wait operation timed out
Please don't refer me to the connectivity blog at http://blogs.msdn.com/b/sqlazure/archive/2010/03/22/9982979.aspx as this seems to refer to problems where you just can't connect. My problem is that it's fine most of the time, but I still get these
intermittently.
This is sometimes on the main database, but we're also using a database for sessions and this gets the errors too. Both databases are on the same server.
I also get errors like:
An existing connection was forcibly closed by the remote host
and:
System.Data.SqlClient.SqlException: The service has encountered an error processing your request. Please try again. Error code 40143. A severe error occurred on the current command. The results, if any, should be discarded.
and, when evil bots are hammering the site:
System.Data.SqlClient.SqlException: Resource ID : 1. The request limit for the database is 180 and has been reached. See 'http://go.microsoft.com/fwlink/?LinkId=267637' for assistance.
Each website can potentially have a Google footprint of around 10,000 pages. The result it that bots are hitting the sites regularly, indexing lots of pages for hundreds of sites. I also have some worker roles doing data work. The database is clearly busy!
I am hoping to add 2 or 3 times the number of sites that I currently have to the "engine".
I am looking at efficiency where possible, but the sites are clearly under a fair load from bots and visitors.
My question is, will one of the upgrades from Business to S2, P1, P2 or P3 resolve these problems? The financial cost of these database instances stagger greatly so I wouldn't want to update and find I'm left with the same problems but am paying many times
more each month.
Thank you in advance.

Hello,
For Web/Business edition database, the maximum limit of concurrent requests is 180. Beyond this limit, you will receive error.
The Max woker threads for Standard(S2) is 100, you should upgrade your database to Permium tier.
The concurrent requests limit of premium database varies depending on the reservation size of a premium database. For example, for P1, the max worker threads is 200.
Reference:Azure SQL Database Resource Governance
Azure SQL Database Service Tiers and Performance Levels
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Create a web site in Visual Studio - fails with SQL Azure V12

Creation of Microsoft Azure Website failed. <Error xmlns="Microsoft.SqlServer.Management.Framework.Web.Services" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><Message>The service objective 'Web' specified is invalid.</Message><InnerError
i:nil="true"/><SqlErrorCode>40804</SqlErrorCode><Severity>16</Severity></Error>
I receive this error after connecting to a database using the Preview Edition of SQL Azure V12 with a service level of 'Basic'
'Web' may need to be changed to 'Basic' or 'Standard' depending on the service level. How can I do this?
Regards
David

Hi,
Thanks for posting here.
Upgrading Web and Business Databases
Upgrading Web or Business databases to a new service tier/performance level does not take the database offline. The database will continue to work through the upgrade operation. At the time of the actual transition to the new performance level temporary
dropping of the connections to the database can happen for a very small duration (typically measured in seconds). If an application has transient fault handling for connection terminations then it is sufficient to protect against dropped connections at the
end of the upgrade.
Upgrading a Web or Business database to a new service tier involves the following steps:
Determine service tier based on feature capability
Determine an acceptable performance level based on historical resource usage
Why does existing performance for my Web or Business database map to the higher Premium levels?
Tuning your workload to fit a lower performance level
Upgrade to the new service tier/performance level
Monitor the upgrade to the new service tier/performance level
Monitor the database after the upgrade
Refer:
http://azure.microsoft.com/en-us/documentation/articles/sql-database-upgrade-new-service-tiers/
https://msdn.microsoft.com/en-us/library/azure/dn741336.aspx
Hope this helps you.
Girish Prajwal

SQL Azure: More Intermittent Timeouts

Hi guys,
We have a set of 5 online auction systems running on Windows Azure & SQL Azure. Each system consists of a single web worker and one or more web roles. Each system is using ASP.NET MVC 3 and Entity Framework, Repository Pattern and StructureMap.
The worker role is responsible for housekeeping and runs two groups of processes. One group is run every ten seconds, the other every second. Each process will likely run a database query or stored procedure. These are scheduled with Quartz.net
The web role serves the public interface and back office. Among other basic crud functionality, both of these provide screens which, when open, will repeatedly call controller methods which will result in execution of stored procedure read-only queries.
The frequency of repetition is about 2-3 seconds per client. A typical use case would be 5 back office windows open, and 25 end user windows open – all hitting the system repeatedly.
For a long time we have been experiencing intermittent SQL timeout errors. Three of the most common ones are:
System.Data.SqlClient.SqlException: 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.)
System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The only predictable scenario is during an auction where a specific controller -> sproc starts to timeout during the event (presumably due to load). All other times the errors appear to be completely random and come in singles, two’s, and three’s etc.
even during periods of user inactivity. For example the system will go 18 hours without an error and then could be 5 – 10 errors from different housekeeping methods, or perhaps a user logged on and viewed their account.
Other info:
I have tried to run the affected queries/sprocs on SQL Azure using both local SSMS and Azure web-based query tool – all seem to execute quickly, 1 second max. Query plans not showing anything too suspicious although I am by no means a SQL query performance
expert, or any other kind of expert for that matter
J
We have wrapped all affected areas in Azure SQL Transient Fault Handling Blocks – but as is discussed here
http://social.msdn.microsoft.com/Forums/en-US/ssdsgetstarted/thread/7a50985d-92c2-472f-9464-a6591efec4b3, they do not catch timeouts, and according to “Valery M” this is for good reason.
We are not storing any session information in the database, although asp.net membership information is stored in the database.
We use 1 “SQL Azure server instance” which hosts all 5 databases, two for staging and three for production. All 5 systems are generally active at the same time although it is unlikely that more than one will be in a state of live load use at any given time.
All web roles, worker roles and the SQL Azure server reside in the same Azure Geographical Region.
Any thoughts on where we should be looking? Would it help giving each system it's own SQL Azure server? ... Failing a solution by ourselves - is it possible to get Microsoft to open a support ticket and take a look under the hood at what’s going on in with
our application – how does one go about this?
Thanks in advance.
Ilan

Ditto.
New website/database (has only been in production for a week or so). The model we have is pretty simple Azure website MVC EF 6.1.1 using a single database in same region as website. I have monitored for and have never found any throttled connections or deadlocks.
What I have tried so far
I bumped the timeout in the connection string to 60 seconds
I changed the web site to Basic and configured the auto scale to max instance size and count
That seemed to help - but then just recently during points of high volume usage (client requests, data in and out, CPU time) I started seeing this error. As I narrow the focus to look at metrics during the exact time of the error it doesn't reflect
the exact peak. For example peak usage may be at 3:45, but the errors occur at 4:30 when the usage is less than 3:45 by a fair amount.
To try to force recreate and see if it was caused by transaction data table locks I ran a query in a transaction block with a WAITFOR delay and then went to the web site and tried to access data that would be locked by that query. That test did generate
an error - but not this specific "semaphore timeout period has expired" - so I don't think it is caused by table locks.
I did notice that when the error happens - it generally happens to one user and then happens multiple times to that one user over the course of what can be a minute or so and in different queries (views). The last analysis showed that pattern for
one user with 2 other users getting the error but just once (and in different views/queries).
USER A - got about 9 of these errors in about 8 different views over the course of a little more than a minute (20:26 to 21:35)
USER B - got 1 (in the same timespan)
USER C - got 1 (in the same time span)
Analysis of the error logs showed it isn't unique to any single view/query or scenario wrt queries. The only clue that makes it less of an intermittent situation is does correspond with usage. However, it doesn't have to be specifically peak usage at the
exact moment - but in a window (within an hour), It makes me wonder if it is the load or just the fact that more usage just increases the odds (I will monitor this relation some more and note the exact metrics).
I am now bumping the timeout in the connection string to 90 seconds and I have changed the database DTU setting to 50

No OFFSET command in SQL Azure?

Note: I am a noob at working with databases, as will likely be clear.
I just upgraded my website to use AzureWebsite's built-in SQL database, upgrading from the SQLCE (.sdf) files that came with the default WebMatrix install. As part of this process, my local database now appears to be a SQLExpress Server (SQL Server
10.50.4000 is what it says in the Server Management Studio).
My OFFSET commands no longer seem to work. It works when I upload the code to Azurewebsites, but locally, the following command:
Line 134: var sqlGetImage = "SELECT * FROM CandidateImage WHERE CandidateID= @0 ORDER BY CandidateID OFFSET BY @1 ROWS";
Line 135: var qImg = gdb.QuerySingle(sqlGetImage,candidate,rndImage);
Returns the following result:
Exception Details: System.Data.SqlClient.SqlException: Incorrect syntax near 'OFFSET'.
I kind of need OFFSET to do what I want to do in a non-terrible way (I want to choose a random candidate out of the possible SELECT results). My question:
1) Is there a way to do what I want to do that works on both platforms? Or alternatively
2) Do I have my development environment set up wrong? It's hard to imagine most people work in a way where this is possible.

Hi Damion Schubert,
According to your description, we need to verify if you want to use offset and fetch to be added after the ORDER BY clause in SQL Azure database and SQL Server database. If yes, in Windows SQL Azure
database, it support ORDER BY with OFFSET and FETCH. However, the form of OFFSET and FETCH is a new T-SQL features in SQL Server2012. Since your local database is SQL Server Express 2008R2, when you use offset function, it will occur error.
Usually, with earlier version of SQL Server , to accomplish paging , we are using the ROW_NUMBER. Since SQL Server 2012 we can use the keywords OFFSET and FETCH where OFFSET is the number of row to skip and FETCH the number of row to take. For more information,
you can review the following article.
http://blog.clicdata.com/2013/05/03/paging-with-sql-server-2012-and-sql-azure/
http://dbadiaries.com/new-t-sql-features-in-sql-server-2012-offset-and-fetch
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Error when running scheduled refresh from SQL Azure data

I have a PowerPivot that connects to a SQL Azure database table. I added the username and password in the PowerPivot connection. It refreshed fine manually straight from PowerPivot. However, when I upload the excel file to Power BI
and I schedule a refresh, it fails with the following error message:
Sorry, something went wrong. Please try again. Correlation ID: d43f07fc-cc0c-461c-b25e-68e866a2a911
I went through this FAQ (http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/scheduled-refresh-faq-HA104180763.aspx#_Toc388441416)
and the steps have me also saving the password in the connection string. However the connection string (under tab Data->Connections) is grayed-out and I am unable to enter the password.
Thanks for your help...

Hi,
When you refresh in Excel client, do you get a prompt for the password?
What worked for me in the past, is the following process:
1. Within PowerPivot, get the data but don't save the password there.
2. Once you get the data go back to Excel, switch to Data ribbon >> Connections, and select the connection(s) that were created in PowerPivot and select to save the password.
3. Refresh the data (it will prompt for the password), save the file.
4. Just to be sure, open the file again, refresh and see that it is not prompting for a password.
GALROY

Alternatives to CONTEXT_INFO on SQL Azure

Hi,
We use CONTEXT_INFO in an application we currently are looking to move to SQL Azure however CONTEXT_INFO is already used to troubleshooting purposes by SQL Azure. Are there any built in alternatives in SQL Azure?
Thanks,

Hmm, still no answer since August of 2010? I hope MS has something for us that use this. I'll give an example I use CONTEXT_INFO in an applicaiton.
I use CONTEXT_INFO to prevent users from modifying a table using SQL Studio. I do this by setting a CONTEXT_INFO in my c#/vb code like so after a begin transaction, along with other TSQL commands, I have this little guy.
    DECLARE @x varbinary(4); SET @x = cast(-1 as varbinary(4)); SET CONTEXT_INFO @x
update dbo.CusCharges set PaymentAmount=5 where CusChargeAmount=10 and CustomerId=30
So then in a particular table, in the trigger (after update, insert) I have this piece of code (shown below)This will allow my application to update the table, but casual TSQL users which don't know about this won't be able to perform an update to this table directly.This works great, except in Azure-land where sysprocesses is not available. So how can I pass down a special variable to a trigger in the context of a transaction?If course, someone could still use TSQL studio, but they would really need to examine the trigger and know what they are doing. This just prevents thebeginning DBA from wiping out Customer Charges for the past decade in a table (it's happened, which is why I put it in).  declare @SessionNid int
    select @SessionNid = cast(substring(CONTEXT_INFO,1,4) as int) FROM master.dbo.sysprocesses WHERE spid = @@SPID
    if @SessionNid = 0 begin
        raiserror('You cannot directly modify dbo.CusCharges.', 16, 1)
        rollback transaction
        return
    end

What's the advantage of Sql Azure?

Hi all;
We assumed that Sql Azure handled clustering, but apparently that feature is in beta (and has been making no progress for a long time). So what's the advantage of Sql Azure over having a VM we install Sql Server on? Because it looks to me like the VM route
is equivalent or better (better because you don't get the occasional delay).
I'm not trying to be antagonistic here, just trying to understand the utility of Sql Azure.
??? - thanks - dave
What we did for the last 6 months -
Made the world's coolest reporting & docgen system even more amazing

Hi;
First off, we've never found Sql Server all that much work. Installs easily and then we're off and running. I understand people finding create & go a big win, but Sql Server is pretty much that already for us.
Our use case is we are creating a cloud app that we hope to see world-wide use of it. So we want to start located in the US & Europe and use TrafficManager to send apps to the closest server. There are 2 key DB records for all the requests we'll get,
the customer & the user.
The user will tend to be on one continent (but not always). But the customer can have employees (users) on every continent. And for each request coming through, we need to get that customer record fast. Very very fast.
I'm guessing that 95% (or more) of our DB activity will be selects.
Our hope was you had Sql Azure working so it could be instantiated in each data center we have our cloud service and then each is hitting a local DB. But we need it keeping each in-sync with the other because of that customer record (and the user record
in case of TrafficManager switching who they go to because something went down).
This is the one thing we've never been able to get Sql Server (on our servers) to do - sync between instances. So I understand that this is hard (impossible?). But at the same time, I think many have this same need we have.
thanks - dave
What we did for the last 6 months -
Made the world's coolest reporting & docgen system even more amazing

Why does a SQL Azure DACPAC upgrade (via a PowerShell script) consistently take 30min to complete

I created a PowerShell script to upgrade a SQL Azure instance with my latest DACPAC (taken from http://msdn.microsoft.com/en-us/library/ee634742.aspx).
What I have experienced when running my PowerShell script is that it consistently takes approximately 30min to execute. The script is idle for almost half an hour waiting on $dacstore.IncrementalUpgrade($dacName,
$dacType, $upgradeProperties) to return from execution and nothing is printed out on the PowerShell console window. Only right at the end of the half hour does the incremental update start spitting out console messages which inform me that
the upgrade is taking place (essentially it appears that the script has hung for 30min until it finally comes back alive and the script does this consistently every time).
Does it usually take this long for the IncrementalUpgrade to complete and is there supposed to be a 30min period of inactivity/waiting?
Note that I am running the PowerShell script from my local machine which is external to the Azure network.
Thanks for any insight you can give for this, I am hoping that I can reduce this incremental upgrade process to substantially less than 30hr so that my continuous integration build doesn't take so long.

Answer this post
According to Microsoft Support this is a known issue and will be fixed in SQL Server 2012 (code named Denali). Here are the details from Microsoft Support:
It’s a known issue that using SSMS 2008 or PowerShell to update DAC on SqlAzure is very slow. SQLServer 2008 utilize old extraction engine which run query for every column and small object. This way works well at on-premise server, and meets
SQLServer 2008 original design target. However, when managing the SqlAzure database, the query need be transferred over internet, network latency makes the old extraction becomes inefficient, especially, when network is not good.
Our SQL product team aware this issue and designed new extraction engine to fix it. The new engine is integrated in SQL Server 2012 (code name Denali). Unfortunately, some of the engine behavior may bring break changes to SQL Server 2008. We try
different approach but we can’t relief regression barrier when apply the new engine in the SQL server 2008. Therefore, we don’t have plan to deliver the new extraction engine as hotfix on SQLServer 2008 so far. That will impact the current on-premise
users and operation.

SQL Azure sync service-- absurdly slow and fails after a few days

Hello. We have been trying to use Azure Data Sync to replicate an on-premise MSSQL database to an SQL Azure database for read-only access by a customer. This was working for a while, but stopped syncing after a couple months(12hr auto-sync schedule) with
no errors in the log. I had to re-create the sync group, but now it takes even longer than originally to try to sync, and never actually completes, as it gets interrupted by bi-weekly server restarts... It used to take a few hours to sync the new data in our
database(which is appended to daily)-- but this time it fails after 4+ days... It was unacceptably slow initially(IMO), but now it's clearly unusable. The original initialization of the data when I first set it up was less than 2 days of syncing.
It seems there is a throttle on the Azure sync service. Is this true? Would it be best to clear the SQL Azure database now and re-sync? Is there a way to pre-load the SQL Azure database with MSSQL on-premise data via a SQL backup file or something?
Please advise. Thank you.

when you re-created the sync group, does the member databases/hub database have pre-existing data?
when synching a sync group for the first time, make sure databases don't contain the same set of data, otherwise, you will run into conflicts which will completely slow down your sync...
I deleted the initial sync group because it wasn't syncing(auto or on-demand), nor creating a log entry with an error indicating why.
So, I simply deleted the sync group and re-created it with the same exact databases and settings. I did not delete all data in the SQL Azure database-- I was under the assumption that the sync service, with the tracking tables were smart enough to not get
confused with pre-existing data, but apparently that's not how this works?
I obviously can't delete the data in the source database(MSSQL on-premise), but I could delete the tables in the SQL Azure database if that's supposed to fix the problem-- then we'll just have to wait multiple days for it to be completely re-initialized,
hopefully without error... Is there a way to seed the data in some way to prevent this extremely log first sync?
Thank you for your help.

Will SqlDependency work on Sql Azure?

Similar Messages

Maybe you are looking for