Devart Forums

My Application with version 3.02 needs about 30 seconds to start. Now with the version 4.0 I must wait about 120 seconds. I have changed no parameter. The app start with 50 tables. What can I do?

Please specify, do you mean the time for loading your project in IDE, or the time when the application buld from your project starts?

After I compiled it and then I start the application (*.exe).

Please try to determine what SDAC functionality caused such performance loss, and send us, if it is possible, a complete small sample project that demonstrates this problem, including script that creates server objects for the test project.

Also specify the following information:
- exact version of Delphi, C++Builder or Kylix you are using;
- exact version of MyDAC. You can see it in the About sheet of TMyConnection Editor;
- exact version of MySQL server and MySQL client. You can see it in the Info sheet of TMyConnection Editor.

I'm working with Delphi 7 Build 8.1 with all SP
MS SQL Server 2000 with all SP
MDAC Version 2.81.1117.0
SDAC Version 4.000.0.7

It's not possible to send you this project.


procedure dm1.datamodulecreate ...
begin
MSLogin.active := true ;
MSConnection.connected := true ;
// So I Start ~ 50 TMSTables
MSTAble1.active := true ;
MSTable2.active := true ;

//and so on

end

all MSTable with fetchall := true ;
fetchrows := 5 ;

In Version SDAC 3.00.02 the app starts on the Desktop after 30 sec. and with 4.000.0.7 after 120 sec.

Please check the value of TMSConnection.Options.Provider. If it is set to prAuto or prNativeClient, change it to prSQL, and try to run your application again.

I set Provider to prSQL.
But the result is not better. ;-(
200 sec!

Please note down the connection time, and the open time for each table you open. A way to do this is to make a method that writes to a log file the object name, and time taken from the QueryPerformanceCounter method, and assign this method to BeforeOpen and AfterOpen events of every TMSTable component.
Build your application with SDAC 4 and run it to create the log file. Repeat the same with SDAC 3, and compare these files. This should help to determine what object(s) causes this problem.

You could also use SQL Profiler to log what queries are running during startup, together with the duration of each query, for both versions of SDAC. Then compare the trace results.

This way, you don't have to modify your code (yet).