To many SQL Data Sources?

[Drathmar]

I'm still pretty new to the Asp.Net world. I have a website that a user will have to fill out some forms. Several of these forms I want the entries to be standardized into drop down boxes. (for intstance, ethnicity) I'd like to be able to pull values from an 'ethnicty' table and well several other tables for other drop down boxes. How ever I have a concern, how many sqldatasource objects is to many? (Is it common practice to use as many as 10 different sql data sources on the same webpage?) How well does the .net code optimize these data sources? For example, on each datasource does it open a connection, run the query then close connection for all 10 sources? In general, if I ran the queries on page load and then set the values of the drop down boxes would/could that be more efficient? Or are there a better places than page_load to do that?? Any info on these questions would be greatly appreciated, thanks Drathmar

[Colin Angus Mackay]

Drathmar wrote:

How ever I have a concern, how many sqldatasource objects is to many? (Is it common practice to use as many as 10 different sql data sources on the same webpage?)

I wouldn't use any at all on a web page. I'd create a proper DAL (Data Abstraction Layer) and access the database through that and only that.

---

Scottish Developers events: * .NET debugging, tracing and instrumentation by Duncan Edwards Jones and Code Coverage in .NET by Craig Murphy * Developer Day Scotland: are you interested in speaking or attending? My: Website | Blog

[mysorian]

You should try looking at 'Factory' class which gives you an idea how to write database agnostic [generic] code.