Bonnie,

I'm very new to .Net. I took Kevin McNeishes class last week and he mentioned this to us. I clearly remember him giving this example, but--- if you ask me how technically MS is making it faster under the hood, you got me!!! I'm not at that level yet. ;-)

May be one of the other .Net experts can comment on 'how' MS is making ADO.Net 2.0 faster.

My main point to Jess was: with subsequent versions of VS, the data manipulation/visualization/retreival/binding will get better and better. Heck, in VS 2005, you can 'browse' a datatable in debugging mode by just clicking one icon next to the Watch window!!! I'm sure you know how difficult it is in VS2003.

Nevertheless, it will be interesting to see how much VS 2005 will solve Jess' problem of slow data binding/retrieval in VS 2003.

--Sid


>Sid,

Not to get into a major .NET discussion here, but I gotta wonder how you're getting that data for a 1 million row DataSet? If it's coming in over the wire, I don't see how 2.0 makes any difference, since the bottleneck would certainly not be from ADO.NET, but simply the speed of retrieving all that data. (SQL Server or what?)

Just curious ...

~~Bonnie

>>Regarding your problem with .Net: if it is ADO.Net then I think it's worth it to give VS2005 a shot. VS 2005 use ADO.Net 2.0 which is much much faster. With ADO.Net 1.1, creating a dataset with 1 million rows takes anywhere from 4 to 8 minutes. With ADO.Net 2.0, it takes well under a minute