Tablescan

ID Category
SDR-Q35 Query Optimization

SDR-I9 Index Optimization
Finding
The function "upper" on column [inforcrm].[sysdba].[USERSECURITY].[USERCODE] may
The function "isnull" on column [inforcrm].[sysdba].[TICKET].[ALTERNATEKEYSUFFIX] may
The function "isnull" on column [inforcrm].[sysdba].[TICKET].[ALTERNATEKEYPREFIX] may
The function "dateadd" on column [inforcrm].[sysdba].[ACCOUNTPRODUCT].
The function "upper" on column [inforcrm].[sysdba].[USERSECURITY].[USERCODE] may
The function "isnull" on column [inforcrm].[sysdba].[TICKET].[ALTERNATEKEYSUFFIX] may
The function "PROBE" on column [inforcrm].[sysdba].[CONTACT].[SECCODEID] may be
The function "isnull" on column [inforcrm].[sysdba].[TICKET].[ALTERNATEKEYPREFIX] may
Table [inforcrm].[].[ADDRESS] is experiencing excessive Page lock contention
Index [HISTORY_STARTDATE] on table [inforcrm].[].[HISTORY] is experiencing excessive
Table [inforcrm].[].[HISTORY] is experiencing excessive Page lock contention
Table [inforcrm].[].[QRTZ_LOCKS] is experiencing excessive Row lock contention
Index [XIE4USERSECURITY] on table [inforcrm].[].[USERSECURITY] is experiencing
Index [PK_USERSECURITY] on table [inforcrm].[].[USERSECURITY] is experiencing
Index [XIE7ACTIVITY] on table [inforcrm].[].[ACTIVITY] is experiencing excessive Row lock
Index [PK_ACTIVITY] on table [inforcrm].[].[ACTIVITY] is experiencing excessive Row lock
Table [inforcrm].[].[QRTZ_TRIGGERS] is experiencing excessive Row lock contention
Table [inforcrm].[].[ACTIVITYATTENDEE] is experiencing excessive Row lock contention
Index [HISTORY_COMPLETEDDATE] on table [inforcrm].[].[HISTORY] is experiencing
Table [inforcrm].[].[INDEXUPDATES] is experiencing excessive Row lock contention
Index
Index [IDX_QRTZ_T_NFT_ST] on table [inforcrm].[].[QRTZ_TRIGGERS] is experiencing
Index
Index
Index [IDX_QRTZ_T_N_G_STATE] on table [inforcrm].[].[QRTZ_TRIGGERS] is experiencing
Index [IDX_QRTZ_T_STATE] on table [inforcrm].[].[QRTZ_TRIGGERS] is experiencing high
Index [XIE6CONTACT] on table [inforcrm].[].[CONTACT] is experiencing high levels of page
Index [IDX_QRTZ_T_NFT_ST_MISFIRE_GRP] on table [inforcrm].[].[QRTZ_TRIGGERS] is
Index [IDX_QRTZ_T_NFT_ST_MISFIRE] on table [inforcrm].[].[QRTZ_TRIGGERS] is
Index [IDX_QRTZ_T_N_STATE] on table [inforcrm].[].[QRTZ_TRIGGERS] is experiencing
Recommendation
It is recommended that you consider redesigning this WHERE clause to prevent index
It is recommended that you review your applications usage of table [ADDRESS] to
It is recommended that you review your applications usage of index
It is recommended that you review your applications usage of table [HISTORY] to determine
It is recommended that you review your applications usage of table [QRTZ_LOCKS] to
It is recommended that you review your applications usage of index [XIE4USERSECURITY]
It is recommended that you review your applications usage of index [PK_USERSECURITY]
It is recommended that you review your applications usage of index [XIE7ACTIVITY] to
It is recommended that you review your applications usage of index [PK_ACTIVITY] to
It is recommended that you review your applications usage of table [QRTZ_TRIGGERS] to
It is recommended that you review your applications usage of table [ACTIVITYATTENDEE]
It is recommended that you review your applications usage of table [INDEXUPDATES] to
It is recommended that you review your applications usage of index [IDX_QRTZ_T_NFT_ST]
It is recommended that you review your applications usage of index [IDX_QRTZ_T_STATE]
It is recommended that you review your applications usage of index [XIE6CONTACT] to
Impact Explanation
The function or expression "upper" in a query in [inforcrm] can cause index suppression
The function or expression "isnull" in a query in [inforcrm] can cause index suppression
The function or expression "dateadd" in a query in [inforcrm] can cause index suppression
The function or expression "upper" in a query in [inforcrm] can cause index suppression
The function or expression "PROBE" in a query in [inforcrm] can cause index suppression
The table is experiencing an average wait time of 16ms per wait due to lock contention with
The index is experiencing an average wait time of 560.6ms per wait due to lock contention
The table is experiencing an average wait time of 234.5ms per wait due to lock contention
The index is experiencing an average wait time of 1s per wait due to lock contention with
The index is experiencing an average wait time of 1.1s per wait due to lock contention with
The index is experiencing an average wait time of 0.2ms per wait with 12327 waits due to
Additional Considerations
Database Table Application Login Nam Workstatio
inforcrm sysdba.USERSECURITY
inforcrm sysdba.TICKET
inforcrm sysdba.ACCOUNTPRODUCT
inforcrm sysdba.USERSECURITY
inforcrm sysdba.CONTACT
inforcrm dbo.ADDRESS
inforcrm dbo.HISTORY
inforcrm dbo.QRTZ_LOCKS
inforcrm dbo.USERSECURITY
inforcrm dbo.USERSECURITY
inforcrm dbo.ACTIVITY
inforcrm dbo.ACTIVITY
inforcrm dbo.QRTZ_TRIGGERS
inforcrm dbo.ACTIVITYATTENDEE
inforcrm dbo.INDEXUPDATES
inforcrm dbo.VIRTUALFILESYSTEM
inforcrm dbo.CONTACT
TSQL Batch
(@P1 int,@P2 datetime2(0),@P3 nvarchar(9))UPDATE USERSECURITY SET
(@P1 nvarchar(8))SELECT COUNT(A1.TICKETID) FROM TICKET A1 INNER JOIN
(@P1 nvarchar(8))SELECT COUNT(A1.TICKETID) FROM TICKET A1 INNER JOIN
select isnull(sum(userfield7),0) from accountproduct where ACCOUNTPRODUCT.choferid
(@P1 nvarchar(9))SELECT LOGINATTEMPTS, FAILEDATTEMPTDATE FROM
(@P1 nvarchar(8))SELECT A1.TICKETID,A1.SECCODEID
(@P1 nvarchar(5))SELECT A1.CONTACTID, A2.INTERNALACCOUNTNO
(@P1 nvarchar(8))SELECT A1.TICKETID,A1.SECCODEID
Fix Script
Undo Script
Learn more about
http://wiki.idera.com/x/44AxAw

Tablescan

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Tablescan

Hochgeladen von

Copyright:

Verfügbare Formate

ID Category

SDR-Q35 Query Optimization

Das könnte Ihnen auch gefallen