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
Publish-DbaDacPackage - Add CommandTimeout parameter to fix deployment timeouts
Adds a -CommandTimeout parameter (default 0 = no timeout) that is injected
into the DacServices connection string. This fixes failures where complex
post-deployment scripts (e.g. SqlWatch MERGE statements) exceed SqlClient's
default 30-second command timeout.
(do Publish-DbaDacPackage)
Co-authored-by: Andreas Jordan <andreasjordan@users.noreply.github.com>
Copy file name to clipboardExpand all lines: public/Publish-DbaDacPackage.ps1
+11-3Lines changed: 11 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,10 @@ function Publish-DbaDacPackage {
54
54
Enables replacement of SqlCmd variables in the publish profile with their actual values during deployment.
55
55
Use this when your deployment scripts or publish profile contain variables like $(Environment) or $(ServerName) that need to be substituted with environment-specific values.
56
56
57
+
.PARAMETERCommandTimeout
58
+
Specifies the execution timeout in seconds for SQL commands during deployment. Set to 0 for no timeout.
59
+
Defaults to 0. Use this for DACPAC packages with long-running pre/post-deployment scripts that may exceed the default 30-second SqlClient command timeout.
60
+
57
61
.PARAMETERWhatIf
58
62
Shows what would happen if the command were to run. No actions are actually performed.
59
63
@@ -149,7 +153,7 @@ function Publish-DbaDacPackage {
0 commit comments