Daily Archives: April 18, 2005

Exchange 2003 – Restricting message sizes

I’ve been clearing out my mailbox as I’ve had a copule of warning messages that I’m up to my size limit in Exchange, and if I ignore these messages then I can’t send any mails – just when I need to send that urgent mail of course.  So that I can easily find out which messages to trash, I use the configurable options for the  search folders feature in Outlook 2003 to find out which messages have the largest attachments.  Then, I can then either delete just the attachment or delete the whole message.  Well, I noticed an extra large attachment, which led me to realise that we’d had our message size limits increased for messages sent internally.  I was convinced that the message size limit isn’t this big at our SMTP gateway.  So I had a look artound and found an article showing how you can configure different message sizes  globally, at the Connector, and at the SMTP virtual server.  

Now you can set different thresholds for messages at different parts of the system.  And confuse everyone if you want.  hee hee.

By the way, after some digging around, our message limits are the same internally and externally so I was wrong about that too. I’ve cleared most of the junk out of my mailbox – but I’m running out of disk space now!! Oh well…

Advertisements

Exchange 2003 Databases and the Exchange store

I’m playing around, trying to tweak Exchange 2003 to get the best possible performance in my Virtual machine demo environment so that my demos look good, and I’ve been reading the Optimising Storage document on TechNet.   There’s a table in this document which talks about the stored and their impact on disk I/O which I thought was worth reproducing here.  I tend to get asked for this quite a lot so here it is…

Table 2   Exchange store components and corresponding impact to disk I/O
Component Why it impacts disk I/O
Jet database (.edb file) The Jet database is used to store all data submitted from MAPI clients. All client activity generated by a MAPI client causes updates to the Jet database.
 

Streaming database (.stm file)

Stores attachments and data submitted from IMAP4, NNTP, Microsoft Outlook® Web Access, or SMTP. Pointers are saved in the Jet database so the data can be delivered to MAPI clients upon request.

Stores incoming SMTP mail. If the data contains MAPI information, the SMTP message is then transferred to the Jet database.

All internet protocol client activity causes updates to the streaming database.

 

Transaction log files (.log files)

 

All changes made to the database are first committed to transaction log files. This means that any time a user sends or reads a message, and any time a user modifies data stored in their mailbox, that change is written to the transaction log file. The change is immediately committed to the in-RAM database cache, and then copied back to disk when the system’s load permits. Transactions are also read back when a database is mounted.

New Smartphone SPV C550 shipping

The Register had something that caught my eye this monring after blogging about it the other day.  Apparantly we’ll be able to get hold of the next version of the Smartphone in the UK from next month.  Yippeee…

The funky matt black look really annoys me for a really girly reason.  Whenever I take a call, my dangly earring screeches on the shell and causes a sound like chalk on a blackboard – Eeuch!   Mind you, my colleague Mike has a bloke type complaint too… He told me that whenever he answers a call, the microphpone part at the top pulls the hairs out of his sideboards (US= sideburns), no, not the hairs out of his ears and he complains that answering a phone call hurts.  Poor chap… I’m sure I’m not alone with my whinges.

So do I go go for this one, or wait until the 600 is ready?  Aargh! decisions, decisions…..