is it better to use multiple asp.net sqldatasource control or programatically populate?

I am regulating mixed sqldatasource controls to stock multiform web controls upon my page. we was wondering if it would be improved to do it so upon page_load in a formula behind, to programmatically open a tie perform all a queries as well as afterwards tighten a connection. Is it improved in conditions of opening as well as connectors to a database to do it which way?

One thought on “is it better to use multiple asp.net sqldatasource control or programatically populate?

  1. It’s always better to code it yourself. You have no idea what the code in the control is doing. Sometimes you run into a problem because of sloppy coding in a control – with a Microsoft control, you can beat your head on the keyboard for weeks before stumbling on some solution, because you never find out that your code is good, but their control has a bug.

    If you write it yourself, it’s lighter, and you know what it;s doing.

    Opening the connection only when you need it is better for the database. The performance hit is barely measurable on today’s computers. (What’s a few microseconds?)