![]() ![]() Returns 43 rows with HEAP, CLUSTERED, NONCLUSTERED indexes.Ĭould you recommend what to look at? Why does it parse so much? Says there are 128 columns, when select * from sys.indexes Where object_id in (OBJECT_ID('tables_names').') timing for 13 joins: SQL Server parse and compile time:ĬPU time = 32250 ms, elapsed time = 32729 ms. Shows that with every uncommented join it takes a longer time to parse, e.g. I commented all joins and started to uncomment them one by one, and SET STATISTICS TIME ON All statistics is gathered with "exec sp_updatestats", and I checked it in sys.stats - everything looks fine. So, it looks like it takes too much time just to build the execution plan. Then I got the query and asked in SQL Server Management Studio for "Display estimated execution plan", and I also started to wait. I tried to get the execution plan by executing a query from an application session, but there were no execution plan. I tried to look at the execution plan and I started to wait. This query works fine with the same data set on PostgreSQL, Oracle and other databases, and entire execution takes about 1 minute.īut on SQL Server it takes about 40 minutes. I have an SQL Server 2014 instance (.8) and a quite complex SELECT statement with about 20 joins. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |