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
Description:RemoveSqlCmdStatements = true will create a wrong script, when certain publish profile settings are set to true.
Additional information:
The setting CreateNewDatabase of the publish profile will add a USE [master] and more to the created script, after which the current database will be dropped, if it exists, and a new one is created. Afterwards, a USE [$(DatabaseName)] will be executed, which will switch the script back to the correct database.
The setting BackupDatabaseBeforeChanges of the publish profile will add a IF (DB_ID(N'$(DatabaseName)') IS NOT NULL) and more to the created script, after which the current database will be backed up. Afterwards, a USE [$(DatabaseName)] will be executed, which will switch the script back to the correct database.
The setting ScriptDatabaseOptions of the publish profile will add multiple database statements that use the $(DatabaseName) variable.
The setting ScriptDeployStateChecks of the publish profile will add multiple database statements that use the $(DatabaseName) variable.
The points above, in combination with the extensions configuration RemoveSqlCmdStatements will cause in a script that will execute not as intended, or won't run at all, depending on the executing application.
The text was updated successfully, but these errors were encountered:
Herdo
changed the title
Invalid configuration combination for CreateNewDatabase and RemoveSqlCmdStatements
Invalid configuration combination for RemoveSqlCmdStatements
Jul 9, 2019
Affected version: 1.2.0
Description:
RemoveSqlCmdStatements = true
will create a wrong script, when certain publish profile settings are set totrue
.Additional information:
CreateNewDatabase
of the publish profile will add aUSE [master]
and more to the created script, after which the current database will be dropped, if it exists, and a new one is created. Afterwards, aUSE [$(DatabaseName)]
will be executed, which will switch the script back to the correct database.BackupDatabaseBeforeChanges
of the publish profile will add aIF (DB_ID(N'$(DatabaseName)') IS NOT NULL)
and more to the created script, after which the current database will be backed up. Afterwards, aUSE [$(DatabaseName)]
will be executed, which will switch the script back to the correct database.ScriptDatabaseOptions
of the publish profile will add multiple database statements that use the$(DatabaseName)
variable.ScriptDeployStateChecks
of the publish profile will add multiple database statements that use the$(DatabaseName)
variable.The points above, in combination with the extensions configuration
RemoveSqlCmdStatements
will cause in a script that will execute not as intended, or won't run at all, depending on the executing application.The text was updated successfully, but these errors were encountered: