We're  currently looking to move a portal to DNN, and covert a majority of our applications to DNN Modules.  We're currently using SQL Server 2000, and I don't see us changing very soon ( short maybe upgrading so SQL 2005 within a few years ).   All the modules we will be using will be strictly for internal use.  Are there any reasons why we would not want to create our data classes to access our database directly?

  It seems like the provider model adds a lot of extra overhead, and the only benefit it would provide is if we were switching databases or attempting sell the module.  Am I missing other benefits?  Opinions and insights are appreciated.  Thanks! 

I've made some very complex modules, talking 35+ tables, without using the DAL. Since 90% of my programming ends up being the re-tooling of stored procedures, there is just no way I'm going to spend the time to update the DAL layer for every single change.

Plus, the DAL tends to generate more round trips -- it's not at all effecient.

When I get back into module development using .NET 2.0, I'll be looking at the DAL again -- thanks for the update. But, I'm pretty sure I'll be sticking to good old ado application blocks... apparently they updated it for 2.0 now -- very exciting! (ya so who needs a girlfriend anyway?)

---

Jason Honingford - Web & Software Developer
www.PortVista.com