-
Notifications
You must be signed in to change notification settings - Fork 62
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
[LogicApps Hybrid] Moving all queries to get unprocessed rows to a StoredProcedure #1159
Comments
I think you may be better served by using a stored procedure that you create and interact with change tracking directly. |
The problem with dataplane creating the stored procedure is that it cannot access sql server with identities that user has given to the app. So it would be better if sql extension itself creates the stored procedure at the time of initialization and keda will take care of executing the stored proc on regular intervals. The stored procedure that we checked and works fine is below.
|
Is your feature request related to a problem? Please describe.
This feature request is related to support of SQL trigger scaling when functions host is running in kubernetes and depends on KEDA scalers for scaling.
This is how it works currently.
But in ACA when sql trigger scaling is required it needs KEDA mssql scaler. our initial approach was below.
This works fine for connection string, as the dataplane is using the user's connection string.
But this would not work for managed identity based connection as dataplane is not having the identity of the app.
Dataplane access to SQL server is needed for creating the stored procedure. But if sql extension itself would create the stored procedure, then dataplane would not need to access the sql server.
This would be more cleaner.
Describe the solution or feature you'd like
Moving the queries to get unprocessed rows to a StoredProcedure, So that sql extension creates the stored procedure and this stored procedure can be executed by Keda Scaler as well.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: