Should validation cmdlets disable verbose logging at first warning?
SteveClement
Posts: 1 New member
I'm trying to debug a larger problem (namely, DLM Automation not deploying objects in the correct order), so I've added the -Verbose flag to the Invoke-DlmDatabaseSchemaValidation command.
The verbose output displays as expected (namely, displaying an entry for each item being created) right up until it hits the first object in error. At that point, all verbose output is swallowed, and the only thing being displayed is subsequent warnings. This is consistent across multiple databases I'm testing.
Is this expected behavior, and if so, is there a better way to debug the order in which objects are being executed? If not, is this just a straight bug?
The verbose output displays as expected (namely, displaying an entry for each item being created) right up until it hits the first object in error. At that point, all verbose output is swallowed, and the only thing being displayed is subsequent warnings. This is consistent across multiple databases I'm testing.
Is this expected behavior, and if so, is there a better way to debug the order in which objects are being executed? If not, is this just a straight bug?
Answers
If you put $DebugPreference = 'Continue' at the start of your Powershell script you will get more detail.
Other than that I recommend using SQL Compare: just compare your scripts folder against an empty database and select the option to generate the update script.
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools