Configurable Timeout for connection used in New Index

Adrian Ursu

Posted on 03/05/2016 23:29:00

I have noticed that the timeout of the connection used for the New Index (SQL Builder) cannot be overriden (at least I could not find a way for it) and it defaults to 20sec.

This means that Count queries that take 21 seconds will prevent the indexer from even starting.

I believe it would be a good ideea to have this timeout configurable somehow.

I will take this opportunity to outline a few interface bugs for the New Index

1. the Interface for SQL Builder does not save the changes to the SQL query after the first save. It allows to edit it but it is not saved (at least in version 8.8.1.0).

2. After you add the first expression in Query, you cannot add additional expressions from the interface. I have to edit the file manually every time. THis happens ever since version 8.7.x.x

Thanks,

Adrian

Replies

Oleg Rodionov

Posted on 05/05/2016 01:36:19

Hi Adrian,

I've tested the issues 1-2 on solution based on official 881 with last IE/Chrome/FF (Win 8) and have good results (the issues are not reproduced). Here is proof:

Chrome: http://screencast.com/t/VZ6TSK8m

IE: http://screencast.com/t/Bqoieupclyvo

FF: http://screencast.com/t/n3rf1EqK3

Please, try to delete cache of your browser initially.

BR, Oleg QA

Adrian Ursu

Posted on 05/05/2016 08:43:13

Thanks Oleg, I tried that before posting this.

I tried it again now with the same outcome:

http://screencast.com/t/PlgQOcEeE9

It probably works ok with new solutions but not with upgraded ones.

Thanks,

Adrian

Oleg Rodionov

Posted on 05/05/2016 13:10:49

And what's DW version was upgraded with 881?

BR, Oleg

Adrian Ursu

Posted on 05/05/2016 13:51:16

The one that I recorded was upgraded from 8.8.0

But I have other solutions that were continuously upgraded ever since 8.6.1 and they have the same issue.

Oleg Rodionov

Posted on 06/05/2016 01:14:41

Hi,

I've checked your solution with the same browsers and have good results as well:

IE: http://screencast.com/t/GxEXnGotH5

FF: http://screencast.com/t/D0nHDBe6

Chrome: http://screencast.com/t/6z3iSvJLM1Lu

BTW, the bug related to restoring existing SQL Queries (TFS 21868, taken on 8.8.0.2) was fixed on 881 with Admin/Module/Repositories/Scripts/IndexController.js updated.

So, probably cause of your issuee is your local one, try to clear browser cache again etc.

BR, Oleg

Nicolai Høeg Pedersen

Posted on 09/05/2016 13:01:31

Hi Adrian

With regards to the timeout - do you have a column on your table with an autoid and a clustered index on that column? It will increase performance a lot.

Adrian Ursu

Posted on 09/05/2016 14:35:56

Hi Nicolai,

Yes, I do. But I had a case where the Count statement took about 24 secodns and because of that the index did not start.

I tried to override the connection string but unsuccessfully.

It's also very possible that I did something wrong.

The timeout in this case should probably be a hidden setting. Not something that and admin can/should play with.

Thanks,

Adrian

Nicolai Høeg Pedersen

Posted on 09/05/2016 14:48:54

Well, I would take a look at the count statement in SQL management studio and have a look at the execution plan. It should not take that much time even with a zillion records.

Adrian Ursu

Posted on 10/05/2016 01:16:20

It's not a common situation. We had a join between EcomProducts and a table that had 9.000.000 + rows

And we expect the final one to have a lot more.

We have optimized the query for the current situation but I can only imagine that the execution time will increase if the number of records will increase that much.

Morten Snedker

Posted on 01/06/2016 13:45:38

Just a follow-up:

I have a 8.7 and 8.8 solution where updating the existing query for SQLIndexBuilder does not work. It is simply not saved, and nothing is notified to user. Also, it occurs across browsers. We'll investigate this to resolve it.

Best regards
Morten Snedker

Adrian Ursu

Posted on 01/06/2016 13:52:39

Thank you Morten.

I have managed to figure put the answer to the second point in my post.

If i want to add more than one condition, I have to add an expression group.

But the editing of the SQL statement is still valid.

Thank you,

Adrian

Morten Snedker

Posted on 01/06/2016 14:14:15

Oh - I missed that. I also missed Olegs comment on "fixed in 881". I'll take a nap.

/Snedker

Developer forum

Configurable Timeout for connection used in New Index

Replies