FrenchTech SAAS

The result of slavish adherence to 3NF in database design can lead to over-engineering; the evidence of which include inflexible design schemas and cumbersome data retrieval.

Rob Gravelle demonstrates how stored procedures can be used in conjunction with triggers to enhance their effectiveness. In doing so, he examines some of the limitations of triggers as implemented in MySQL as well as ways to circumvent them.

If your MySQL database interfaces with applications or is used to generate reports then chances are good that it contains some massive stored procedures.

Tokutek has developed a new kind of data structure called a Fractal Tree that is purported to achieve insertion rates of five to twenty times faster in large databases, as in 100 million rows and above.

A loop is a programming construct that executes a block of code repeatedly based on a condition. Cursors, on the other hand, are utilized to process each row returned by a SELECT statement.

While useful in some contexts, database triggers are not the best option in every situation. There are times when a stored procedure is the preferred solution. The trick is of course, when to choose one over the other.

With respect to data types, MySQL and MS SQL Server have some important differences. Chances are that you’ll have to do some mapping to get the correct data when migrating from one to the other.

Viewing the process list is a key step in debugging many
common server problems, including bottlenecks, poor performance, deadlocks,
connection issues, and many others.

10+ Great Open Source Tiny Database Engines Entirely Written In Java.