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
When scanning source tables from an Azure MS SQL Database, each table name starts with dbo.[table name] as shown in the screenshot below:
The tabs for the whiteRabbit scan report also contain the leading dbo. When loaded into RabbitInAHat and generating a TestFramework (see below) the tables names still contain the leading dbo.
When setting up the unit testing and generating the insert.sql file the generated script is resulting in a error due to the leading dbo. before the table name
Is there anyway to stop the schema. name from being added to the table names in an Azure MS SQL Database as it seems to be resulting in an error in the unit testing stage?
Thanks,
Solmaz
The text was updated successfully, but these errors were encountered:
Hi,
When scanning source tables from an Azure MS SQL Database, each table name starts with dbo.[table name] as shown in the screenshot below:
The tabs for the whiteRabbit scan report also contain the leading dbo. When loaded into RabbitInAHat and generating a TestFramework (see below) the tables names still contain the leading dbo.
When setting up the unit testing and generating the insert.sql file the generated script is resulting in a error due to the leading dbo. before the table name
Is there anyway to stop the schema. name from being added to the table names in an Azure MS SQL Database as it seems to be resulting in an error in the unit testing stage?
Thanks,
Solmaz
The text was updated successfully, but these errors were encountered: