.NET application architecture involving heterogeneous data sources

[Simeon Lobo]

Hello All,

I am in the process of building a proof-of-concept ASP.NET reporting
application that compares using a DataSet to hold information from various
data sources (SQL Server 2000 and Oracle 8i).

The above solution will be compared in terms of performance to a similar
proof-of-concept ASP.NET application connecting to a SQL Server linked
servers implementation and using DataReaders (our SQL Server will have
read-only access to the remote server, in this case Oracle 8i and the sample
ASP.NET app will run a stored proc against the SQL Server only).

Since we are attempting to build a reporting application, the key priority
is performance. As a benchmark I would like to display 10000 records within
a sub-second response times. I plan to load test each implementation with
60-100 concurrent users.

I would appreciate any feedback regarding the above implementations. I've
read that using linked servers is network resource intensive, while using
DataSets is not recommended to persist large amounts of data (and all I
really need to do is retrieve data, no INSERTS/UPDATES/DELETES).

Thank you for your help/feedback in advance,
Simeon

[RiteshDotNet]

use object and that object is directly map with ur table , if you are
fetching data from multiple table then use view and create object for that
view, and fill data by using datareader into object. You can also see
example into petshop application they have implemented in same manner.

"Simeon Lobo" wrote:

Hello All,

I am in the process of building a proof-of-concept ASP.NET reporting
application that compares using a DataSet to hold information from various
data sources (SQL Server 2000 and Oracle 8i).

The above solution will be compared in terms of performance to a similar
proof-of-concept ASP.NET application connecting to a SQL Server linked
servers implementation and using DataReaders (our SQL Server will have
read-only access to the remote server, in this case Oracle 8i and the sample
ASP.NET app will run a stored proc against the SQL Server only).

Since we are attempting to build a reporting application, the key priority
is performance. As a benchmark I would like to display 10000 records within
a sub-second response times. I plan to load test each implementation with
60-100 concurrent users.

I would appreciate any feedback regarding the above implementations. I've
read that using linked servers is network resource intensive, while using
DataSets is not recommended to persist large amounts of data (and all I
really need to do is retrieve data, no INSERTS/UPDATES/DELETES).

Thank you for your help/feedback in advance,
Simeon