You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, super excited to see a recent release! Thanks for the hard work in keeping this thing up to date 馃檹
There are a few issues with the newest version (V1.0.7597.5637) that don't work with Azure SQL when running tSQLt.class.sql:
Msg 40515, Level 15, State 1, Procedure RemoveAssemblyKey, Line 16 [Batch Start Line 192]
Reference to database and/or server name in 'master.sys.sp_executesql' is not supported in this version of SQL Server.
Switching these database-qualified system stored procs to simply sp_executesql seems to resolve the error. This also applies to sp_configure as well.
Msg 10341, Level 16, State 100, Line 1204
Assembly 'tSQLtCLR' cannot be loaded because Azure SQL Database does not support user-defined assemblies. Contact Azure Technical Support if you have questions.
It looks like the issue is probably because older versions had the CLR whitelisted (discussed in #36) and this one has not yet.
I think the remaining downstream errors would be fixed by the above two problems being resolved. I am happy to make a PR for the first set of problems 馃憤
The text was updated successfully, but these errors were encountered:
<dbname>.sys.sp_executesql is executing the code in the context of the <dbname> database. Therefore, the change you suggest changes the behavior of the code. While I can think of a few workarounds for 1, without getting 2 fixed it won't make a difference. We've contacted Microsoft about 2, but without success so far.
First off, super excited to see a recent release! Thanks for the hard work in keeping this thing up to date 馃檹
There are a few issues with the newest version (V1.0.7597.5637) that don't work with Azure SQL when running
tSQLt.class.sql
:Switching these database-qualified system stored procs to simply
sp_executesql
seems to resolve the error. This also applies tosp_configure
as well.It looks like the issue is probably because older versions had the CLR whitelisted (discussed in #36) and this one has not yet.
I think the remaining downstream errors would be fixed by the above two problems being resolved. I am happy to make a PR for the first set of problems 馃憤
The text was updated successfully, but these errors were encountered: