Allow schema renaming for internal state tables

[sylvaingirardbe]

Problem
We have a logic app with SQL trigger and a function with a SQL trigger running against the same database. Both use the internal state tables. The problem is that they seem to be having different requirements regarding the schema. The SQL trigger on the function adds a not nullable LastAccessTime column which is not used by the SQL trigger on the logic app, making it fail. We now manually changed the column to be nullable. However that's not something that you'd want to do.

Solution
A solution to this problem would be to allow for a configurable schema name on the SQL trigger for functions.

Describe alternatives you've considered
We mitigated the problem by making the LastAccessTime column nullable.

[chlafreniere]

Thanks @sylvaingirardbe. We've put this request to add configuration for schema names on our backlog.

As for why there was a mismatch for the LastAccessTime column between SQL Trigger in Logic Apps vs. SQL Trigger in Function Apps, that's because the version of the SQL Trigger used in Logic Apps is slightly older, and an update to the latest version of the SQL Trigger is in progress by the Logic Apps team. I don't have an ETA available at this time other than to say that it's in progress - deployments are done by the Logic Apps folks themselves.