44
Note:Thissectioncoversonlythebasicsofdeterminingadatabaseissueasthe
issuepertainstointeractionwithOrion.ItisnotintendedasanSQL
troubleshootingguide.
IntheOriondatabase,thesinglemostimportantSQLserverperformance
measurementisdiskqueuelength.QueuelengthisameasurementoftheSQL
writesthatarewaitingtobewrittentodisk.Whendiskqueuesstartlengthening
andthereisasteadyloadontheSQLwrites,thequeuesmaygrowsolargethat
writerequestsgetdropped.Thismayleadtogapsindataandwillaffectthe
overallperformanceoftheSQLserver.Agoodruleofthumbisthatdiskqueue
lengthshouldnotexceedtwotimesthenumberofeffectivespindlesintheSQL
storage.Theeffectivespindlecountisthenumberofstripedspindles.ForaRAID
10directattachedstorageunitwitheighttotaldisks,theeffectivespindlecountis
four.Fourofthespindlesinthisarrayaretheprimarystripedarrayandtheother
fourareasecondarystripedmirrorofthefourprimaryspindles.Sinceno
performancegainisachievedbymirroringdisks,onlytheprimarystripedsetis
usedtomeasureperformance.
Foradditionalinformationondatabaseperformance,seetheManaging
Orion
Performance
Technical
Reference
(PDF).
Whenerrorsoccurthatpointtoalossoftheconnectiontothedatabasethe
followingstepscanhelpisolatetheissue:
1. PingtheSQLserverfromtheOrionservertochecknetworkconnectivity.
2. OpenSQLServerManagementStudioortheOrionDatabaseManagerand
attempttoconnecttothedatabase.
3. Ifbothoftheabovearesuccessful,runtheOrionConfigurationWizard
againstthedatabasebyselectingDatabaseinthefirstwizardscreen.
Ensurethatyouareusingtheproperdatabasecredentials.
4. OpentheOrionwebUItotestconnectivityagain.
5. TestopeninganODBCconnectionfromtheOrionserverusingaMicrosoft
utilitysuchasODBCPing
.
Ifallofthisfails,thentheissueisafailurewiththeSQLserver.Atthispoint,you
willneedtogodirectlytotheSQLserverandbegintroubleshooting.
TroubleshootingSQLisveryspecificforeachversionandimplementation,andit
isrecommendedthatyouconsulttheMicrosoft
Support
site
andsearchfor
informationpertainingtoyourversion.
654
TroubleshootingYourOrionDatabase