Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

       How did you like this article? Please vote and let us know.          

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Shannal L. Thomas
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath

 

 
 

PST=BAD! (More Q&A)

By Drew Nicholson, dnicholson@OutlookExchange.com

Why are PSTs Bad?

Troy asks:

I have a question. You mention that - (PST=BAD!). Why? I wanted to know what your reasoning is besides users having more files to backup and manage. I would be open to get your thoughts.

Well, other than the two reasons you give, here are some more:

1) PSTs get corrupted easily.
2) PSTs have a hard limit of 2 gigs.
3) PSTs store information in TWO formats -- the Information Store only one.
4) PSTs do not support Single Instance Storage -- the IS does.
5) PSTs cannot be shared. This means that calendar info cannot be shared.
6) PSTs cannot take advantage of Server Side Rules (I think. Maybe. It depends.)
7) Being on Pacific Time means your friends can call you up and tell you the ending to ER before it even starts. (joke!)
Other well thought out reasons are at http://www.simpler-webb.com/resource/exch_faq.htm.

Click here to go back to my OutlookExchange homepage.


Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Pro Exchange. OutlookExchange.Com and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

© Copyright Pro Exchange, Inc., 2006