Gordon said:
No it's not - from the bottom of the KB page:
"Note You can set the UNICODE limits beyond the values that are
listed in the table. However, we do not recommend doing this because
performance can decrease"
Yep, you are right that the physical maximum can be set to a much
higher value. I wouldn't recommend it, though. I don't recommend
putting a 600HP V8 into a Geo Metro to make a suicide car (screech,
zoom, SPLAT). It's up the user if they want to configure outside the
valid data range for PST file size. There are plenty of folks that
like to tweak with the TCP configuration in the registry and then have
to figure out why it doesn't work anymore.
You first run into the 2TG limit (for both file and volume size) after
which you have to use dynamic volumes to get up to the 256GB limit
(and using a non-standard 65K cluster size; 16TB if you use the
standard 4K cluster size). Very few users employ dynamic volumes.
Except for extreme rare setups, you'll won't get more than 2TB for the
size of the PST file. The user might also want portability to move
their .pst file onto storage media which only supports FAT32 so the
max file size there is 4GB (and only 2GB for FAT16).
Due to the indexing for the records within the Unicode-enabled
database (i.e., its records can handle multi-byte Unicode characters),
I'm sure there is a pretty good reason why performance would
significantly drop for a PST database file that exceeds 20GB, and it
probably drops exponentially. You could probably run an inadequate
computer using Vista's Aero desktop and enable all visual gimmickry
but that doesn't mean you'll be happy with the lack of responsiveness
from that host. Also, there is no PST4GB.exe, PST20GB.exe, or
PST2TB.exe repair utilities. The bigger the PST file, the more likely
the user will lose data and a LOT more data, too. I don't recommend
going outside the recommended range of values. I wouldn't be
surprised if there is a gotcha that Microsoft isn't revealing about
PST files that exceed 20GB. Considering that a 1-byte change to a 2TB
..pst file would require it all get backed up even in an incremental
[logical file] backup, those backups could take ages to complete.
If the user had 4GB of e-mail, personally I think it is about time
that user rethinks what e-mails they need to keep and start consider
using archiving.