RE: Designing of database system based on .net

From: Cowboy (Gregory A. Beamer) - MVP (NoSpamMgbworld_at_comcast.netNoSpamM)
Date: 09/17/04 

Date: Fri, 17 Sep 2004 04:49:19 -0700

I recommend stored procedures for data access, as it adds a security layer.

How to separate tiers? With data access only, you really do not have to, as
ADO.NET can contact a SQL Server instance anywhere it can actually reach it.
There is no need, in most instances, to add the extra weight of web services
(whether remoting or ASMX). On the other hand, a data tier that uses web
services is perfect for a very loosely coupled environment (SOA - Service
Oriented Architecture).

The middle tier can either be wrapped DataSets (the quick and easy method)
or actual business objects. Business Objects get easier with ObjectSpaces in
Framework 2.0. Lhotka has an interesting object theory in his books on VB.NET
and C# Business Objects (two different books). They are worth a read for one
theory on objects. The theory is not completely compatible with ObjectSpaces,
which, as I stated, comes in with 2.0 in 2005. 

---
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"Hawix" wrote:
> Hi,
> 
> I try to know a Framework.NET platform in the light of the medium size of
> database system.
> 
> Background:
> I want to build system for about 200 users which will be connected in one
> moment to database. User interface will be developed using Windows.Forms
> technology. System is based on SQL database which is connected using the
> ADO.NET. But, both the UI and database aren't problem.
> 
> It's a very intresting subject how to make database access for this
> application. In this case I see two .NET technologies which help me create
> third-tired application: "Remoting" and "XML Web Services".
> There is, too, a very "strong" object named "DataSet".
> 
> Questions:
> 1. Could anybody help me and tell how to deploy objects according for a
> client and server side?
> 2. Which of practices is better:
> - build SQL statments (INSERT, UPDATE, DELETE, SELECT) on buissnes layer,
> - or buisness layer use stored procedures only?
> 
> ---
> Best regards,
> Hawix
> 
> 
>

Relevant Pages

  • Looking for a decent data access architecture to implement
    ... application so that there is a clean separation between the data access ... layer, the business layer and the GUI layer. ... the actual database. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Looking for a decent data access architecture to implement
    ... > application so that there is a clean separation between the data access ... > layer, the business layer and the GUI layer. ... > the actual database. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: OOP question --- theoretically speaking....
    ... >database access components, you have to rewrite your class all over again. ... >It really is better and more beneficial to have a separate data layer that ... initially hosted each tier as serviced components and serialised chunks ... of the domain model out to the web UI layer via a service layer (kind of ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Am i thinking correctly?? business objects inserting to database
    ... We are building the new application using a 3 tier ... What I generally do is create a class for each business object. ... classes themselves know nothing of the database. ... Next I create Data Access layer that knows how to take a Value object ...
    (microsoft.public.dotnet.general)
  • Re: Data Access Layer
    ... > Could you point me to a good resource for creating my data access ... I have my database, I have me front end, but I want a nice ... > layer between them so I can just call functions in my code behind ... which is a Data Access Application Block. ...
    (microsoft.public.inetserver.asp.db)
Loading