• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 259
  • Last Modified:

Very slow ORDER BY

Hello,

When I tried to ORDER BY anything in one of my tables, it takes a lot of time to do it even for not too many records (about a thousand).

I have two tables, say Contracts and Names table, the query is:

SELECT
contracts.key,
contractor_names.Name AS contractor_name,
client_names.Name AS client_name

FROM
Contracts as contracts      
JOIN
Names as contractor_names            
      on contracts.Contractor_Name_Key = contractor_names.Name_Key
JOIN
Names as client_names            
      on contracts.Client_Name_Key = client_names.Name_Key
      
order by contracts.key

Everything works fine UNLESS I try to order this query by anything... In which case it does it, but extremely slow, like sorting 100 rows for a minute. I presume it's because of my double join, so can it be fixed somehow?

The query and all names have been changed as originally it's a bit bigger, so pay no attention to that.

Thanks,
Yurich
0
Yurich
Asked:
Yurich
  • 6
  • 3
  • 2
  • +2
4 Solutions
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
how much RAM does your server have?
how much RAM does your sql server take from that?
0
 
YurichAuthor Commented:
frankly, I got no idea as it's a remote server and I got no rights to browse it. but for other querries it can take  10-20 seconds to fetch and sort a million or two records.
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
How do you connect to the server (which tools)?
can you get a execution plan for that query?
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
davbouchardCommented:
Is there a index on contracts.key column?
0
 
YurichAuthor Commented:
I connect through Query Analyzer, if that's what you're asking about and I'm not sure what teh execution plan is...

Actually, I'm not trying to sort by contracts.key in my original query, I trried to do it by dates, but later I tried by this key and by then by the names - the result is the same.

If I go to the contracts table properties (and that's the only place I have priveledges to go), I can see that there's a tick under ID, but no tick under key for contracts.key

0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
>I connect through Query Analyzer, if that's what you're asking about and I'm not sure what teh execution plan is...

look in the view menu of the QA, there is a option "Display Execution Plan".
Activate it, run the query, and you will get an additional tab with the execution plan (graphical)
tell us what you get there.
0
 
YurichAuthor Commented:
ok, found it.

when I add order by, i have table spool/lazy spool operation to appear, which generated by table scan, connects to Nested Loops/Inner Joins, costs 69% and generates 11 mil rows... that must be my problem, but what do we do about it?

thanks,
yurich
0
 
Aneesh RetnakaranDatabase AdministratorCommented:
Yurich,
> which generated by table scan
Now make sure that you have indices on these columns

 contracts.Contractor_Name_Key , contractor_names.Name_Key  
contracts.Client_Name_Key , client_names.Name_Key
contracts.key


0
 
imran_fastCommented:
Create index on the field you are using in your order by .
0
 
YurichAuthor Commented:
guys, i cannot change the table structure
0
 
imran_fastCommented:
We are not asking you to change the schema of the table but if you can you have to create index on the table

create nonclustured index ix_index1 on contracts (key)

0
 
YurichAuthor Commented:
thanks,

I had a look at the sp that creates this table and actually they do create indeces for this fields and for other "key" fields.

I probably will check if there're indeces for other fields.

regs,
yurich
0
 
YurichAuthor Commented:
i haven't sorted this problem, but I just did for this query all sorting right in the report (and that was for a report), and that was just fine. I had all indeces for all entities that I had to order by, but it must be something else. I found that in some cases (in the same database) joining table on itself and then to something else can cause the same problem with no order by at all...

anyway, thanks again,
yurich
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 6
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now