Re: Is this a good application Design?
Hi all;
Three tier architecture is very use ful for distributed application; You can
do one thing make some common classes for common functions and use sqlhelper
class as a DAL (Data Access Layer); dont customize sqlhelper class becauase
this can be use for all applications.
you can also customize your shared functions and pass sql statement as
string and can pass perameter according to condition; but you should use
stored procedure;
thankx
"Eliyahu Goldin" wrote:
[color=blue]
> Sometimes it is the best practice. You can change from one platform to
> another without affecting the business logic implemented in stored
> procedures.
>
> Eliyahu
>
> "Kim Quigley" <kimquigley@hot mail.com> wrote in message
> news:%23n%23QjX ndFHA.4040@TK2M SFTNGP14.phx.gb l...[color=green]
> > I wasn't aware that putting SQL in the business layer was a best practice.[/color]
> I[color=green]
> > use SQL Server 2000 with stored procedures and my data layer accesses[/color]
> those[color=green]
> > stored procedures. In the business layer, I have logical business objects
> > with properties and methods. The purpose of having a seperate data layer[/color]
> is[color=green]
> > so that if your data source changes (for example: moving from SQL Server[/color]
> to[color=green]
> > MySQL) then you only have to modify the data layer. The presentation and
> > business layers would be unaffected.
> >
> >
> > "Josh" <s@a.com> wrote in message
> > news:OS2sZKndFH A.3324@TK2MSFTN GP10.phx.gbl...[color=darkred]
> > > Your SQL should be in the Business Layer. The presentation layer should
> > > not make or provide decisions on how data is collected ( that what[/color][/color]
> tables[color=green][color=darkred]
> > > / view or columns are used ) as that is a business rule.
> > >
> > >
> > >
> > > "Jay Balapa" <jbalapa@hotmai l.com> wrote in message
> > > news:%23zUYpHnd FHA.3488@tk2msf tngp13.phx.gbl. ..
> > >> Hello,
> > >>
> > >> Currently my application has three tiers-
> > >>
> > >> 1. Presentation Layer (Asp.Net / Win Forms/ Pocket PC UI.)
> > >> This predominantly contains User Controls, Custom Controls and Win/Web
> > >> Forms.
> > >> I have one base form and I inherit from that form.
> > >> All validation is done in this tier. There is zero Data Access code in
> > >> this tier. This tier exclusively gets DataViews/ Arays/Lists as input.
> > >> Outputs are string objects with SQL Statements or just paremeters with
> > >> dataconnection key.
> > >>
> > >> 2. Business Layer.
> > >> Currently this is just a Library residing in the same machine as
> > >> Presentation layer. Eventually I plan to use WebServices if application
> > >> needs physical seperation.
> > >> Most of Business Logic are implemented in this layer. There is[/color][/color]
> absolutely[color=green][color=darkred]
> > >> no UI code here.
> > >> These are all bunch of static methods which perform CRUD functionality.
> > >> All methods are atomic in nature. I dont rely on Static Variables.[/color][/color]
> There[color=green][color=darkred]
> > >> is just one DatabaseGateway class which does all the functionality.
> > >>
> > >> 3. Data Layer. (SQL Server)
> > >> I dont use stored procedures. predominantly use Views.
> > >>
> > >>
> > >> I have been reading up on Rockford Lhotka's business objects and I just
> > >> feel that his framework is unnecessarily complex. I just dont see the
> > >> need to hold these intermediate Business Objects.
> > >>
> > >>
> > >>
> > >> Thanks for your responses.
> > >>
> > >> --
> > >> Jay Balapa
> > >> Director Of Software Engineering
> > >> www.atginc.com
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >[/color]
> >
> >[/color]
>
>
>[/color]
Hi all;
Three tier architecture is very use ful for distributed application; You can
do one thing make some common classes for common functions and use sqlhelper
class as a DAL (Data Access Layer); dont customize sqlhelper class becauase
this can be use for all applications.
you can also customize your shared functions and pass sql statement as
string and can pass perameter according to condition; but you should use
stored procedure;
thankx
"Eliyahu Goldin" wrote:
[color=blue]
> Sometimes it is the best practice. You can change from one platform to
> another without affecting the business logic implemented in stored
> procedures.
>
> Eliyahu
>
> "Kim Quigley" <kimquigley@hot mail.com> wrote in message
> news:%23n%23QjX ndFHA.4040@TK2M SFTNGP14.phx.gb l...[color=green]
> > I wasn't aware that putting SQL in the business layer was a best practice.[/color]
> I[color=green]
> > use SQL Server 2000 with stored procedures and my data layer accesses[/color]
> those[color=green]
> > stored procedures. In the business layer, I have logical business objects
> > with properties and methods. The purpose of having a seperate data layer[/color]
> is[color=green]
> > so that if your data source changes (for example: moving from SQL Server[/color]
> to[color=green]
> > MySQL) then you only have to modify the data layer. The presentation and
> > business layers would be unaffected.
> >
> >
> > "Josh" <s@a.com> wrote in message
> > news:OS2sZKndFH A.3324@TK2MSFTN GP10.phx.gbl...[color=darkred]
> > > Your SQL should be in the Business Layer. The presentation layer should
> > > not make or provide decisions on how data is collected ( that what[/color][/color]
> tables[color=green][color=darkred]
> > > / view or columns are used ) as that is a business rule.
> > >
> > >
> > >
> > > "Jay Balapa" <jbalapa@hotmai l.com> wrote in message
> > > news:%23zUYpHnd FHA.3488@tk2msf tngp13.phx.gbl. ..
> > >> Hello,
> > >>
> > >> Currently my application has three tiers-
> > >>
> > >> 1. Presentation Layer (Asp.Net / Win Forms/ Pocket PC UI.)
> > >> This predominantly contains User Controls, Custom Controls and Win/Web
> > >> Forms.
> > >> I have one base form and I inherit from that form.
> > >> All validation is done in this tier. There is zero Data Access code in
> > >> this tier. This tier exclusively gets DataViews/ Arays/Lists as input.
> > >> Outputs are string objects with SQL Statements or just paremeters with
> > >> dataconnection key.
> > >>
> > >> 2. Business Layer.
> > >> Currently this is just a Library residing in the same machine as
> > >> Presentation layer. Eventually I plan to use WebServices if application
> > >> needs physical seperation.
> > >> Most of Business Logic are implemented in this layer. There is[/color][/color]
> absolutely[color=green][color=darkred]
> > >> no UI code here.
> > >> These are all bunch of static methods which perform CRUD functionality.
> > >> All methods are atomic in nature. I dont rely on Static Variables.[/color][/color]
> There[color=green][color=darkred]
> > >> is just one DatabaseGateway class which does all the functionality.
> > >>
> > >> 3. Data Layer. (SQL Server)
> > >> I dont use stored procedures. predominantly use Views.
> > >>
> > >>
> > >> I have been reading up on Rockford Lhotka's business objects and I just
> > >> feel that his framework is unnecessarily complex. I just dont see the
> > >> need to hold these intermediate Business Objects.
> > >>
> > >>
> > >>
> > >> Thanks for your responses.
> > >>
> > >> --
> > >> Jay Balapa
> > >> Director Of Software Engineering
> > >> www.atginc.com
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >[/color]
> >
> >[/color]
>
>
>[/color]
Comment