Help me put Oracle terminology into SQL Server terminology [closed]

问题

My company is now supporting Oracle for the first time, and most of my colleagues are SQL Server developers who haven't really worked with Oracle. I'm a little bit familiar with Oracle, but far from a genius on the subject. Unfortunately, that is enough to mean that I know more about Oracle than most of my co-workers, so I find myself constantly struggling to explain concepts I'm still learning myself in terms that people who aren't familiar with Oracle at all can understand.

The biggest problem that I run into is in knowing how SQL Server terminology translates into Oracle terminology. I understand that there's not a direct 1:1 mapping of terms, but it would be helpful to be able to know how to put Oracle concepts into SQL Server terminology and vice-versa when talking to my SQL Server-centric co-workers. Can someone tell me the best way to put these SQL Server terms into Oracle terminology?

database
instance
schema

And conversely, how to explain these Oracle concepts in SQL Server terms?

tablespace
database
listener
service name
SID

回答1:

Oracle/SQLServer:

tablespace = doesn't exist
database = doesn't exist
instance = instance
schema = database
listener = doesn't exist
service name = database name
SID = database name

回答2:

I don't know anything from sqlserver so what I can do is to try to explain what * tablespace * database * listener * service name * SID are. A database is the collection of files that all together make the database. This can be datafiles but also parameter and password files. That database is serviced by one or more instance[s]. An instance is the interface between client processes and the database. In a parallel server configuration - RAC - there can be multiple instances active on the same database. A service is a connection handle to a database. A service van be serviced by multiple instances and every instance can serve multiple services. Services are used to make the combination of applications in one database possible. Every application connects to it's own service, ending up in an instance of the database. A listener is the process that listens for clients that want to connect to an instance or service. the listeners hands over the connection request to an instance background process that performs the database interactions for the client. A SID or ORACLE_SID is just the name of an instance.

The Concepts manual will be of great help. I hope this helps.

Ronald