I was improving my project performance when I realized that all my ADO actions delaied from 3 to 10s to connect to the database. Well, I have counted 13 ADO actions plus 3 for each item I build. Suppose I have a build of 100 items (witch is very common having more than this) I'll have to connect 313 times to the database and supossing each one delays 3s to connect so I'll have 15 minutes and 65 seconds only connecting to the database. So I thought about that xml action (XML Document Define) and thought about having one for database connections, that would be very usefull for me and other people that uses ado actions.
Thanks for the suggestion. I agree that reusing a connection can be very useful.
I'm actually surprised that this causes such a long delay, because I've read that ADO will cache database connections to avoid that very situation. Possibly this is the difference between a 3 second connection delay and a 10 second one, I don't know.
At any rate, the "ADO Connection Define" action is a good idea. I've added it to our To-Do list.
Regards,
Angus
PS I've moved this to the FinalBuilder wish list, because I think you were referring to FB.
I was taking a closer looking this weekend and realized that it’s not so long the delay (my dba just adjusted some databases configurations), but either, it’s using four connections (I think it’s opening one more for each included project I call).
Ps- I’m allways talking about finalbuilder, but I posted at automise because the ADO DataSet Iterator “issue” I posted at finalbuilder and got moved to automise…
