Re: ADVANCED-DOTNET Digest - 28 Jan 2009 to 29 Jan 2009 (#2009-17)

lol

-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[email protected]] On Behalf Of ADVANCED-DOTNET
automatic digest system
Sent: Friday, January 30, 2009 12:01 AM
To: [email protected]
Subject: ADVANCED-DOTNET Digest - 28 Jan 2009 to 29 Jan 2009 (#2009-17)

There is 1 message totalling 92 lines in this issue.

Topics of the day:

  1. Current approach to fast n tier oracle design

===================================
View archives and manage your subscription(s) at
http://peach.ease.lsoft.com/archives

----------------------------------------------------------------------

Date:    Thu, 29 Jan 2009 17:03:57 -0800
From:    Fletcher's Discussion Account <[email protected]>
Subject: Current approach to fast n tier oracle design

Hi all,

 

I have been asked to develop a spec to do something that is fairly simple.
I am just doing a quick sanity check before I start.

 

I have to replace an application that gets data from an oracle server via an
ODBC connection.  It's a read only system that people like because it's much
faster than using the actual application used to manage the data.  I program
in a number of languages and am just getting back into .NET (2008) so I am
not up to date on the best approach to use these days.

 

My plan is to create a Web Service (probably the new WCF) that can pass
queries to the SQL server.  

 

Questions:

 

1)      Is WCF the best choice given that I need speed and support for a
variety of clients (browsers and applications)

2)      What is the best (fastest) way for the web service/WCF to talk to
the oracle server (OLE DB, ODBC, Oracle's drivers, etc.)? 

3)      Which of the .NET approaches (LINQ, TableAdaptor, CreateConnection,
etc.) will get the result the fastest from Oracle to the WS?

4)      What is the best way to package the data to send back to the final
client (either a browser or application)?  My guess is that I can probably
just pass the result set from the server on to the client

5)      Is there anything I should do to the IIS server to make sure it is
supporting the applications the most efficiently?

6)      With WCF, if I define an instance of the web service, does it retain
its state until I release the instance?

 

If the difference in speed is fairly negligible, then ease of implementation
is the 2nd choice.

 

I am looking at a web service because it can serve data to any client
(browser or application).  We also have a problem with the IT people
changing the information that references the Oracle server, so I would
rather have one place to update instead of every user (which is what we have
to do today with ODBC based clients.)

 

The result sets are usually fairly small (100 rows or less) and may contain
parent-child data sets.

 

Finally, are there any gotchas in this approach that might trip me up?

 

Thanks,

 

Fletcher

 

 


===================================
View archives and manage your subscription(s) at
http://peach.ease.lsoft.com/archives

------------------------------

End of ADVANCED-DOTNET Digest - 28 Jan 2009 to 29 Jan 2009 (#2009-17)
*********************************************************************

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives