0% found this document useful (0 votes)
63 views

RDBMS Pakages

RDBMS packages include Oracle, MS SQL Server, MySQL, IBM DB2, and others. They store data in tables that can be related through common fields. The main differences between MySQL, Oracle, and MS SQL Server are their companies (open source vs Oracle Corporation vs Microsoft), features, strengths/weaknesses, and application domains.

Uploaded by

Dikshita Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
63 views

RDBMS Pakages

RDBMS packages include Oracle, MS SQL Server, MySQL, IBM DB2, and others. They store data in tables that can be related through common fields. The main differences between MySQL, Oracle, and MS SQL Server are their companies (open source vs Oracle Corporation vs Microsoft), features, strengths/weaknesses, and application domains.

Uploaded by

Dikshita Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

RDBMS Packages

A Relational database management system (RDBMS) is a database management system (DBMS)


that is based on the relational model as introduced by E. F. Codd. Thus RDBMS store the data into collection
of tables, which might be related by common fields.

Various RDBMS packages available are:

 Oracle
 MS SQL Server

 Microsoft Access.

 MySQL (Open Source)

 IBM DB2

 Openbase

 SAP Sybase IQ
Difference between MYSQL, ORACLE and MS SQL SERVER.

Features&
My SQL Oracle MS SQL Server
Functionality
Company Open Source Oracle Corporation Microsoft Inc
Latest Versions version 5.6.12
Version 12c Sql server 2012

Features  High Performance  Concurrency  High Performance.


 High Availability  Locking Mechanisms  High Availability.
 Robust Transactional  Portability  Database mirroring.
support  Self managing database  Database snapshots.
 web and data  SQL*Plus  CLR integration.
warehouse strength  Scheduler  Service Broker.
 management ease  Resource Manager  DDL triggers.
 open source freedom  Data Warehousing  Ranking functions.
 low cost  Materialized views  Row version-based
 Bitmap indexes isolation levels.
 Table compression  XML integration.
 Parallel Execution
 Analytic SQL
 Data mining
 PartitionC
Strengths Price/Performance Great Capable of running large OLTP
performance when and VLDBs. High performance
applications leverage High availability
architecture. Database mirroring
Database Snapshot
Administration Can be trivial to get it setup Requires lots of in-depth Requires lots of in-depth
and running. Large and knowledge and skill to manage knowledge and skill to manage
advanced configurations can large environments. Can get large environments. Can get
get complex. extremely complex but also extremely complex but also
very powerful. very powerful.

Application 1) Web (MySQL excels) 1) Medium/Large OLTP 1) Medium/Large OLTP


Domains 2) Data Warehouse 2) Enterprise applications. 2) Enterprise applications
(most popular) 3) Small/medium OLTP Oracle excels in large 3) Data Warehouse
environments business applications
(EBS, Siebel, PeopleSoft,
JD Edwards, Retek,)
3) Medium/Large data
warehouse
Development 1) PHP 1) Java 1) .NET
Environments
(most common) 2) Java 3) AJEX

3) Ruby on Rails 4) Ruby on Rails

4) .NET 5) PHP
5) Perl
Database Server Database Instance stores Database instance has MS SQL SERVER background
(Instance) global memory in mysql numerous background processes are
background process. processes dependent on
configuration. System Global LAZY WRITER
User sessions are managed EAGER WRITER
Area is shared memory for CHECKPOINT
through threads. SMON, PMON, DBWR, LGWR,
ARCH, RECO, etc. LOG WRITER
BACKUP LOG
Sessions are managed through
server processes.
Database Server Made up of database Uses tablespaces for system
(Physical schemas. metadata, user data and SQL Server data is stored in data files
that, by default, have an .MDF
Storage) indexes. Common tablespaces extension. The log (.LDF) files are
Each storage engine stores include: sequential files used by SQL Server to
information differently. log transactions executed against the
1) SYSTEM SQL Server instance (more on
Common storage engines: 2) SYSAUX instances in a moment).
3) USER DATA
MYISAM – stores data in 4) USER INDEXES
.FRM, .MYD and .MYI files. 5) TEMPORARY
6) UNDO
InnoDB – stores data in a
7) REDO and archive log
common tablespace or
files are used for point in
individual tablespaces per
time recovery.
table.

Binary logs are used for


point-in-time recovery
Partitioning Free, basic features lots of options lots of options
Replication Free, relatively easy to setup Lots of features and options.
and manage. Basic features Much higher complexity with a
but works great. Great lot of features. Allows a lot of
horizontal scalability. data filtering and
manipulation.
Transactions InnoDB and upcoming Falcon Regular and Index only tables
and Maria storage engines support transactions.
Backup/Recovery No online backup built-in. Recovery Manager (RMAN) online backup built-in
supports hot backups and runs
Replication as a separate central OS Snapshots
repository for multiple Oracle
OS Snapshots database servers.
InnoDB Hot Backup
Export/Import Easy, very basic. More features. More features.
Data Dictionary Information_schema and Data dictionary offers lots of
(catalog) mysql database schemas offer detailed information for It offers detailed information
basic metadata. tuning. Oracle starting to for tuning.
charge for use of new metadata
structures.
Stored Procedures Very basic features, runs Advanced features, runs
interpreted in session interpreted or compiled. Lots
threads. Limited scalability. of built in packages add
significant functionality.
Extremely scalable.

Commercial issues
I. Prices Free of Cost Expensive Expensive
II. Technical support No Support It Provide Support 24x7 It Provide Support 24x7
Reliability & It has Average Recovery Very good in recovery Very good in recovery
Recovery
Distributed databases
I. Access to multiple Poor Good
databases Very good
II. Heterogeneous Poor Good
systems support Good

Portability and scalability

I. Portability Good
Very good Good
II. scalability Good
Very good Good

You might also like