Hi,
I am building a new project in ASPRunner 4
I am using views as the tables and some views when run without a where clause return more than 50000 records/rows, this can take minutes to return all the data.
When the views are called on the web it is always called with a where clause and only takes a few seconds.
It seems when moving between steps or moving between tables in the tables list the view is called taking considerable time. Presumably ASPRunner is checking that things work as requested.
This means it takes a long time to create the project but when it is created it runs perfectly fast.
Is this behaviour by design and if so is there any way of turning it off or do you have any suggestions.
This problem is getting worse as many new rows are added into the table every day, when the database was small it was not a problem. I have already indexed optimally and checked the query execution plan in profiler.
Regards,
Spencer.
