I will be placing SQLDataSource examples here shortly.

I know there is controversy relating to placing SQL or even Stored Procedure names in .aspx files, but the reality is that for some applications, there is no need to concern ourselves with the complexities related to N-tiered, fully-abstracted, technical-utpoia development. This is especially prevalent when the resources working on an implementation do not have the background or ability (for a variety of reasons not always their own doing) to deliver solutions with these concepts intact each time.  Certainly, Microsoft must have agreed as they allow/support this approach.  None-the-less, feel free to engage in healthy discussion here.  And I hope this area will be useful for those who know the pros and cons, and make the educated decision to use the SQLDataSource inside their .aspx pages.

Related Information:

1. RDL and RDLC Conversion - SSRS (Reporting Services) and ReportViewer

   RDL and RDLC conversion is something that people who use both Reporting Services and ReportViewer have already done. For those...

2. asp:ControlParameter vs. asp:FormParameter in Master Page

   I hit what I considered to be an annoying “issue” in ASP.NET 2.0 the other day that I thought I...

3. Oracle on Amazon EC2 Cloud - APEX, Apps, Middleware, and DB Virtualized Hosting

   The economy is evolving, technology is getting better, and overall, the game is changing with cloud computing. M&S is now...

4. Oracle BAM Sucks, For Now

    Our team has been working with BAM since Oracle took it on (we rolled out BAM reports in 2007).Â...

5. Oracle SUBSTR with INTSR Function - SQL Syntax Examples

   Oracle SUBSTR and INSTR SQL functions are typically used together in practice for parsing a string. Following are...

6. Oracle Portal HTML Templates - Page Skins, Content Layouts and More

   I have seen a large number of Oracle Portal implementations, and even a fair number using Portal version 10.1.4. It...