Datasets are known for their penalty caused by their size. So an immediate
question is: Are you sure you actually are in need of a dataset?
My experience with DS are more or less: Do not use!
A better approach is most often this:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.dotnet.framework.webservices&mid=a3a3e619-6131-4791-ad44-6f08bc7f6a79 You do not state the reasoning behind using the DS, but if it is just what
came out of an SQL select; I strongly suggest that you review your
systemdesign once more to eradicate use of such elements.
If you find that you can not live without, you might want to have a look at
DIME or MTOM to send the data using chunked mechanisms instead of one-shot.
--
rgds.
/Claus Konrad
MCSD.NET (C#)
[quoted text, click to view] "Evgeny.Br@gmail.com" wrote:
> Hi All,
>
>
> I use .NET 2.0.
>
> I experience huge performance problem retrieving dataset from web
> service.
> The dataset volume returned from WS is about 5-7 megabyte, it's take
> too long.
>
> Is it possible to compress dataset in some way in the WS send to
> client, and decompress
> in the client, if yes how???
>
> Maybe there is another way to pass huge datasets from WS, maybe IIS ??
>
> To do this asyncronously or in batches is not suitable for my problem.
>
> Any ideas??
>
> Thanks in advance.
>
>
>
>
> I too face the similar problem.What we did is to serialize the entrie
> dataset to byte array and transmits it through the wire.Before
> serializing we did convert the datasets to arrays and used gzip
> copression after
>