Part II in our series on MySQL picks up where we left off from talking about some of the challenges, and potential issues and problems that come up with MySQL replication after you have it setup and running for some time. DBJ: Fixing MySQL Replication
In this piece we talk about some of the ways to verify your setup, and make sure your slave does not drift out of sync with the master, and to alert you if it does.
In this month’s Database Journal article we write about Replication Pitfalls with MySQL.
Replication is fairly straightforward to setup, however your slave databases can get out of sync, or throw errors. We investigate some of the reasons why, and help you identify those before they come back to bite you!
If you’re already building LAMP applications (linux/apache/mysql/php), and you’re looking to port them to Oracle, or you’re new to this technology stack, and you want to use Oracle as your database, this article is for you. We cover the basics of gettings started, and where to look for more information.
In our latest database journal piece, we cover some useful Oracle-supplied pl/sql stored procedures to help you instrument and debug your code, dump metadata descriptions of your database objects (a la MySQL dump –no-rows) and much more.
Take a look at DBA Insider - Useful PL/SQL Packages.
Our two part article on migrating a MySQL database to Oracle features in Database Journal in January and February of this year. Take a look and please post your comments!
In Part II in this series, I talk about how these three databases compare in some particularly crucial areas.
For instance how do the optimizers of these different database engines behave, and why does that matter? What type of indexes are available, particularly with respect to typical applications. I then move on to datatypes available and which are missing. You’ll find some surprises here.
Lastly the holy grail of any modern relational database, I discuss transactional support. Relevant concepts include ACID compliance, read-only versus insert and update activity, and so on.
If you’re interested in how these three databases measure up in terms of feature sets, take a look at part one in a two part series I wrote over at Database Journal.
I discuss stored procedures, views, materialized views or snapshots, triggers, and security. Stored procedures and functions are supported on all three databases, as are views and triggers. Although MySQL and Postgres aren’t there in terms of default snapshot support, there are ways to get that functionality in a somewhat roundabout way.
Security is always a tricky question, as all the bugs out there aren’t always publicized. It’s sort of a cat and mouse game. All three databases support user based authentication to login to the database, and various privilege levels to control access to objects and data. Oracle also supports FGA or fine grained access control for …
[Read more]