Page 1 of 1
Find out, why dataset uses so long
Posted: Wed 07 Mar 2007 10:21
by Zero-G.
Hey
I am using v. 3.5
How can I find out, why retriving data through a dataset uses such a long time.
I have created a dataset, with the dataset Designer. - The SQL Statement is not very complicated & when I use the code in the mySQLControlCenter, it takes 0,08 sec to give back the information. - But when I use the dataset, it takes up to 8 sec.
How can I find out, what the problem is?
Second question: - When will the finished v4 be available?
THX
Posted: Wed 07 Mar 2007 11:22
by Alexey
I suppose the time is consumed for opening a connection to MySQL server.
Posted: Wed 07 Mar 2007 11:29
by Zero-G.
Hey
But I do use more datasets (designed through the designer) - And there it works really fine.
No idea for the second question?
THX
Posted: Wed 07 Mar 2007 11:47
by Alexey
But I do use more datasets (designed through the designer) - And there it works really fine.
You mean you have many datasets and only one of them works so slow? Maybe it is connected with connection pooling.
No idea for the second question?
We are going to release MySQLDirect .NET 4.0 in two weeks.
Posted: Wed 07 Mar 2007 12:04
by Zero-G.
You mean you have many datasets and only one of them works so slow? Maybe it is connected with connection pooling.
Yes, that is correct - How do I turn off connection pooling in a designed DataSet?
We are going to release MySQLDirect .NET 4.0 in two weeks
Will the registered users be informed by mail? - Because I would like to know, when the new version is out!
THX
Posted: Wed 07 Mar 2007 12:56
by Alexey
How do I turn off connection pooling in a designed DataSet?
I cannot say for sure that the problem is in pooling. Please describe in detail how you use datasets. You may send me small test project to reproduce the problem. Include definitions of your own database objects. Use e-mail address provided in the Readme file.
Will the registered users be informed by mail?
Yes, you will be notified via e-mail.