-
-
Notifications
You must be signed in to change notification settings - Fork 794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test-DbaDbCompression is completely silent for empty tables #9469
Comments
ahem .... there's no data to test compression so .... what output you'd expect ? |
@niphlod I'd expect some notice, particularly when under |
notice that your table is empty and so there's no way we can test for compression ? |
@niphlod That's good practice, but it's easy to miss such things when you are checking a big number of tables. You end up in a confusing situation where some tables are doing what you expect but others don't. As I recall, |
yeah, my point is understanding what you're asking. |
@niphlod I'm happy with either. |
it's all T-SQL so if it's doable it should be easy |
you may want to try itself, is it this filter ? https://github.com/dataplat/dbatools/blob/development/public/Test-DbaDbCompression.ps1#L218 |
@niphlod Thanks. I may give this a try. My list of open-source work is currently long. |
no worries, it's still a good starting point for anyone who has enough time to look into it. |
Verified issue does not already exist?
I have searched and found no existing issue
What error did you receive?
No error. It's just a case where we silently do nothing. This happens even if
-Verbose
andEnableException
are enabled.Steps to Reproduce
Please confirm that you are running the most recent version of dbatools
Yes. Just updated.
Other details or mentions
No response
What PowerShell host was used when producing this error
Windows PowerShell (powershell.exe)
PowerShell Host Version
Yes. Just updated.
SQL Server Edition and Build number
SQL Server 2019. Was able to replicate on multiple versions.
.NET Framework Version
Just updated.
The text was updated successfully, but these errors were encountered: