Site Sponsored By: SQLDSC - SQL Server Desired State Configuration
Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Well I havent used these much so I started reading a bit on them.But most people say "o they are so cool cause they give me intellisense"...fine and dandy but has anyone run any benchmark tests on stronly typed datasets or should I wait for whidbey ?I mean whats the performance like vs using the sql command object and invoking a stored procedure and then using the dictionary form?What about serialization? Adding / Modifying / Deleting / etc....Has anyone used them in their applications now ?Keeping the web experience alive -- [url]http://www.web-impulse.com[/url]Imperfection living for perfection -- [url]http://jhermiz.blogspot.com/[/url]
spirit1
Cybernetic Yak Master
11752 Posts
Posted - 2005-03-13 : 14:44:04
i use them. they're pretty cool. although if you rename the column name you have to drop and recreate the whole dataset.ok, you don't have to but it's better than changing it in n places...they're ver easy to work with and i haven't seen any downside to them.some will complain that having more than 50k rows in it willl amke it slow but i don't think that's a dataset problem.don't put 50k rows on the client. Go with the flow & have fun! Else fight the flow
TG
Master Smack Fu Yak Hacker
6065 Posts
Posted - 2005-03-13 : 16:17:15
If your application architecture requires serialization/deserialization via SOAP, the proxy objects can be pretty big. If there are a lot of these datasets that need to go through that process at one time (like at startup) it can be quite a time consuming process.Be One with the OptimizerTG
jhermiz
3564 Posts
Posted - 2005-03-13 : 17:08:18
quote:Originally posted by spirit1 i use them. they're pretty cool. although if you rename the column name you have to drop and recreate the whole dataset.ok, you don't have to but it's better than changing it in n places...they're ver easy to work with and i haven't seen any downside to them.some will complain that having more than 50k rows in it willl amke it slow but i don't think that's a dataset problem.don't put 50k rows on the client. Go with the flow & have fun! Else fight the flow
The benefit is...????Dont tell me intellisense...Got any sample code...Is it just to keep things neat and tidy ?Keeping the web experience alive -- [url]http://www.web-impulse.com[/url]Imperfection living for perfection -- [url]http://jhermiz.blogspot.com/[/url]
rockmoose
SQL Natt Alfen
3279 Posts
Posted - 2005-03-14 : 04:07:53
Maybe a typed dataset is just something that helps you with the typing rockmoose
spirit1
Cybernetic Yak Master
11752 Posts
Posted - 2005-03-14 : 04:27:04
http://www.dotnetjunkies.com/Tutorial/83DA8FC4-79D1-477C-9D5E-70444A476270.dcikHow to add a row:DataSetInput ds = new DataSetInput();DataSetInput.InputRow dr = ds.Input.NewInputRow();ds.Input.AddInputRow(dr);TypedDataset.TableName.RowPropertiesAndMethodsGo with the flow & have fun! Else fight the flow