Re: Inline SQL or stored procs for my C# windows app?
- From: Burt <burt_5920@xxxxxxxxx>
- Date: 23 Apr 2007 13:38:12 -0700
Thanks all. Nicholas you wrote:
Honestly, I would use something like the Data Access Application Block
in the Enterprise Framework that is offered by Microsoft. It will help
mitigate using stored procedures and changing from one database to another
(you won't have to worry about changing how you call stored procedures from
managed code, for example), and you can use the object model exposed by it
to generate dynamic sql that will work across any database that has a
provider for the DAAB, assuming you don't use any database-specific features
in your SQL.
My next question was actually about the DAAB. At my current company
we're using it. At my last job, we just had a shared class called
"Data Access" which all programmers used. It was one level, and just
had some basic "GetDataReader", "GetDataSet", etc methods. The DAAB
sure does seem like a lot of overhead. Occasionally it will throw an
error which I'll have to Step through through a few Microsoft code
files to figure out. But I see there are benefits, like the one
above.
Burt
.
- References:
- Inline SQL or stored procs for my C# windows app?
- From: Burt
- Re: Inline SQL or stored procs for my C# windows app?
- From: Nicholas Paldino [.NET/C# MVP]
- Inline SQL or stored procs for my C# windows app?
- Prev by Date: Re: converting 4bytes(32bits) to float
- Next by Date: Re: Object reference not set to an instance of an object
- Previous by thread: Re: Inline SQL or stored procs for my C# windows app?
- Next by thread: Re: Inline SQL or stored procs for my C# windows app?
- Index(es):
Relevant Pages
|
