Since Exchange uses a database backend, is there provision for connecting it to an existing Oracle/DB2/Sybase database? That would eliminate a lot of the stability/recovery problems in a manner acceptable to even the most demanding shops. Dan On Wed, 21 Aug 2002, Forrest Dickinson wrote: > On Wed, 7 Aug 2002, Carl Wilhelm Soderstrom wrote: > > > > b. from what I hear, these files get corrupted on a regular basis; and > > they take *forever* to fix. I know of an administrator who has a quad > > xeon box, just for rebuilding corrupt Exchange databases. (and it > > still takes many hours to rebuild them). > >>Both of these are addressed if you set up the message store to be an SQL > >>server, or so someone said earlier this week on the list. > > > You cant use SQL as your message store with exchange server its not an > option also the problems people had with database corruption on exchange > server were with version 4.0 and 5.0 Microsoft completely redesigned the > database store with exchange 5.5 and again in exchange 2000 I have had > exchange 5.5 running for over 2 years and have yet to have any database > corruption and we store a lot of data in exchange both of our Exchange > Servers have over 10 gigs of data stored on each of them (not that this > compares with some oracle installations but exchange and oracle are two > different products with two different purposes) > > > > Forrest Dickinson > Network Administrator > Morgan Hunter Companies > 7600 West 110th Street > Overland Park, KS 66210 > (913) 409-1230 > mailto://fdickinson@morganhunter.com > http://www.morganhunter.com > > > > > > _______________________________________________ > Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list >