Forum Moderators: open
- Was it to reduce redundant code?
- To have a consistent data access that could easily be maintained?
- Did you need to have application portability?
For me I'm curious about the portability benefits. The Database class lets you hook into MS SQL, Oracle or DB2 but will you still get good performance when it ports to say oracle or DB2 if you've written and optimized the initial implementation for ms sql?
As for as using with something else besides SQL server I can only guess, but as far as I know the application blocks are really just functions and methods that still use the underlying data provider that is required for access to the type of database that you are using. So if you use the Oracle stuff it will still use the Oracle data provider.