locked
different between Exchange Database 2007 and Exhcnage Database 2010 RRS feed

  • Question

  • Hi All,

    Can anyone give me brief explanation about Exchange Database,

    01. What is main architectural different between Exchange 2007 Database and Exchange 2010 Database , what is Single instance Storage and what is Extensible Storage Engine , Why ESE reduce the IOPS requirement  when it come Exchange 2010  If we are implementing Exchange 2010 we shouldn't concern about IOPS ? does it mean that we need more memory 

    02. What is Transaction Logs how does  it works , what is function of  Checkpoint Files , what is Database Cache Shall we consider Memory for Database Cache ,

     

    It would be appropriated if anyone give me answers Point-by-Point 

    Thanks

     

    Monday, January 16, 2012 3:19 PM

Answers

  • 01. What is main architectural different between Exchange 2007 Database and Exchange 2010 Database , what is Single instance Storage and what is Extensible Storage Engine , Why ESE reduce the IOPS requirement when it come Exchange 2010 If we are implementing Exchange 2010 we shouldn't concern about IOPS ? does it mean that we need more memory

    Single Instance Storage - In laymans Term - If you Send a Attachment to 100 Users. Its Stores only Once -And pointers are given to the Users where they can access them.

    This gives Performance Issues.

    There was memory Contrains in 32 bit machines like windows server 2003 can support only till 3 to 4 gb of memory

    After 64 Bit machines came . Memory wasn't a Contrain for us

    Now in Exchange 2010 - Single Instance Storage was removed - Cause there is no Size issues in mailbox level or Database level (unlimited) - No Memory Issues ( Rams or so Cheaper now)

    The Hardisk RPMs are more Efficient nowadays , You Don't need to worry of IOPS.

    For Example - Am Seeing 32 Gb of memory all roles installed they run 2000 mailboxes where 1000 are Effective - Server Runs with No issues

    **Some Prereq Outlook are running in Cache mode etc.. 

    02. What is Transaction Logs how does it works , what is function of Checkpoint Files , what is Database Cache Shall we consider Memory for Database Cache ,

    When you Move a mailbox are when you move a item in mailbox , or when you send a email . Transactions are happening . and these logs are created

    In Exchange 2010 its 1024kb .once its created its get played into the database.

    ""Data is not going in to the database directly. Data is created as logs then its get played into the database"

    Now while restoring - Logs can help in restoring the data

    For Example , If you have a full backup of last week and a differential backup of 7th day of this week.

    We can restore the full backup and the 7th day differential backup and

    We can use eseutil tools to replay the logs into the database in DR situations.

    .chk File Stores all information . Like Backup taken , and how many logs are created , It has the log sequence information. so n so.

    Regards Database Cache --

    The Extensible Storage Engine (ESE) engine uses database cache to reduce I/O operations. In general, the more database cache that is available, the less I/O that is generated on a Microsoft Exchange Server 2010 Mailbox server. The database I/O reduction primarily depends on the amount of database cache available to the server and the user message profile.

    http://technet.microsoft.com/en-us/library/ee832793.aspx

    Regards

    Satheshwaran Manoharan

    • Proposed as answer by Sukh828 Monday, January 16, 2012 8:22 PM
    • Marked as answer by Terence Yu Wednesday, January 25, 2012 7:39 AM
    Monday, January 16, 2012 3:57 PM

All replies

  • 01. What is main architectural different between Exchange 2007 Database and Exchange 2010 Database , what is Single instance Storage and what is Extensible Storage Engine , Why ESE reduce the IOPS requirement when it come Exchange 2010 If we are implementing Exchange 2010 we shouldn't concern about IOPS ? does it mean that we need more memory

    Single Instance Storage - In laymans Term - If you Send a Attachment to 100 Users. Its Stores only Once -And pointers are given to the Users where they can access them.

    This gives Performance Issues.

    There was memory Contrains in 32 bit machines like windows server 2003 can support only till 3 to 4 gb of memory

    After 64 Bit machines came . Memory wasn't a Contrain for us

    Now in Exchange 2010 - Single Instance Storage was removed - Cause there is no Size issues in mailbox level or Database level (unlimited) - No Memory Issues ( Rams or so Cheaper now)

    The Hardisk RPMs are more Efficient nowadays , You Don't need to worry of IOPS.

    For Example - Am Seeing 32 Gb of memory all roles installed they run 2000 mailboxes where 1000 are Effective - Server Runs with No issues

    **Some Prereq Outlook are running in Cache mode etc.. 

    02. What is Transaction Logs how does it works , what is function of Checkpoint Files , what is Database Cache Shall we consider Memory for Database Cache ,

    When you Move a mailbox are when you move a item in mailbox , or when you send a email . Transactions are happening . and these logs are created

    In Exchange 2010 its 1024kb .once its created its get played into the database.

    ""Data is not going in to the database directly. Data is created as logs then its get played into the database"

    Now while restoring - Logs can help in restoring the data

    For Example , If you have a full backup of last week and a differential backup of 7th day of this week.

    We can restore the full backup and the 7th day differential backup and

    We can use eseutil tools to replay the logs into the database in DR situations.

    .chk File Stores all information . Like Backup taken , and how many logs are created , It has the log sequence information. so n so.

    Regards Database Cache --

    The Extensible Storage Engine (ESE) engine uses database cache to reduce I/O operations. In general, the more database cache that is available, the less I/O that is generated on a Microsoft Exchange Server 2010 Mailbox server. The database I/O reduction primarily depends on the amount of database cache available to the server and the user message profile.

    http://technet.microsoft.com/en-us/library/ee832793.aspx

    Regards

    Satheshwaran Manoharan

    • Proposed as answer by Sukh828 Monday, January 16, 2012 8:22 PM
    • Marked as answer by Terence Yu Wednesday, January 25, 2012 7:39 AM
    Monday, January 16, 2012 3:57 PM
  • I appreciated   your answer,

    Unfortunately i am still not clear!!

    your explanation didn't helped me so much...i think  i need to reread the book..

    anyway thanks a lot for your effort

    Monday, January 16, 2012 6:03 PM
  • I couldn't really explain it better than already explained.
    Sukh
    Monday, January 16, 2012 8:22 PM
  • Well Satheshwaran explained in a good way.
    If you found this post helpful, please "Vote as Helpful". If it answered your question, remember to "Mark as Answer". MCSE,MSCITP-EA
    Wednesday, January 18, 2012 9:41 AM