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
No error: silent drop unless -Verbose switch is used
With -Verbose: Performing the operation "Dropping all objects created by Ola's Maintenance Solution" on target "server02".
If -LogToTable is specified the CommandLog table will still be dropped, but a new version of the table will be created. Without param -LogToTable param -ReplaceExisting will not replace the CommandLog table. The table is simply dropped, creating a breaking condition as the Ola sprocs will not fire without the table present if @LogToTable = 'Y' is in use.
Please confirm that you are running the most recent version of dbatools
2.1.28
Other details or mentions
Ola Hallengren Maintenance Solution stored procedures are replaced by newer versions, CommandLog table should be left alone if it already exists. Perhaps a separate switch(es) for less destructive behavior is warranted?
What PowerShell host was used when producing this error
PowerShell Core (pwsh.exe)
PowerShell Host Version
Name Value
PSVersion 7.4.6
PSEdition Core
GitCommitId 7.4.6
OS Microsoft Windows 10.0.14393
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
SQL Server Edition and Build number
Microsoft SQL Server 2019 (RTM-CU29-GDR) (KB5046860) - 15.0.4410.1 (X64)
Oct 23 2024 15:50:49
Copyright (C) 2019 Microsoft Corporation
Standard Edition (64-bit) on Windows Server 2019 Datacenter 10.0 (Build 17763: ) (Hypervisor)
.NET Framework Version
.NET 8.0.10
The text was updated successfully, but these errors were encountered:
Verified issue does not already exist?
I have searched and found no existing issue
What error did you receive?
No error: silent drop unless -Verbose switch is used
With
-Verbose
:Performing the operation "Dropping all objects created by Ola's Maintenance Solution" on target "server02".
Steps to Reproduce
If
-LogToTable
is specified the CommandLog table will still be dropped, but a new version of the table will be created. Without param-LogToTable
param-ReplaceExisting
will not replace the CommandLog table. The table is simply dropped, creating a breaking condition as the Ola sprocs will not fire without the table present if@LogToTable = 'Y'
is in use.Please confirm that you are running the most recent version of dbatools
2.1.28
Other details or mentions
Ola Hallengren Maintenance Solution stored procedures are replaced by newer versions, CommandLog table should be left alone if it already exists. Perhaps a separate switch(es) for less destructive behavior is warranted?
What PowerShell host was used when producing this error
PowerShell Core (pwsh.exe)
PowerShell Host Version
Name Value
PSVersion 7.4.6
PSEdition Core
GitCommitId 7.4.6
OS Microsoft Windows 10.0.14393
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
SQL Server Edition and Build number
Microsoft SQL Server 2019 (RTM-CU29-GDR) (KB5046860) - 15.0.4410.1 (X64)
Oct 23 2024 15:50:49
Copyright (C) 2019 Microsoft Corporation
Standard Edition (64-bit) on Windows Server 2019 Datacenter 10.0 (Build 17763: ) (Hypervisor)
.NET Framework Version
.NET 8.0.10
The text was updated successfully, but these errors were encountered: