tag:blogger.com,1999:blog-3179219424167705024.post1962512523752900043..comments2024-03-21T00:12:28.185-07:00Comments on M365 and AZURE Blog: Recommended mailbox size and Exchange DatabasesOz Casey, Dedealhttp://www.blogger.com/profile/12226180672457689907noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3179219424167705024.post-33425809739408534292012-12-04T13:41:31.803-08:002012-12-04T13:41:31.803-08:00Another reason not to go past 100gig is if you wer...Another reason not to go past 100gig is if you were to run into database corruption issues and had to perform eseutil /p /d and isinteg on a 300gig database. It would take FOREVER! Don't go past 100gig. lol Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3179219424167705024.post-16306518727098602522008-12-19T13:10:00.000-08:002008-12-19T13:10:00.000-08:00Mike as always thanks for the comments,The MS numb...Mike as always thanks for the comments,<BR/><BR/>The MS numbers are only for guidelines and taken from some of the testing. The Reality behind these numbers will change based on various factors. <BR/>The logic behind my statement is clear, if you have database 50 gigs versus 100 gigs which one takes up less process, memory, CPU, and I/O? <BR/>You will realize, the smaller database will be easy for an application to handle, and this is true for Exchange as well. Some of MVP’s I know running over 200GIG databases happily after all. These database can be restored in very quick time as well. ( Snapshots).<BR/>Having Enterprise version of exchange and making one DB 200 gig and not creating multiple small databases is BAD idea. If you are running standard version, you have no choice anyways (- :<BR/><BR/>best<BR/>ozOz Casey, Dedealhttps://www.blogger.com/profile/12226180672457689907noreply@blogger.comtag:blogger.com,1999:blog-3179219424167705024.post-12926780489827470842008-12-19T11:45:00.000-08:002008-12-19T11:45:00.000-08:00"The reality behind the size of the database is th..."The reality behind the size of the database is that the bigger the database is, it gets harder for application to handle." <BR/>----<BR/>This is not true. The only reason Microsoft recommends the 100GB limit on Exchange 2007 databases is because of the cost and technology available for backup/restore. They have said if cost and technology for backup were to improve they will adjust their size recommendation. This is also why they recommend up to 200GB for CCR - because you can backup off of the passive node which can usually run during the day. Microsoft says that Exchange 2007 runs fine with multi-terabyte databases, but its not recommended for above mentioned reasons.Anonymousnoreply@blogger.com