pros and cons of Typed and untyped dataset

[vrushalik]

Hi,

i want to know pros and cons of both Typed and Untyped dataset in detail.

can we customize untyped dataset?

What is benefit of Typed dataset?

is there significant difference between performance of Typed and untyped dataset?

is overhead in typed dataset is of XSD only or any else overhead is there?

What is benefit of using Untyped dataset?

Please give me some concret answers.



thanks

Vrushali

[Rahulbatra]

A strongly typed has some methods and properties in it that helps to make it more describing, does it still inherits from dataset. Also a "generated" strongly typed dataset is not easy to change. It is possible you will save a few cycles using untyped DataSets on the back end.

[Adrian]

The features of the DataSet object can be combined with XML to create a new type of object called the typed DataSet, which simplifies the task of data navigation. This is one of the benefits of typed dataset.

[sammy]

The nature of a DataSet requires that it is either typed or untyped. By definition a typed DataSet is any DataSet that is derived from the base DataSet class that applies the information contained in the XSD to generate a typed class. Information from the schema that contains the tables, columns, and rows is generated and compiled into a new DataSet derived from the XSD and this promotes the DataSet to a first class object in the .NET Framework. The process of inheriting the typed DataSet from the base DataSet class means that the typed class assumes all functionality of the DataSet class and can be used with methods that take an instance of the DataSet class as a parameter. This is the opposite of the untyped DataSet that has no corresponding schema and is exposed only as a collection.

[Corporate Gifts]

A typed dataset contains columns with strict types: Integers, dates, etc.

An untyped set treats all columns as strings, which you can cast explicitly to other types, such as numerics, dates, etc., outside the dataset (in your code).