Sqltabledependency (or something similar) with SQL azure

Question

5.00/5 (1 vote)

See more:

I'm looking at moving a system to an Azure SQL database - but i require the broker service to be running so a service can detect changes using SqlTableDependency.

I don't want to poll the database every minute - i would prefer a 'proper' solution.

Has anyone any suggestions - as I've googled it and i've not seen anything yet....

Or is there a completely different way to do using an API from SQL ( if such a thing exists )

Thanks

What I have tried:

I have tried researching this - but looking for suggestions from people who may have already done it to see if it works OK.

Posted 25-Jan-18 4:25am

pokemonjohn

Updated 14-Feb-18 21:49pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Herman<T>.Instance · Accepted Answer · 2018-02-14T21:49:00

Biggiest issue: You cannot enable the Service Broker on an AZURE SQL Database

see: Resolving T-SQL differences-migration-Azure SQL Database | Microsoft Docs[^]

part:
Transact-SQL syntax statements with partial differences
The core DDL (data definition language) statements are available, but some DDL statements have extensions related to disk placement and unsupported features.

CREATE and ALTER DATABASE statements have over three dozen options. The statements include file placement, FILESTREAM, and service broker options that only apply to SQL Server. This may not matter if you create databases before you migrate, but if you are migrating T-SQL code that creates databases you should compare CREATE DATABASE (Azure SQL Database) with the SQL Server syntax at CREATE DATABASE (SQL Server Transact-SQL) to make sure all the options you use are supported. CREATE DATABASE for Azure SQL Database also has service objective and elastic scale options that apply only to SQL Database.

You cannot 'sp_configure options and RECONFIGURE' the database so you cannot enable the .NET CLR

it is a pitty