Hi,
We are loading the Limits from Access with 'OpenDatabase Step', 'OpenSQLStatement Step' and the 'Property Loader'. This worked fine for years. Now we moved the Limit-Database to an SQL-Server. The SQL-Querry remained absolutly the same because the Database Schema is the same:
SELECT Tbl_Stepname.Stepname, Tbl_StepLimit.LowerLimit, Tbl_StepLimit.UpperLimit, Tbl_StepParam.ParaString
FROM Tbl_StepParam INNER JOIN (Tbl_Stepname INNER JOIN (Tbl_StepLimit INNER JOIN Tbl_SeqProperty ON Tbl_StepLimit.StepLimitId = Tbl_SeqProperty.StepLimitId) ON Tbl_Stepname.StepNameId = Tbl_SeqProperty.StepnameId) ON Tbl_StepParam.StepParamId = Tbl_SeqProperty.StepparamId
WHERE Tbl_SeqProperty.LimitParamSetId=112;
For Loading the Limits and the InBuffer the Step-Property-Loader needs !!! 17.257 sec !!! when we are working with the SQL-Server (to load 143 Steps).
The Same Data with the Access-Database needs 0.154 Sec.
I don't unterstand what the Step-Property-Loader is looking for.
Of Course in the SQL-Server-Database are much more data, but the result of the mentioned querry is 143 Records.
The previous Open SQL-Statement-Step works very fast and the local variable 'NumRecords' has the value of 143 as expected.
I tested the Querry with the Database-Viewer-Tool in TestStand. No Performance Problem occured. I also tested the Querry in the SQL-Server-Managment Studio and
everthing works fine.
We have installed:
-SQL-Server 2008
-TestStand 4.2 (Engine 4.2.1.83)
-CVI-2010 10.0.1 (419)
Does anybody know these problem? Perhaps we have to update TestStand to a newer Version?
Thank you for your help
Best Regards
Paul Bühlmann