Win2k/Com+/VB.NET/SQL Server 2k/XP


Can anyone advise me on the following

We have a 3 tier application
1. Client runs vb.net forms on XP
2. Server runs vb.net dlls in COM+ talking to a database on the same =
machine
3. Client Server connectivity is via DCOM, ie export client package from =
the server pacakge


When the client makes a simple call to retrieve 10 records, which are =
returned as a datatable, over 2 mb of network traffic is generated. The =
records account for only 10k or so

Has anyone any ideas in terms of how to break this problem down, or is =
this what we should expect with COM & dotnet.=20

This sounds as a bit too much overhead.
:-)

Sending datatables over the wire is often a bit expensive. Often 3-5 =
times larger than the same data in an ordinary collection, but... Have =
you serialized the datatable at the server-side into a file and =
investigated the file to see its size and if it contains what you =
expect?

Best Regards,
Jimmy
www.jnsk.se/weblog/
###
[quoted text, click to view]
Win2k/Com+/VB.NET/SQL Server 2k/XP


Can anyone advise me on the following

We have a 3 tier application
1. Client runs vb.net forms on XP
2. Server runs vb.net dlls in COM+ talking to a database on the same =
machine
3. Client Server connectivity is via DCOM, ie export client package =
from the server pacakge


When the client makes a simple call to retrieve 10 records, which are =
returned as a datatable, over 2 mb of network traffic is generated. The =
records account for only 10k or so

Has anyone any ideas in terms of how to break this problem down, or is =
this what we should expect with COM & dotnet.=20