I've just started to try out the Visual Builder environment (as found in the latest beta release) and have the following feed back (for which there maybe config fixes for but I'm not currently aware of).
1) It seems that VB often tries to find out the number of underlying records in a table/view by doing a
SELECT COUNT(*) FROM X WHERE ('1'='1')
This has a major impact on performance if the table is very large or the view depends on additional constrants to limit it's logical size.
2) There is no attempt to control the issue of spaces within column names, For a MSSQL based link this would mean placing each column name within [].
3) In the Database Browser screen it would be very helpful to have the ListGrid that shows the tables and views defined with a filter editor as this would improve the speed that a table/view can be found in a large system. This also solves the issue I see with MSSQL connections where all the system views are listed as well as the database view.
Apart from the above, my eval is going as well as you can expect for someone who has not used the product before :)
Thanks
Roger
1) It seems that VB often tries to find out the number of underlying records in a table/view by doing a
SELECT COUNT(*) FROM X WHERE ('1'='1')
This has a major impact on performance if the table is very large or the view depends on additional constrants to limit it's logical size.
2) There is no attempt to control the issue of spaces within column names, For a MSSQL based link this would mean placing each column name within [].
3) In the Database Browser screen it would be very helpful to have the ListGrid that shows the tables and views defined with a filter editor as this would improve the speed that a table/view can be found in a large system. This also solves the issue I see with MSSQL connections where all the system views are listed as well as the database view.
Apart from the above, my eval is going as well as you can expect for someone who has not used the product before :)
Thanks
Roger
Comment