|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
anyone able to answer an ADAM question?im running ADAM in conjunction with Quest Migration Manager software. QMM
uses ADAM to store information about the migration that is running. The migration has come to a standstill because DSAMAIN.EXE (ADAM) is CONSTANTLY, 24 hours a day consuming 100% of the cpu. If i stop the Quest services this drops down to a normal level so uts obvious that QMM is hitting ADAM pretty hard but 100% 24 hours a day?!?!? what can i do? Personally, I usually start with a network sniff. Take a network sniff for
3-5 mins of the software hitting ADAM. Then, look at the trace to see what the product is doing, and you can engage the vendor as needed. If you need help reading the sniff, send it to me offline. Just drop the online from my address. Thx! ~Eric -- Show quoteHide quoteEric Fleischman [MSFT] Microsoft Windows Server Division This post is provided "AS IS" with no warranties, and confers no rights "momo" <m***@momo.com> wrote in message news:OQDM74FRGHA.5116@TK2MSFTNGP10.phx.gbl... > im running ADAM in conjunction with Quest Migration Manager software. QMM > uses ADAM to store information about the migration that is running. > > The migration has come to a standstill because DSAMAIN.EXE (ADAM) is > CONSTANTLY, 24 hours a day consuming 100% of the cpu. > > If i stop the Quest services this drops down to a normal level so uts > obvious that QMM is hitting ADAM pretty hard but 100% 24 hours a day?!?!? > > what can i do? > > I second Eric, find out what it is doing and then you can pick who to complain
to. :) -- Show quoteHide quoteJoe Richards Microsoft MVP Windows Server Directory Services Author of O'Reilly Active Directory Third Edition www.joeware.net ---O'Reilly Active Directory Third Edition now available--- http://www.joeware.net/win/ad3e.htm Eric Fleischman [MSFT] wrote: > Personally, I usually start with a network sniff. Take a network sniff for > 3-5 mins of the software hitting ADAM. Then, look at the trace to see what > the product is doing, and you can engage the vendor as needed. > If you need help reading the sniff, send it to me offline. Just drop the > online from my address. > > Thx! > ~Eric > Hi
you need to speak to Quest. It's probably an poorly indexed query. The Quest KB seems to be quite helpful http://support.quest.com/eSupport/Solution.asp?WAid=268454021&itemID=12001 see point 12 on "slow performance" Lee Flight Show quoteHide quote "momo" <m***@momo.com> wrote in message news:OQDM74FRGHA.5116@TK2MSFTNGP10.phx.gbl... > im running ADAM in conjunction with Quest Migration Manager software. QMM > uses ADAM to store information about the migration that is running. > > The migration has come to a standstill because DSAMAIN.EXE (ADAM) is > CONSTANTLY, 24 hours a day consuming 100% of the cpu. > > If i stop the Quest services this drops down to a normal level so uts > obvious that QMM is hitting ADAM pretty hard but 100% 24 hours a day?!?!? > > what can i do? > > both extension attributes(14 and 15) are indexed... we set this up at the
beginning of the project. performance was not always this bad. only as the ADAM database has grown (almost 2GB now) is it getting worse every day. Show quoteHide quote "Lee Flight" <l**@le.ac.uk-nospam> wrote in message news:%239uuO$FRGHA.4740@TK2MSFTNGP14.phx.gbl... > Hi > > you need to speak to Quest. It's probably an poorly indexed query. > > The Quest KB seems to be quite helpful > > http://support.quest.com/eSupport/Solution.asp?WAid=268454021&itemID=12001 > > see point 12 on "slow performance" > > > Lee Flight > > > "momo" <m***@momo.com> wrote in message > news:OQDM74FRGHA.5116@TK2MSFTNGP10.phx.gbl... >> im running ADAM in conjunction with Quest Migration Manager software. QMM >> uses ADAM to store information about the migration that is running. >> >> The migration has come to a standstill because DSAMAIN.EXE (ADAM) is >> CONSTANTLY, 24 hours a day consuming 100% of the cpu. >> >> If i stop the Quest services this drops down to a normal level so uts >> obvious that QMM is hitting ADAM pretty hard but 100% 24 hours a day?!?!? >> >> what can i do? >> >> > > Talk to Quest people. Obviosly their application is doing something to
ADAM -- they should help you figure out what is it that it wants to get. -- Show quoteHide quoteDmitri Gavrilov SDE, DS Admin eXperience This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "momo" <m***@momo.com> wrote in message news:OQDM74FRGHA.5116@TK2MSFTNGP10.phx.gbl... > im running ADAM in conjunction with Quest Migration Manager software. QMM > uses ADAM to store information about the migration that is running. > > The migration has come to a standstill because DSAMAIN.EXE (ADAM) is > CONSTANTLY, 24 hours a day consuming 100% of the cpu. > > If i stop the Quest services this drops down to a normal level so uts > obvious that QMM is hitting ADAM pretty hard but 100% 24 hours a day?!?!? > > what can i do? > > |
|||||||||||||||||||||||
Other interesting topics