I've changed the value for "NonMAPI Named Props Quota" to 24k (Default 8k) I've also added the a new key: "Named Props Quota" and set the value to 24K I know that the table can only grow to 32K total. My question is: Will the setup above grow my table past 32k and make the database unusable? Any help is appreciated. Thanks,-DEMPC

Named Properties consists of both “Named Props Quota” and “NonMAPI Named Props Quota”. http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/cee1cfb2-1fa1-41e9-adff-00ecd0b0729a/Jasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP:EMA Exchange 2010/2007 | MCTS:OCS 2007 | Exchange 2010/2007 | MCSA:Messaging/Security | MCSE:Messaging/Security

Thanks for your reply. I read this article (and many others) before I post the question. What is your take on the 32k limit.. will my values above combine to exceed that value and make my databases unusable?-DEMPC

On Wed, 2 Nov 2011 17:14:34 +0000, DEMPC wrote: >Thanks for your reply. I read this article (and many others) before I post the question. What is your take on the 32k limit.. will my values above combine to exceed that value and make my databases unusable? No. You just increased the ceiling, you didn't add anything. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

will my values above combine to exceed that value and make my databases unusable? The combined limit what you setting is definetly more then 32k and will make database unusable. But i agree with Rich that atpresent you are not adding anything but increaing the ceiling.Jasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP:EMA Exchange 2010/2007 | MCTS:OCS 2007 | Exchange 2010/2007 | MCSA:Messaging/Security | MCSE:Messaging/Security

This confuses me. If I'm increasing the ceiling to a value that could possibly allow the database to become unusable then I would like to change it. The last think I want to do is down one of my databases. -DEMPC

On Thu, 3 Nov 2011 16:09:57 +0000, DEMPC wrote: >This confuses me. If I'm increasing the ceiling to a value that could possibly allow the database to become unusable then I would like to change it. The last think I want to do is down one of my databases. Then reduce the number. If you don't want to risk a problem then move offExchange 2003 or put a front-end machine in place that can remove the X-* headers that are causing you the problem. Exchange 2007 (and 2010) removes X-headers from anonymous connections. You can even use a custom agent to remove others: http://headerfilteragent.codeplex.com/ Doing this with Exchange 2003 is possible, but a lot more difficult in terms of coding. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

will my values above combine to exceed that value and make my databases unusable? The combined limit what you setting is definetly more then 32k and will make database unusable. But i agree with Rich that atpresent you are not adding anything but increaing the ceiling.Jasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP:EMA Exchange 2010/2007 | MCTS:OCS 2007 | Exchange 2010/2007 | MCSA:Messaging/Security | MCSE:Messaging/Security

Hello, Hope the following article will be useful to understand: Understanding the Impact of Named Property and Replica Identifier Limits on Exchange Databases http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx Thanks, Simon

I am currently in coexistence with 2003 and 2010. I will lower the values so I don't run into any problems with the database in the future.-DEMPC