Get-DbaInstanceAudit: MaximumFileSizeUnit shows Mb rather than MB

[ReeceGoding]

Verified issue does not already exist?

I have searched and found no existing issue

What error did you receive?

No error, just wrong output. It appears that the file size returned by Get-DbaInstanceAudit reports Mb rather than MB.

Steps to Reproduce

$primary = Connect-DbaInstance -SqlInstance Whatever
$StupidPath = (Get-DbaDefaultPath -SqlInstance $primary).Log                                                                    
Invoke-DbaQuery -SqlInstance $primary -Query "CREATE SERVER AUDIT NewAudit TO FILE (FILEPATH = '$StupidPath', MAXSIZE = 100 MB)"
Get-DbaInstanceAudit -SqlInstance $primary -Audit NewAudit   

Incidentally, I would like to know if there is a better way to write this. I'm not aware of a dbatools wrapper for CREATE SERVER AUDIT.

Please confirm that you are running the most recent version of dbatools

2.7.27

Other details or mentions

No response

What PowerShell host was used when producing this error

PowerShell Core (pwsh.exe)

PowerShell Host Version

Name Value

---

PSVersion 7.6.0-preview.6
PSEdition Core
GitCommitId 7.6.0-preview.6
OS Debian GNU/Linux forky/sid
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.4
SerializationVersion 1.1.0.1
WSManStackVersion 3.0

SQL Server Edition and Build number

Microsoft SQL Server 2025 (RTM-CU3) (KB5077896) - 17.0.4025.3 (X64) …

.NET Framework Version

.NET 10.0.0

[andreasjordan]

@claude please have a look at this issue.

[claude]

Claude finished @andreasjordan's task in 59s —— View job • claude/issue-10292-20260328-1818 • Create PR ➔

---

Fix implemented

• Gather context and understand the issue
• Find the relevant code in Get-DbaInstanceAudit
• Fix the MaximumFileSizeUnit casing issue
• Commit and push changes

Root cause

The SMO MaximumFileSizeUnit property returns enum values with mixed case (Mb, Gb, Tb) which is just how the AuditFileSizeUnit enum is defined in SMO. The fix maps these to the correct uppercase abbreviations (MB, GB, TB) using a switch statement and overrides the property via Add-Member.

Changes made

In public/Get-DbaInstanceAudit.ps1 (line 117-129):

• Added a switch block to convert Mb → MB, Gb → GB, Tb → TB
• Added an Add-Member call to override the MaximumFileSizeUnit NoteProperty with the corrected value

|

[andreasjordan]

@ReeceGoding I'm not sure if we want to change that. This is the way the SMO outputs it and we should take it that way. PowerShell is case insensitive so it should not matter.

Do you still want this to be changed?

[ReeceGoding]

@andreasjordan I think it should be changed. If SMO reports the unit as Mb, then SMO is wrong. Are you proposing that it should be fixed upstream instead?

[andreasjordan]

@ReeceGoding I would just ignore it. But what do you think @potatoqualitee ?