Export of Azure SQL databases not possible because of Private views

[shiwaretsu]

I executed the tSQLt.class.sql file on an Azure SQL database. It worked well and I was able to use it there.

But when I wanted to export the database (via "Generate Scripts" in SQL Server Management Studio or directly from the Azure portal), I got errors like:

Error SQL71501: Error validating element [tSQLt].[Private_GetFullTypeName]: Function: [tSQLt].[Private_GetFullTypeName] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [tSQLt].[Private_SysTypes].[schema_id] or [tSQLt].[Private_SysTypes].[T].

Error SQL71501: Error validating element [tSQLt].[Private_ScriptIndex]: Function: [tSQLt].[Private_ScriptIndex] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [tSQLt].[Private_SysIndexes].[I] or [tSQLt].[Private_SysIndexes].[type].

I tried on my local machine and did not encounter the problem there.

Note: in both cases (on Azure and locally) I didn't execute the SetClrEnabled.sql file, because it does not work on Azure.

Versions:
tSQLt: 1.0.5873.27393
Azure DB: Microsoft SQL Azure (RTM) - 12.0.2000.8 Jun 7 2017 01:09:35

[Mja101]

Did you ever find a solution to this problem? I am currently experiencing the same issue.

[shiwaretsu]

Did you ever find a solution to this problem? I am currently experiencing the same issue.

@Mja101 Unfortunately no. At the moment we delete tSQLt tables and objects before the export.

[lizbaron]

@shiwaretsu, can you say more about your use case for exporting the database from Azure SQL DB?

[shiwaretsu]

@shiwaretsu, can you say more about your use case for exporting the database from Azure SQL DB?

Hi @lizbaron we added the tSQLt classes to some of our test databases, to run our tests daily/weekly. Sometimes when a bug is found, we need to quickly get a copy of the test database, to easily reproduce the problem locally.

[Lochrine]

Hello. Any resolution here? Facing the same problem.

[Mja101]

@michael, Best practice of tSQLt suggested that the framework should not be used on production databases. Based on that, during our CICD pipeline, we install Azure SQL onto a docker image, install the framework, run the tests. As a last step in the pipeline we uninstall the tSQLt.

…

On Sat, 2 Mar 2024, 3:47 pm Michael McLaughlin, ***@***.***> wrote: Hello. Any resolution here? Facing the same problem. — Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHFNWPSQXHDETWXHYV6OOHDYWE4VBAVCNFSM4DSHHBDKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJXGQZDEOBXHEYA> . You are receiving this because you were mentioned.Message ID: ***@***.***>