Database design - layers

From an ASP.NET perspective is it common to layer the database integration like this for example:

Db access layer
Performs raw queries and handles the connection and other low level functions. If this was a class, it would probably not need any changes if you implemented it to another application, simply because the next layer does the app specific stuff.

Db 'abstraction'/app interface layer
Higher level functions which interface between the front end and db access layer. Contains app specific functions like getProducts().

Cheers
Chris

Similar to what i do, but i call the Db 'abstraction'/app interface layer a Business Layer in my apps.

Normall i would create a Data Layer folder and Business Layer folder.

Within the Data Layer folder i would also place parameter collection classes, which will be used by a stored procedure.

And the Business Layer folder would hold a number of classes that would interact between the web front end and the data layer. Each business class would hold a number of function. E.g. cContracts.vb will hold a number of functions like SelectContract, UpdateContracts, DeleteContract, SearchContracts... etc

e.g. Example image below

Cheers Kev I will keep this in mind.

Chris