ASP.NET on SQL Server

I've been asked to quote for developing a system to expose data on a
web application. Most of the data will come from SQL Server DBs
located on a single box. However, some of the data will be sourced
from ORACLE which is located on a different box. It may be necessary
to create VIEWS and Stored Procedures joining these DBs

Does anyone have any pointers, clues, hints, tips or pitfalls that I
might consider while making my proposal? What sort of extra
contingency should I allow for the connection to ORACLE? Should I do
all the data retrieval on the DB server, or should I do it on the Web
server?

Any thoughts would be appreciated.

Thanks

William Balmer

William wrote:
> ASP.NET on SQL Server
>
> I've been asked to quote for developing a system to expose data on a
> web application. Most of the data will come from SQL Server DBs
> located on a single box. However, some of the data will be sourced
> from ORACLE which is located on a different box. It may be necessary
> to create VIEWS and Stored Procedures joining these DBs
>
> Does anyone have any pointers, clues, hints, tips or pitfalls that I
> might consider while making my proposal? What sort of extra
> contingency should I allow for the connection to ORACLE? Should I do
> all the data retrieval on the DB server, or should I do it on the Web
> server?

Look into the Linked Server features of SQL server. You can link to the
Oracle db & run queries against the Oracle db thru SQL server. This may
reduce the maintenance - you'll only be writing in SQL Server syntax, or
calling SQL Server stored procedures that query the Oracle db.
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

"Linked Server" can be one way to do this. However general network
latency and throughput restrictions due to bandwidth limitations or
network traffic, etc. can completely kill joins across the wire.

Also, be prepared to write views on the Oracle box to convert Oracle
data types to be more compatible with Sql Servers needs even using
linked servers.

Another option to consider it to "replicate" the data from the Oracle
box onto a Sql Server box, avoiding the need for joins across the wire.
This is the option I had to take to get acceptable performance for one
job I did.


William wrote:
> ASP.NET on SQL Server
>
> I've been asked to quote for developing a system to expose data on a
> web application. Most of the data will come from SQL Server DBs
> located on a single box. However, some of the data will be sourced
> from ORACLE which is located on a different box. It may be necessary
> to create VIEWS and Stored Procedures joining these DBs
>
> Does anyone have any pointers, clues, hints, tips or pitfalls that I
> might consider while making my proposal? What sort of extra
> contingency should I allow for the connection to ORACLE? Should I do
> all the data retrieval on the DB server, or should I do it on the Web
> server?
>
> Any thoughts would be appreciated.
>
> Thanks
>
> William Balmer