Forum Discussion

Resolver I

8 years ago

Direct Query...Performance Issue

Hey everyone, I have a large dataset and I'm trying to decide between 'import' and 'direct query'. Import takes forever to refresh this model. It sometimes works and sometimes can timeout, so i...

ricardocamargos

Continued Contributor

8 years ago

Have you tried to run this query on the database ? Is it ok ?

Are you writing your SQL or just selecting the tables ?

Thanks,

Ricardo

Resolver I

8 years ago

I have ran this query against the DB and it's fine. I can also run the same exact query in 'import' mode...and it works fine.

Anonymous
Not applicable
8 years ago
The default timeout on each query is 10 minutes. I have a couple of queries that need a bit longer than that. You are able to choose a longer timeout time if required. When you are in your Query Editor, find the Source line of the table. Click on the Cog icon. In the window that appears, open up the 'Advanced Options' and the first box is "Command Timeout".

I generally work with Import where possible. It seems to give a better level of user performance and I'm able to manage server strain a little easier. Fortunately i'm working with data that only needs to be up to date as of close of business, so i don't have that direct query need.
- codyraptor
  Resolver I
  8 years ago
  I have the query set to 120 minutes. Definitely not an issue with timeout. I'm also receiving a schema error.
  - Anonymous
    Not applicable
    8 years ago
    My next question would be what happens between the Source statement and when the query finalises. What operations are happening on the table after you get it from the source?
    
    Also are there other tables that will rely on this source, for either merging or as its own source?