Sie sind auf Seite 1von 4

DATABASE ANALYSIS

BACKGROUND

Textit Database has to be optimized for the issues like Index Maintenance and also Query Optimization.
These three areas are the primary focus of optimization in our Initial Database Analysis.

There are three areas which are focused primarily:

1 Query Optimization.

2. Index Analysis

1. Query Optimization

Before blaming the database for the cause of slowness. We have gathered some queries which are
really causing the slowness. This judgment was based on the amount of reads, execution per minutes,
total, Average CPU (milliseconds).

QUERY/STORED PROCEDURE Executions/Min AVG CPU (MS) AVG Reads


CF_NEW_CHATS_COUNT 68.1695 1286.7811 112866
ETL_CLIENT_STAGING_DATA_LOAD 0 4744472.91 1689807404
Notification Count 56.3372 1357.3406 201314
FETCH_CHAT_BLOCKS_V3 9.9567 798.9439 83338
FETCH_HEADER_STATISTICS 70.3158 74.7501 12542
[cases].[FETCH_CASE_LIST] 0.1065 1116.5787 289199
FETCH_PROFILE_ATTRIBUTES 11.0337 85.4309 54321
DASH_SUMMARY 1.9832 1593.5143 297790
Fetch Pending For A Keyword Query 8.0541 3971.5384 474860
Fetch Routing Query 217.0411 22.0316 11653

The higher the executions/min the higher the amount of RAM usage. Moreover the higher the average
reads the higher the amount of Read Locks on the table.
2. Index Analysis:

While doing index analysis multiple issues were found with indexes. These are

a. Missing indexes
Sql server keeps a list of queries and their execution time so that it can help build new
indexes with the passage of time and usage.
b. Index Hoarding Accumulating too many indexes for no reason
c. Aggressive Index Those which causes locks and slowness.

Datab
Prio ase
rity Finding Name Table Name Usage Size Recommendations
Aggressive
Indexes:
Total lock
wait time >
5 minutes Reads: We cannot delete this
(row + 4,008,712 index as it is of High
page) with (4,008,712 120,406 Risk. But we have to
long seek) ,208 figure out an alternate
average Writes:1,5 rows; to avoid locks on the
1 waits TextIt reports.conversations 55,222 7.0GB database
Aggressive
Indexes:
Total lock
wait time >
5 minutes Reads:
(row + 105,113
page) with (22 seek
long 105,091 Index on a Table with
average dbo.outgoing_notifica scan) 6 rows; 6 Rows should not be
2 waits TextIt tions_trigger Writes:22 0.0MB there in any case
Aggressive
Indexes:
Total lock Reads:
wait time > 529,359
5 minutes (238,158
(row + seek
page) with 291,201
long scan) 10 Index on a Table with
average Writes:238 rows; 10 Rows should not
3 waits TextIt dbo.jobs ,174 0.0MB be there in any case
Aggressive Reads: Index on a Table with
Indexes: 209,354 170 <1000 Rows should
Total lock dbo.incoming_messag (26,262 rows; not be there in any
4 wait time > TextIt es seek 1.2MB case

2
5 minutes 176,079
(row + scan 7,013
page) with lookup)
long Writes:51,
average 465
waits
As the writes are high
Index 8,302,5 but reads are 0 we
Hoarder: 59 can delete the index
Unused NC Reads: 0 rows; and as its size is low, if
index with client.staging_data_lo Writes:7,2 312.2M anything goes wrong
5 High Writes TextIt ad 56,681 B we can re-create it.
These indexes are just
writing and increasing
Index the size of the db. We
Hoarder: 120,514 can delete it one by
Unused NC Reads: 0 ,646 one on weekends to
index with Writes:792 rows; avoid any mishap and
6 High Writes TextIt dbo.chats ,306 4.5GB see the performance
These indexes are just
writing and increasing
Index the size of the db. We
Hoarder: 374,795 can delete it one by
Unused NC Reads: 0 ,175 one on weekends to
index with Writes:1,4 rows; avoid any mishap and
7 High Writes TextIt dbo.dlr_history 89,675 11.1GB see the performance
These indexes are just
writing and increasing
Index the size of the db. We
Hoarder: 55,112, can delete it one by
Unused NC Reads: 0 179 one on weekends to
index with dbo.subscriber_attrib Writes:695 rows; avoid any mishap and
8 High Writes TextIt utes ,979 4.8GB see the performance
These indexes are just
writing and increasing
Index the size of the db. We
Hoarder: 103,783 can delete it one by
Unused NC Reads: 0 ,537 one on weekends to
index with Writes:213 rows; avoid any mishap and
9 High Writes TextIt dbo.transaction ,880 2.7GB see the performance
As the writes are high
Index 15,438, but reads are 0 we
Hoarder: 772 can delete the index
Unused NC rows; and as its size is low, if
index with Reads: 0 410.2M anything goes wrong
10 Low Writes TextIt client.Import_Data Writes:6 B we can re-create it.

3
As the writes are high
Index 11,978, but reads are 0 we
Hoarder: 130 can delete the index
Unused NC Reads: 0 rows; and as its size is low, if
index with Writes:5,8 324.2M anything goes wrong
11 Low Writes TextIt dbo.subscriptions 39 B we can re-create it.
As the writes are high
Index 11,978, but reads are 0 we
Hoarder: 129 can delete the index
Unused NC Reads: 0 rows; and as its size is low, if
index with Writes:5,8 515.5M anything goes wrong
12 Low Writes TextIt dbo.subscriptions 39 B we can re-create it.

Das könnte Ihnen auch gefallen