Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Utilize Azure Functions as CLR replacement for Azure SQL Database #188

Open
OsirisDBA opened this issue Feb 3, 2023 · 1 comment
Open

Comments

@OsirisDBA
Copy link

With the introduction of the ability to call sp_invoke_external_rest_endpoint from all Azure SQL Databases this leads to a possible solution to the CLR issue where the CLR function could be reimplemented as a set of Azure Functions.

I see a couple areas of concern.

  • Is it even possible to duplicate the functionality in Azure Functions
  • How much duplication and complexity would this introduce
  • How would this be deployed and maintained for end users
@asos-martinsmith
Copy link

Personally I now see little value of running tSQLt tests in Azure.

I find that I can just use SQL Server 2022 localdb for all my testing needs.

It does mean that potentially I can't quite use the latest and greatest syntax as and when new syntax gets introduced in Azure but I'm OK with that for the convenience of being able to run on my local machine without having to provision something in Azure.

It is also true that there might be some behavioural differences between localdb and Azure but I don't expect those to impact the unit testing of business logic that tSQLt is for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants