Strongly Typed Datasets (.net 2)?

Question

Strongly Typed Datasets (.net 2)?

Ray Herring

SSCertifiable

Points: 5533
More actions
February 26, 2007 at 11:18 am

#98173

This not strictly a SQL question. I am wondering if anyone is doing n-tier development using Strongly Typed Datasets in the data access layer and stored procedures in the database?
We are doing a project now and I would be interested in sharing experience. We are currently using Vb.net 2.0 and SQL 2005 to develop a WinForm client app, a web services Business/Data layer, and the backend database.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

BeerBeerBeer SSCarpal Tunnel Points: 4021 More actions · Answer 1

We did some of this about 4 years ago under .Net 1.1 and c#.

While you get great intellisense out of your objects, we found that we struggled with the maintenance whenever we needed to change a database object. Perhaps we weren't going about it the right way though. We haven't used them since.

Our system involved SQL Server 2000 backend, with WebServices (where we did the strong datatyping) in front of the data acting as the gateway for the application to access the data.

I think from memory our biggest issue was ensuring that the datatyping made it's way past the webservices boundary and into the application.

Like I say, it might well have been our inexperience with this functionality and our inability to get the stroing typing working across the webservices-application boundary.

Seemed to be ok inside the webservices though.

Regards,

Steve

Life without beer is no life at all

All beer is good, some beers are just better than others

Lowell SSC Guru Points: 323518 More actions · Answer 2

similar issues here that Steve reported;

we started using strongly typed data sets, and found issues when the underlying structure changed...if we added a column to a table, for example, the data set was no longer valid, and we'd have to update it.

We also had to make a lot of changes to our data access layer so that we could have views or virtual tables that would never be updated , or columns that were calculated that did not exist in the actual table; little things like firstname + ' ' + lastname as name would be difficult witht he strongly type set vs a LoadDataTable command to a normal? datatable

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

bledu SSChampion Points: 12335 More actions · Answer 3

i had the same experience as above. I was using .net 1.1 and sql 2000 backend. when ever we changed the underlying tables, it was hell.

the upside is probably that you can use the dataset designer.

Everything you can imagine is real.