Designing of database system based on .net

[Hawix]

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?

 

[Guest]

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!
***************************

 

[duncan]

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?

I cannot help with Q1 but Q2

I personally would use store procedures and pass the data as an XMl
document. That way you can pass quite complicated data with 1 call,
the database can validate and then in one transaction update 1 or more
tables. The called store proc could call other store procs to
complete its work. Security is improved as you would remove all
persmissions from tables and views to the users and grant execute
permissions only on the store procs.

Hope this helps



Duncan