Hello Steve, The 2 databases that have had this problem (both have had the namedproperties increased twice now) have less than 700 mailboxes. We have 1 database with slightly more mailboxes that isn't even logging warning yet I'm perfectly willing to add more databases, I guess I will look for the documentation you reference. Karl > Yes - it sucks. We're all in agreement on this. But it's the way > things are, and as long as MAPI property values are 32 bit numbers > with only 16 bits available for the unique identifier, that's the way > things will continue to be. It's a bad situation and we're doing our > best to help everyone cope with it. > > This scenario (and others) are part of why we don't recommend placing > so many users in a single database. You can put them all on the same > server - just break up the databases so you have far fewer users per > database. The named prop issue will take much longer to appear, > migration to a new database if it does appear will be much faster, and > backup/restore times will be much shorter. I'm sure someone around > here's got a link to our official guidance if you want some numbers to > help. > > Steve > > "Karl Mitschke" wrote in message > news:d66cd4c240ce58caa419e07da5c3@msnews.microsoft.com... > >> Hello Dgoldman [MSFT], >> >>> You dont want to increase the limit because down the road all you >>> are going to do is hit it and have the same problem. You can >>> download a copy of MFCMapi and logon to the information store and >>> dump out the Named Props table. Essentially the only way to fix it >>> (the correct way) is move the users to a new information store and >>> also to stop the program from creating so many named props. >>> >>> Dgoldman >>> http://blogs.msdn.com/dgoldman >>> Download OABInteg >>> (http://gotdotnet.com/Community/UserSamples/Download.aspx?SampleGuid >>> =A >>> 2338E73-F521-4071-9B1D-AAF49C346ACD) >> Are you kidding me? >> >> We get 1 million mail messages a month. If only a very small >> percentage of thes have a rogue header like >> "x-david-mailscanner-spamcheck" and soon we will have to move all >> 14000 users to new databases? >> >> That's insane! >>
