Best practise making a Data Access layer in .NET.

  • Thread starter Thread starter Geir Holme
  • Start date Start date
G

Geir Holme

Hi all.
Could anyone guide me to some innformation on "Best Practise" on the matter
of designing a Data Access Layer for our klient.

We are starting to convert from VB6 to .NET. Our VB app is a single layer
app, but we do want to get the data access layer out (as recomended). Any
guidlines/experiences on this topic would be great.

Using .NET and SQLServer2000.

We want one .dll for the klient and one for the web. Mabe place the files on
som kind of Message queing.

Thanx all.

-geir
 
Hey,

You should look over the Data Access Block for SQL Server provided by MS. It's
really nice for and very comprehensive. At the very least it will give you some
great ideas.

Fred
 
Thanks for Brian and Fred's quick response!

Hi Geir,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you would like to get some suggestions
about how to build the data access tier for your application. If there is
any misunderstanding, please feel free to let me know.

Brian and Fred has provided us with a good suggestion to use Data Access
Application Block for .NET to build the data access tier. The Data Access
Application Block is a .NET component that contains optimized data access
code that will help you call stored procedures and issue SQL text commands
against a SQL Server database. It returns SqlDataReader, DataSet, and
XmlReader objects. You can use it as a building block in your own
.NET-based application to reduce the amount of custom code you need to
create, test, and maintain. And you can download the source code and
documentation for free from the link Brian provided.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/
daab-rm.asp

Also, if you would like to build the Data Access tier yourself without
using tools, you can check some of architectural sample applications on
MSDN. I think they are the best practices on building .NET multi-tier
applications. Pet Shop and Duwamish are well-known ones. They can be
downloaded from the following links:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/
petshop3x.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dwamish7/ht
ml/vtoriarchitecturaloverview.asp

HTH. If anything is unclear, please feel free to reply to the post.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Thank you all.

I hope you know how much this kind of information means for us "rather
small businesses" here in Norway. Your understanding of the problem is
100% corect and I am diving into the Block right away. Having that I
will take a look at the two examples and deside from there.

Our goals:
We need a fast and scaleable dataaccess solution to keep up with the
WebShop traffic agins our customers data along with the klient
application traffic.
We do hosts many of the WebShops arround Norway and it all runs on
Microsoft plattforms. We are preparing for more traffic and scalability.

Thans again all.

-geir
 
Hi Geir,

You're welcome. Thanks for sharing your experience with all the people
here. If you have any questions, please feel free to post them in the
community.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Back
Top