=== 15e.1 Modules containing SET TIME ZONE
module|type_desc
------|---------
tzlab.usp_Nested|SQL_STORED_PROCEDURE
tzlab.usp_ReportInTokyo|SQL_STORED_PROCEDURE
tzlab.usp_SetThenFail|SQL_STORED_PROCEDURE
tzlab.trg_TriggerTarget_Audit|SQL_TRIGGER

=== 15e.2 Dropping them (recreated at the end)
DROP PROCEDURE [tzlab].[usp_Nested]; DROP PROCEDURE [tzlab].[usp_ReportInTokyo]; DROP PROCEDURE [tzlab].[usp_SetThenFail]; DROP TRIGGER [tzlab].[trg_TriggerTarget_Audit]; 
=== 15e.3 Export BACPAC again
Processing Table '[tzlab].[Orders]'.
Processing Table '[dbo].[ErrorLog]'.
Successfully exported database and saved it to file 'results/15_artifacts/cst_no_set_tz_modules.bacpac'.
Time elapsed 0:00:13.28
--- TIME_ZONE in bacpac model.xml:
5055-		</Element>
5056:		<Element Type="SqlGenericDatabaseScopedConfigurationOptions" Name="[TIME_ZONE]">
5057-			<Property Name="GenericValueType" Value="2" />
5058-			<Property Name="GenericValue" Value="Central Standard Time" />
5059-		</Element>
=== 15e.4 Import scripting is not executed here (a BACPAC import needs a NEW database).
    sqlpackage /a:Script only accepts a .dacpac, so the scripted TIME_ZONE line is shown by 15c (same script generator).
=== 15e.5 Recreate the dropped modules (re-run scripts/07_module_scope.sql)
modules_with_set_time_zone
--------------------------
4