Slow query performance in dbForge Studio vs. SSMS

[scott]

Hi,

New forum user, first post. Happy user of SQLComplete plugin to SSMS.

I thought I'd give dbForge Studio a try, with the hope of convincing my boss to buy it. I bought SQLComplete at my own expense (I'm a contractor at my employer), but can't afford to buy dbForge Studio (dbFS) at my own expense.

However, I'm experiencing really poor performance when querying to data grid view in dbFS vs. SSMS.

My test table has 403 columns, 4221306 rows, and is 5,443.680 MB.

Sample queries:

Code: Select all

SET STATISTICS TIME ON
SELECT TOP (1000) * FROM dmt.PHI_FLAT
SELECT * FROM dmt.PHI_FLAT

SSMS:

Code: Select all

SQL Server parse and compile time: 
   CPU time = 15 ms, elapsed time = 15 ms.

 SQL Server Execution Times:
   CPU time = 0 ms,  elapsed time = 0 ms.

(1000 rows affected)

 SQL Server Execution Times:
   CPU time = 16 ms,  elapsed time = 7 ms.

(4221306 rows affected)

 SQL Server Execution Times:
   CPU time = 34547 ms,  elapsed time = 418914 ms.

The whole process ran in 7 mins.

dbFS:

At 24 min dbFS is frozen and not responding. I can send a screenshot if Devart Support is interested.

At this point, unless I'm doing something wrong, I can't recommend dbFS. And I really want to, there are a lot of nice features. But, on the same machine, SSMS is demonstrably faster.

[alexa]

We will review this post and will answer you as soon as possible.

[alexa]

We were able to reproduce this issue and will fix it in one of the next product builds. We will notify you once it's available fro downloading.

[nishiwoba]

great to see this topic. It is what I am findingStickman Boost