jbobst
asked on
Exchange 2003 Questions - Mailbox size and Database size
We run a single Exchange 2003 server. The priv1.edb size is pretty large at 51,076,552 KB (48.71GB). I read an online article that said even though Exchange 2003 SVP2 now can have a database size of 75GB, the default size is still 18GB. Since my database is still running I assume the 18GB default size has been changed at some point in the past, but the article said there should be a DWORD entry in Regedit specifying a new Database Size Limit in GB. I don't have this entry in my registry, so I am wondering how I am still operating on a 48GB database size?
Also, we have a few large mailboxes. One mailbox is over 6GB, and a few others are in the 3GB - 5GB range. Is there a certain point where the mailboxes get so large that it is unhealthy for the server or does mailbox size really make any difference?
I want to separate some mailboxes out into a secondary database on the same server. I have already created a second database, and I will start moving some mailboxes over to it soon, so we don't have all our mailboxes in one huge database. I figure this will help offload the data when I do offline defrags or other maintenance things. Is this a good idea for the most part?
Finally, once I do split out mailboxes into two separate databases, will my public folders be accessible to each database? We rely heavily on public folders and I want to make sure separate databases won't affect the public folder operation.
Thanks!
Also, we have a few large mailboxes. One mailbox is over 6GB, and a few others are in the 3GB - 5GB range. Is there a certain point where the mailboxes get so large that it is unhealthy for the server or does mailbox size really make any difference?
I want to separate some mailboxes out into a secondary database on the same server. I have already created a second database, and I will start moving some mailboxes over to it soon, so we don't have all our mailboxes in one huge database. I figure this will help offload the data when I do offline defrags or other maintenance things. Is this a good idea for the most part?
Finally, once I do split out mailboxes into two separate databases, will my public folders be accessible to each database? We rely heavily on public folders and I want to make sure separate databases won't affect the public folder operation.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Alan Hardisty
If you have Exchange 2003 Standard - you can't add another Database, but if you have Exchange 2003 Enterprise, then you can and you also won't suffer the 18Gb limit problem that the Standard version has.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I forgot that we did purchase the Enterprise edition, so that answers the question of database size limit (which is basically unlimited at 8,000 GB).
Yep - that's why your database is still mounted :)
ASKER
So at this point, since I have the Enterprise edition, I really don't need to be concerned with size limits. Even the 6GB mailbox sizes are ok, although probably slow in the client experience.
Exactly - you are free from the regular constraints that the Stabdard version imposes and 6gb, whilst large for some people, isn't massive for others, as long as it isn't causing problems with anything, you should be fine.