Question
PEGA0005 alerts on the table CPMHC_WORK.
Hi Team,
We could find a lot of PEGA0005 alerts on the table CPMHC_WORK.
PFB for one of the alerts.
Database update took more than the threshold of 500 ms: 23,301 ms SQL: INSERT INTO dbo.CPMHC_WORK (pzInsKey , "ActionTaken" , "AddressLine1" , "AppointmentAssistance" , "AuthCancelReason" , "AuthNumber" , "AuthRequestType" , "CFRequest" , "CTICallID" , "CallBackNeeded" , "CallBackPhone" , "CallComments" , "CallPurpose" , "CallPurposeID" , "CallType" , "CallerType" , "CancelAuthReason" , "CancelAuthReasonCode" , "CancelReason" , "CheckReferenceID" , "City" , "ClaimDOS" , "ClaimID" , "Comments" , "CommentsForFLDifficulty" , "ContactId" , "ContactName" , "ContactPhone" , "ContactRelationships" , "CurrentPCPOpenClaim" , "CurrentWorkbasketName" , "DeniedAuth" , "DifficultyFindProvider" , "DocumentID" , "DropdownServicingProvider" , "DualMemberID" , "EDUID" , "EGName" , "EGRFollowUp" , "EGRUrgentRequest" , "EffectiveDateText" , "EndDOI" , "EnrollmentMarkets" , "FaxWOID" , "FlagBenefitsSubject" , "FlagCallerHungUp" , "FlagClinicalTask" , "FlagCreateNewMailAddress" , "FlagDenAuthFaxSent" , "FlagDenAuthLetterSent" , "FlagEnrollProcessSubject" , "FlagExist" , "FlagGoodContact" , "FlagMembersIssue" , "FlagNetworkSubject" , "FlagOtherSubject" , "FlagTTYandTDD" , "FlagUpdatedHomeAddress" , "FlagUpdatedMailAddress" , "GRCallerFirstName" , "GRCallerLastName" , "GRCallerPhoneNum" , "HCCustomerType" , "InquiryDate" , "InteractionGoal" , "InteractionTime" , "InteractionType" , "IsAdvTakenForAssistanceOffer" , "IsAuthCancelledForRedir" , "IsCallTransferred" , "IsCallerAMember" , "IsDenialLetterRequiredForEGR" , "IsEGRMember" , "IsFirstImpCall" , "IsItemsOpen" , "IsProvbehalfMem" , "IsRelatedToPriorInquiry" , "IsTransferredIn" , "IsTransferredOut" , "IssueResolved" , "MemberDualCitizen" , "MemberFullName" , "MemberID" , "MemberLOB" , "NATFAcceptance" , "NetPromoterCategory" , "NetPromoterScore" , "NewPCPID" , "NewPCPName" , "NoOfItemsCreated" , "PCPChangeFOM" , "PCPReasonCode" , "PayDispCatg" , "PerformAction" , "Performance" , "PhoneNumber" , "PolicyNumber" , "PrivacyType" , "ProactiveAssistance" , "ProviderIDSearch" , "ProviderName" , "ProviderNumber" , "ProvidersReviewedNone" , "QualityReviewCaseID" , "RDEDay" , "RDEMonth" , "RDEQuarter" , "RDEWeek" , "RDEYeay" , "ReasonForIDCard" , "ReasonForInteraction" , "RecipientType" , "RequestReceivedDate" , "ResolveNotes" , "SCCF_ID" , "SavingsAmount" , "SearchDateTime" , "SelectedPCPAddress" , "SelectedPCPID" , "SelectedPCPName" , "StartDOI" , "StateCodes" , "Subject" , "TTYandTDDComments" , "TotalScore" , "TransferCallCategory" , "TransferCallSubCategory" , "TypeofBreach" , "UpdateEligibilityUrgent" , "UpdateMbrType" , "UpdatePDQProvider" , "VoiceMailMarkets" , "VoiceMailRcvdDate" , "WarmComments" , "WarmTransfer" , "WorkbasketName" , "pxCoverInsKey" , "pxCoveredCount" , "pxCoveredCountOpen" , "pxCoveredCountUnsatisfied" , "pxCreateDateTime" , "pxCreateOpName" , "pxCreateOperator" , "pxCreateSystemID" , "pxFlowCount" , "pxInsName" , "pxObjClass" , "pxUpdateDateTime" , "pxUpdateOpName" , "pxUpdateOperator" , "pxUpdateSystemID" , "pxUrgencyWork" , "pyAgeFromDate" , "pyChargeAmount" , "pyDescription" , "pyEffortActual" , "pyEffortEstimate" , "pyElapsedCustomerAck" , "pyElapsedCustomerUnsatisfied" , "pyElapsedPastDeadline" , "pyElapsedPastGoal" , "pyElapsedStatusNew" , "pyElapsedStatusOpen" , "pyElapsedStatusPending" , "pyEventID" , "pyFolderType" , "pyID" , "pyLabel" , "pyOrigDivision" , "pyOrigOrg" , "pyOrigOrgUnit" , "pyOrigUserDivision" , "pyOrigUserID" , "pyOrigUserWorkgroup" , "pyOwnerDivision" , "pyOwnerOrg" , "pyOwnerOrgUnit" , "pyProblemReason" , "pyProblemType" , "pyReopenCount" , "pyResolutionCost" , "pyResolvedDivision" , "pyResolvedOrg" , "pyResolvedOrgUnit" , "pyResolvedTime" , "pyResolvedTimestamp" , "pyResolvedUserID" , "pyResolvedUserWorkgroup" , "pyRootCause" , "pySLADeadline" , "pySLAGoal" , "pySLAName" , "pyStatusCustomerSat" , "pyStatusWork" , "pyUrgencyAdjustment" , pzPVStream) VALUES (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?) inserts: > > > > > > > > > > > > > > > > > > > > > > > 715066655> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 715066655> > > > > > > > > > > > > 0110955135> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 0> 0> 0> 2018-03-26 10:04:50.301> > 2018-03-26 10:04:50.646> 10> 2018-03-26 10:04:50.302> > > > > 0> > > 0> 0> 0> > > > > > > > > > > > > 2018-03-29 10:04:50.58> 2018-03-28 10:04:50.58> > [B@558d46e9>
The SQL Server Database Engine automatically maintains indexes whenever insert, update, or delete operations are made to the underlying data. The above rulebase entries / modifications can cause the information in the index to become scattered in the database (fragmented). Fragmentation exists when indexes have pages in which the logical ordering, based on the key value, does not match the physical ordering inside the data file. Heavily fragmented indexes can degrade query performance and cause the application queries to respond slowly.
Updates query optimization statistics on a table or indexed view. By default, the query optimizer already updates statistics as necessary to improve the query plan; in some cases you can improve query performance by using UPDATE STATISTICS or the stored procedure sp_updatestats to update statistics more frequently than the default updates.
Updating statistics ensures that queries compile with up-to-date statistics.