FOr DNN, is there any good reason to place SQL in a stored procedure and not in code.  I am looking at this issue from a performance and maintainability issue.  I know that with a complex module, it would be best to have the SQL in a procedure rather than directly in the program.  The reason I am asking is he is I'd planned to upgrade the module to work with LINQ in the future and that technology does processing in code rather than in SQL procedures.

Any comments would be helpful

thank you

Example code:

Try
                Return CBO.FillCollection(Of xxxxControlInfo)(CType( _
                    DotNetNuke.Data.DataProvider.Instance(). _
                    ExecuteSQL(sql, pa), _
                    IDataReader))
            Catch ex As Exception
                Throw New Exception(ex.Message)
            End Try