Description: Oracle 10g Tablespaces

Description: Oracle 10g Tablespaces
Oracle Database Architecture
An Oracle database is a collection of data treated as a unit. The purpose of a database is to store and
retrieve related information. A database server is the key to solving the problems of information
management. In general, a server reliably manages a large amount of data in a multiuser environment
so that many users can concurrently access the same data. All this is accomplished while delivering high
performance. A database server also prevents unauthorized access and provides efficient solutions for
failure recovery.
Oracle Database is the first database designed for enterprise grid computing, the most flexible and cost
effective way to manage information and applications. Enterprise grid computing creates large pools of
industry-standard, modular storage and servers. With this architecture, each new system can be rapidly
provisioned from the pool of components. There is no need for peak workloads, because capacity can be
easily added or reallocated from the resource pools as needed.
The database has logical structures and physical structures. Because the physical and logical structures
are separate, the physical storage of data can be managed without affecting the access to logical storage
structures.
Overview of Oracle Grid Architecture
Grid computing is a new IT architecture that produces more resilient and lower cost enterprise
information systems. With grid computing, groups of independent, modular hardware and software
components can be connected and rejoined on demand to meet the changing needs of businesses.
The grid style of computing aims to solve some common problems with enterprise IT: the problem of
application silos that lead to under utilized, dedicated hardware resources, the problem of monolithic,
unwieldy systems that are expensive to maintain and difficult to change, and the problem of fragmented
and disintegrated information that cannot be fully exploited by the enterprise as a whole.
Benefits of Grid Computing Compared to other models of computing, IT systems designed and
implemented in the grid style deliver higher quality of service, lower cost, and greater flexibility. Higher
quality of service results from having no single point of failure, a robust security infrastructure, and
centralized, policy-driven management. Lower costs derive from increasing the utilization of resources
and dramatically reducing management and maintenance costs. Rather than dedicating a stack of
software and hardware to a specific task, all resources are pooled and allocated on demand, thus
eliminating under utilized capacity and redundant capabilities. Grid computing also enables the use of
smaller individual hardware components, thus reducing the cost of each individual component and
providing more flexibility to devote resources in accordance with changing needs.
Title: End-to-End Hash Logon
Description: This code is is a sample application demonstrating an End-to-End has logon process where
the user's password is hashed using MD5 and compared to the stored MD5 hash of the password in the
SQL database.
The Hash is protected while travelling over the network by using RSA Public Key crypto between the
client and the SQL Server (while changing the password) and between the DLL and the SQL database
(while verifying the password).
This includes a Transact SQL TSQL port of the RSA code in
Summary:
| clear screen
-------------------------
Installation notes
------------------
1) Create a logon account on the network for the DLL to authenticate
with SQL server. The password should be secure and shouldn't

change.
2) Install the Database Objects into your favourite Database.
a) Execute the RSASetup.SQL script first.
b) Execute the SQLSetup.SQL script.
3) Grant the account created in step 1 access to the Database.
4) To use the precompiled DLL, install it in Component Services.
a) Create a new Application.
b) Set the Application Identity to the account created in step 1.
c) Add the Component DLL (make sure the DLL is installed outside of the IIS wwwroot directory
structure)
This DLL was made compatible with COM+ but does not use transactions. It may be used without
Component Services, but this is not recommended.
5) Create an ODBC System DSN which points to the Database where the tables and Stored Procedures
were installed.
a) Call the DSN "HashLogonDemo"
b) Make sure Windows Authentication is used.
c) Make the DSN change the default DB to the DB where
where the DB objects were installed in step 2.
6) Install the ASP, INC and JS files into the same web folder on the IIS server.
7) To test, read the passwords in the SQLSetup.SQL file which are commented in plain text.
Open the location where the IIS files are installed by browsing to
"http://servername/directory/MyHome.asp"
or to "http://servername/directory/TokenLogon.asp" ---------------------

Description: Oracle 10g Tablespaces

Uploaded by

Copyright:

Available Formats

Description: Oracle 10g Tablespaces

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Description: Oracle 10g Tablespaces

Uploaded by

Copyright:

Available Formats

Description: Oracle 10g Tablespaces

Oracle Database Architecture

Overview of Oracle Grid Architecture

This includes a Transact SQL TSQL port of the RSA code in

1) Create a logon account on the network for the DLL to authenticate

with SQL server. The password should be secure and shouldn't

2) Install the Database Objects into your favourite Database.

a) Execute the RSASetup.SQL script first.

b) Execute the SQLSetup.SQL script.

3) Grant the account created in step 1 access to the Database.

4) To use the precompiled DLL, install it in Component Services.

a) Create a new Application.

b) Set the Application Identity to the account created in step 1.

a) Call the DSN "HashLogonDemo"

b) Make sure Windows Authentication is used.

c) Make the DSN change the default DB to the DB where

where the DB objects were installed in step 2.

You might also like