k-335975 (11/10/2011)
I just see the letter of mount point and not underlying disks in the instance list of above counters
you're looking for volumes not disks. They are not actual disks within Windows, they are formatted volumes
CDA (11/10/2011)
So, the one limitation, that I still see with mount points, is still doing any kind of logical detection of free-space.Say I have a stub drive (drive letter) that's 500mb
xp_fixeddrives will ONLY see the stub drive freespace; it doesn't matter if I have mount points of 2 TB of space underneath it.
some vendor apps fail to install, saying there's not enough free space to complete installation based on this.
the only way I've figured out around this is to drop down into powershell and
gwmi win32_volume|where-object {$_.filesystem -match "ntfs"}|ft name,capacity,freespaceAnyone know of a way (or i'd like sql to have something built-in) to figure this out within TSQL?
you can either use
wmic volume get name, capacity, "free space"
or view through explorer but you'll need to add the extra columns in the explorer window first
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉