I have a scenario where I start multiple SSIS-packages simultaniously. This is done from SQL-code by, for each package first prepare using[SSISDB].[catalog].[create_execution], [SSISDB].[catalog].[set_execution_parameter_value], [SSISDB].[catalog].[set_object_parameter_value] and[SSISDB].[catalog].[set_execution_property_override_value]. After that [SSISDB].[catalog].[start_execution]
Problem I have is frequent deadlocks. I have then found there to be a known issue i MSSQL2014 and MSSQL2016 which are supposedly fixed in CU's. https://support.microsoft.com/en-gb/help/4016804/fix-deadlocks-occur-in-ssisdb-when-you-run-multiple-ssis-packages-in-s
For myself I also made a workaround by putting in delays in the code. Parctically making sure to avoid exact simultanious start of the packages.
Now moving forward by upgrading to MSSQL2017, more specifically 14.0.2002.14, I had hope that this problem should have been resolved but I find the problem to still be there.
Looking closer at the deadlock I can pinpoint the problem to [SSISDB].[catalog].[set_object_parameter_value]and the update...
UPDATE [internal].[object_parameters]
SET [default_value] = @parameter_value,
[sensitive_default_value] = NULL,
[base_data_type] = @parameter_type,
[value_type] = @value_type,
[value_set] = 1,
[referenced_variable_name] = NULL
WHERE parameter_id = @parameter_i
I have checked the later CU's for MSSQL 2017 but not found anything exactly targeting the above, althogh KB4466491 CU13 also seems to be about parallell SSISpackages. Also Im not sure that the problem I have is exactly the same as the ones fixed in 2014/216. I have compared procedure [SSISDB].[catalog].[set_object_parameter_value] and table [SSISDB].[internal].[object_parameters] and found no differences between 2016 and 2017 so if this was the same problem as in 2014/216 I dont understand what should have been fixed. So question is if this is known and perhaps any recomended workaround.