<div>
The best practice part was relatively complete but the &quot;feasibility&quot; part and the best way to implement part was missing.<br />
<br />
But it was usefull to begin with, tx!
</div>


The best practice part was relatively complete but the "feasibility" part and the best way to implement part was missing.

But it was usefull to begin with, tx!

<div>
<div class="content wysiwyg-content">
Hi,<br />
I have upgrade the store on my Exchange 2003 server and now have plenty full of space available. The Private store has right now a quota at 100mb for each users. I would like to raise it to 2-5gb PER user.<br />
I am looking for the best practices and feasibility of that change of configuration.<br />
Should I split my 200 users into 200 storage's groups. Keep all in the same storage group but create xx number of stores. Or would I need more then one Exchange server for this. <br />
We need to consider also the feasibility in case of a database corruption.<br />
If there are limitations, would Exchange 2010 have any advantages?<br />
<br />
tx!<br />

</div>
</div>


Hi,
I have upgrade the store on my Exchange 2003 server and now have plenty full of space available. The Private store has right now a quota at 100mb for each users. I would like to raise it to 2-5gb PER user.
I am looking for the best practices and feasibility of that change of configuration.
Should I split my 200 users into 200 storage's groups. Keep all in the same storage group but create xx number of stores. Or would I need more then one Exchange server for this. 
We need to consider also the feasibility in case of a database corruption.
If there are limitations, would Exchange 2010 have any advantages?

tx!


Exchange 2003 Private db maximum size

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.