You may run into issues creating tables with the correct dbo schema when running the SQL Scripts manually.
This can happen if the Default Schema being used is something other than dbo.
A symptom of this would be seeing the table created something like nondboschema.ASCMPackageData instead of dbo.ASCMPackageData.
This can break the proper execution of scripts manually and if ignored could affect the creation of the database properly.
A solution to this would be to set the user's default schema used to dbo.
This SQL statement can be used and added to the beginning of the adminstudio SQL scripts given to set the schema to dbo:
ALTER USER [DOMAIN\USERNAME] WITH DEFAULT_SCHEMA=dbo EXECUTE AS USER='DOMAIN\USERNAME'
This SQL statement can be used to check the schema used:
Here is a link to our documentation on Creating New Application Catalogs Using Scripts.