Between
Oracle and SQL Server, they are having more and more similar features,
some of them are language feature such as sub-query factory and analytic
functions, some of them are technique trends such as in-memory and
column store.
And some times, they learn from each other.
In SQL Server 2008, it introduced isolation level
read-commited-snapshot, which is borrowing row versioning concept that
is well known in Oracle. But it has bottleneck due to relaying on
tempdb. In version 2014, its in-memory OLTP, the implementation is not
only more similar to Oracle's, but also introduced some good and
revolutionary.
When I eventually understand what is container
and pluggable database in Oracle, which is hoorayed as revolutionary
architecture change in Oracle 12c, I kind of think, well, it's only
revolutionary to Oracle world, it's there in SQL Server or Sybase from
when they were born.
For the people who want to have a glace of
similarity, here are few of them, same list number is the equivalent
features in each database.
Oracle 12c
1. root container
2. seed db
3. pluggable database
4. local user
5. common user
6. plug the pluggable database
7. unplug the pluggable database
8. isolated name space in each pluggable database
9. individual pdb backup and restore
...
SQL Server
1.master
2.model
3..user database
4 local database user
5. login user(kind of)
6. attach user database. even better here because it does not require extra meta data file
7. detach user database
8. same here
9. same and even better in SQL server because they share nothing
No comments:
Post a Comment