When I was looking at Yukon (pre ss2005) - the Stored Proc's under .NET had the ability to open up the db for anyone to do anything. There were 3 levels of security. I would thoroughly test it before opening your data base up. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] Sent: Wednesday, March 15, 2006 11:41 AM To: Oracle-L Subject: RE: .NET Stored Procedures in Oracle database Fyi, this is related to the fact that SQL Server 2005 now offers CLR. CLR is the Common Runtime Language "engine" that let you have managed code running, built on .NET languages, within the SQL Server engine. Since MS now provides it, Oracle also has to. M$ has been touting this features, so this is Oracle's reply. John -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Christian Antognini Sent: Wednesday, March 15, 2006 9:58 AM To: juancarlosreyesp@xxxxxxxxx Cc: Oracle-L Subject: RE: .NET Stored Procedures in Oracle database Juan >Had you read this? >Is this better than using java? >Any experience? Notice that: - The stored procedures don't run *in* the database. - It's a simple external call... as we used to do with C shared libraries. - This is a Windows only feature. Basically it makes only sense if you already have some kind of library that you *absolutely* want to call from the database. The same thing applies to Java in the database. Therefore, IMHO, one is not better than the other. HTH Chris -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l