VU World || Assignments, Quizzes, GDBs, Past Papers, Reports etc....

A short definition of an RDBMS is: a DBMS in which data is stored in tables and the relationships among the data are also stored in tables. The data can be accessed or reassembled in many different ways without having to change the table forms.
according to my opinion based on security ORACLE is far better than others..
Oracle is more stable, more robust, and more secure
Oracle is premium soft, it is best for any system setup relational database, many supporting tool , but no free.
Oracle is more geared towards and thus may perform better with very large deployments, it is true, but the thing that actually makes a difference is having optimized queries and sensible indices.
It really depends on what you want to use it for. Oracle is better for larger sites (it's better at handling a lot of simultaneous requests at once).

MYSQL I'd say is easier to use and there are a lot more resources out there for it than Oracle.

IDEA Solution:-

Microsoft SQL Server has a stronger security posture than the Oracle RDBMS.

DISADVANTAGE PRESENT IN MYSQL:

MYSQL standard has diverted on the standards of implementation of Null and default values. Arithmetic operations are susceptible to integer over flow. Mode of operation of SQL is set to unusual tolerant state which developers hate.
MySQL does not support a very large database size as efficiently
MySQL does not support ROLE, COMMIT, and Stored procedures in versions less than 5.0
Transactions are not handled very efficiently.

---

Advantages of MySQL over Oracle :

MySQL is characterised as a fast, robust database with a good feature set, but one which lacks all the extras of something like Oracle ... so if you're writing code that's designed to be portable it's a pretty good choice. Admin / security are effective but the setup of these and othe features isn't over-complicated. All in all, a pretty good choice for many "middle of the road" requirements.

MySQL is characterised as a free, fast, reliable open source relational database. It does lack some sophistication and facilities, but it has an active development team and, as it goes from release to release, more capabilities are added. At certain times there will be a trade-off between speed and capabilities, and the MySQL team intend to keep their database engine fast and reliable.


Advantages of Oracle over MySQL :

Oracle is much versatile than MySQL. Oracle can run and handle more transactions than MysQL. Oracle would be better if you are going to have lots of db usage.

I've used MySQL. Only for a forum. Still, MySQL takes up resources with PHP that affected the server load. Oracle on the other hand is better with memory leaks and handles multiple threads. You can do SQL Transactions, stored procedures, DTS in Oracle that you can not do in MySQL earlier versions.

Oracle is expensive, although they came out with Oracle Free Edition to attract MySQL users.

MySQL users enjoy this database because it is available on virtually all hosting companies. Oracle are only limited to large corporations due to licencing costs and not all hosting companies have Oracle (they might have SQL Server, but not Oracle).

You can make billions of data with MySQL, but it will be slow on the server. In addition, backing up the MySQL database takes forever, versus Oracle's tools which makes database backup a cinch.

If you are going to use MySQL, then add lots of memory. In addition, I recommend that you seperate the Website from the database. In other words, have emails and website on a seperate server and only have a dedicated MySQL server specific to mysql/db only.

MySQL is Free, It's everwhere, that's the whole concept!!!

---

MYSQL and SQL me se to SQL he best hai esko read kro. ab hme SQL and ORACLE ka comparison krna chaheay.

To give a better idea of the differences in MySQL and SQL Server, MySQL is geared more toward selecting data so is can be displayed, updated and saved again. MySQL is weaker in the areas of inserting and deleting data. MySQL is an excellent choice, for other reasons that we will discuss later on, for data storage and referencing data. MySQL is not the best choice however, for creating, inserting and deleting data from tables on the fly.
For an Internet application, MySQL would be a good choice for tracking clients and creating dynamically populated pages with information from the database. For an application of moderate to large scale that is used for commerce of any kind, SQL Server is by far the better choice with more options and functionality to add, manipulate, update and delete data.
Following are some specific technical differences in MySQL and SQL Server when it comes down to the ANSI SQL standard:
MySQL does not support Triggers, SQL Server does.
MySQL does not support User Defined Functions, SQL Server does.
MySQL does not have Cursor Support, SQL Server does.
MySQL does not support Stored Procedures, SQL Server does.
MySQL does not have FULL JOIN capabilities, SQL Server does.
MySQL has limited Import/Export capabilities, SQL Server has full support for Import/Export.
MySQL has limited Transaction Support while SQL Server offers full Transaction Support.
So, it becomes clear that SQL Server is an obvious choice for the company or individual that needs to have FULL control over their data to manipulate and change it as they need.
The following table shows a more complete comparison of the differences between MySQL and SQL Server:
Feature
MySQL 4.1
SQL Server 2000
Notes
SQL VIEW support

SQL VIEWS let administrators abstract database designs away from developers.
Triggers

Lack of triggers makes MySQL developers add extra logic to their front end and middle tier when the logic should go into the database.
Stored Procedures

Stored procedures are mechanisms for abstraction and security
User Defined Functions

User Defined Functions (UDFs) allow encapsulation of complex code into simple callable interfaces.
CURSOR Support

Lack of CURSOR support in MySQL increases network traffic and lowers app response time.
SQL SELECT

MySQL supports using a regular expression as a filter clause in a query.
XML Support

XML is a standards-based format for data. MySQL has no native support for XML.
FULL JOIN

MySQL does not support FULL JOIN
Referential Integrity

MySQL 4.0 supports referential integrity (RI) so long as the InnoDB table type is chosen.
Transaction Support

MySQL´s default installation does not support transactions. Transaction support requires InnoDB.
Full Text Support

Import/Export Support

Replication Support

Auto Tuning

Database Management Tools

Query Analysis Tools

Job Scheduling

Profiling

Online backup support

Clustering Support

Log Shipping

Support for Storage Area Networks (SANs)

Hot Backups / Incremental backups

Basic Security

Security Certifications

Security Tools

Security through stored procedures & views

OLAP Services

Data Mining

Data Reporting

Security Support
Another major concern to business today is security. While data management can seem to be a mundane process at times, securing critical data from "the outside world" is an ever increasing and trying task.
While is good to know that your database management system (MySQL or SQL Server) utilize security features it is very important to know that the application has been verified by a third party. SQL Server has been certified as C2 compliant, which ensures that the database has adequate security support for government applications.
Along with C2 certification, Microsoft Baseline Security Analyzer helps administrators ensure that their SQL Server installations are up to date with the most current patches and security features. MySQL has no equivalent tool to protect and ensure the same confidence in their platform.
While both MySQL and SQL Server support security measures within in their platforms, MySQL supports security via the SQL GRANT command. The MySQL GRANT command is limited to granting security at the table level. This means that if any portion of data in the table needs to be secure from any particular user, then the entire table has to be secured from that user. SQL Server supports security at the column level, meaning that any portion of data in a table can be secured from any particular user while allowing that same user to see other portions of the table data.
SQL Server also makes their database more secure by abstracting its data behind a layer of stored procedures. This ensures that developers never see how the actual data is represented. My SQL, as noted above, does not support stored procedures.
Data Protection
Another security aspect is the protection from loss of data due to power failure. Database administrators in large environments employ the concept of "warm standby servers". This is an additional server containing duplicate data that, by normal use, is not accessed until an event such as a power failure of the main server. Standby servers are kept in a ready state using a concept known as log shipping. Log shipping takes a regularly scheduled backup (sometimes at intervals of less than 10 seconds) of a database and stores that data on the duplicate standby server´s hardware.
MySQL lacks the capability to perform such a backup transaction in an online, or "live" environment. This feature is standard to SQL Server and includes tools to help the database administrator manage the details of the log shipping.
Support and Service
When deciding on how you want to manage your data, you must also consider what kind of support you can expect to receive from the manufacturer of your data management application. After all, if you can´t figure out how to make it work for you, you can´t make any use of your data.
MySQL and SQL Server both offer support plans that are available from their respective vendors. Both applications offer some free support as well as some paid support options and plans.
MySQL claims to employ about 100 people worldwide, which makes up the entire company consisting of product development, support staff, sales staff, distribution, and clerical workers. With such a small staff dispersed over a wide area of expertises, this fact may worry some database administrators.
SQL Server, from Microsoft, has a significantly large support program and large staff backing the program.
Pricing!
Now, let´s move on to the biggest issue of them all. Pricing! Let´s start with MySQL, how does FREE sound? Well, while MySQL is an open source database management tool, it does have its retractions on that $0.00 price! MySQL can be used, for free, for any purpose whether its used to manage a large companies data or to spice up a hobbyist´s web site.
SQL Server on the other hand, could take a small independent company´s budget and eat it for lunch! However, the many outstanding features that are far and away above MySQL offset the price paid for SQL Server drastically.
Conclusion
Now that we have taken a good look at the defining differences between MySQL and SQL Server, its plain to see that the final decision will come down to your needs. How flexible do you need your data to be? How secure must your data be? Do you need support in utilizing your data management tools? These are all questions that you will have to answer for yourself. And in answering them, you will know which data management tool will be best suited for your personal, business or corporate needs.
From a database developer´s standpoint, the choice is clear. SQL Server is the most sensible choice because of its rich features in manipulating, securing and managing data. Also, from a developer´s stand point, MySQL´s lack of support for the basic database features mean that development of an application to interface with the database will be both more costly and take longer to finalize. Too much code must be written in the user interface to manipulate the data first, before sending that data to the database. All this extra code costs time and money to develop and maintain.