Azure SQL is not supported
See original GitHub issueDB_ID always returns NULL for azure sql (single database).
We could instead use
"IF NOT EXISTS(SELECT * FROM master.sys.databases WHERE name='Notification') CREATE DATABASE Notification;"
The USE command is also not allowed on azure sql single database which is used by ChangeDatabase: https://github.com/EdwinVW/pitstop/blob/master/src/NotificationService/Repositories/SqlServerNotificationRepository.cs#L44
We can replace this with closing the sql connection to master and creating a new sql connection to the target database.
This does work on azure sql. Would this change be acceptable?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Solved: SQL Azure is not supported by the SQL data extensi...
I can´t publish my paginated report in Power BI Service because this error message happen: SQL Azure is not supported by the SQL...
Read more >Resolving T-SQL differences-migration - Azure SQL Database
In this article. Overview; T-SQL syntax statements with partial differences; T-SQL syntax not supported in Azure SQL Database; Full T-SQL ...
Read more >SQL Server features that are not supported by Azure SQL ...
SQL Server features that are not supported by Azure SQL Database · Common Language Runtime (CLR and CLR User-Defined Types) · Database Mirroring...
Read more >If "USE statement is not supported", for Azure Databases, how ...
I have some Azure databases. I regularly use Management Studio to execute some commands. As expected, after some idle time in a query...
Read more >Transact-SQL syntax not supported in Azure SQL Database
Most Transact-SQL features that applications use are fully supported in both Microsoft SQL Server and Azure SQL Database.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
See commit https://github.com/EdwinVW/pitstop/commit/f243358e7b66e2d341905df7d142f32e1dd0912e
I’ve also changed the SqlServerWorkshopPlanningEventSourceRepository of the WorkshopManagementAPI so its structure is identical to that of the other two repos.
Yes, it makes sense to explicitly open the connection. I’ll create a fix for that.