Home > database >  Comply to the highest table associated with eight digit meter on the time-consuming problem
Comply to the highest table associated with eight digit meter on the time-consuming problem

Time:03-19


Query is the primary key two tables, indexes, were also carried out a full table scan way updated index statistics, opens the real-time query statistics, can see time consuming more than 1 second, close the real-time query statistics, too, means open and not get too much extra time consuming, and tried to loop the join, hash join, merge join three associated ways are the same time, deviation is less than 50 ms,
Hardware information: 3800, 1 3900 x, 32 g ddr4 TS750 (belong to the domestic high-end solid)
I don't know should shouldn't doubt, 30 w table associated with 4 line table, will need a second, it belongs to the normal speed?

CodePudding user response:

You don't post the SQL, can't help you optimize,
If there are words, you can change the table name, column name, to deal with the sensitization,

CodePudding user response:

reference 1/f, gypsy song response:
is not posted on the SQL, you can't help you optimize,
If there are words that can modify the table name, column name, to deal with the sensitization,

Actually to do not have these scruples, or you'll make the execution plan can I sold out...
Is one of the most common query
 
Select
A1. Id
A2. Name
The from YieldTransit as a1
Inner join EMAgitation as a2 on a2. Id=a1. EMAgitation_ID

31 w the table a1 said, a2 is 4 lines of the form,

CodePudding user response:

reference 1/f, gypsy song response:
is not posted on the SQL, you can't help you optimize,
If there are words that can modify the table name, column name, to deal with the sensitization,


This is the opening Time and IO information

CodePudding user response:

Single check a1 table primary key ID, takes 1100 ms, associated a2 after table, took 1320 ms,
There are two questions
Query 1: in the domestic high-end solid, 31 w line table primary key ID, take 1.1 seconds to normal?
2: the associated foreign key table, check the foreign key after a name field, time-consuming increased by about 200 ms, moreover key table data is 4 lines, the time consuming increase properly?
  • Related