Robert Scheer said:
Hi.
I was developing a web application using SQL Server. Suddenly, my
customer decided to use Oracle 8.1.6 as the database. The DBA is
deciding if the application will access a new database or a scheme and
I wiil have to migrate my SqlHelper class to an OracleHelper class.
What is the purpose of an Oracle scheme? Can I access it using the
.NET Oledb Provider?
Thanks,
Robert Scheer
An Oracle Schema is a logical collection of all of the database objects
owned by a security principal. The security principay may or may not be a
user account - the account may not support a connection to the database, but
may have granted access to the objects (tables, views, packaged, functions,
sequences, etc) to other security principals or schemas.
The DBA may be thinking of creating a new database for you on an new
machine, or a new instance of a database on an existing machine with Oracle
already installed, or may be thinking of creating a schema for your
application on an existing instance. Which of these the DBA does is
absolutely of no concern to you or the application. The DBA will create the
security principal (i.e. user account), then allocate that to that account a
default tablespace, a temp tablespace, and maby a few roles and permissions
so the account can support logon, object creation, DML and SQL Selects, and
so on.
Your first worry should be to decide on the .NET provider - Oracle from
MSFT, Oracle from Oracle, or OLEDB/ODBC bridge. If you had lots of SQL
Server stored procedures, then you need to get them rewritten. If you used
named notation for .Net bind variables, change to positional notation.
that's just a few thoughts - I sure many will provide more.
regards
roy fine