Speed matters. That’s why you’re willing to pay a dollar more for milk at the convenience store — it’s quicker than waiting in line at the supermarket. And that’s why you will lose business if your database slows down the customer experience.

This is especially true of e-commerce websites. Forty percent of people won’t wait more than three seconds for a mobile shopping site to load. Amazon estimates it would lose $1.6 billion a year if its web pages took one second longer to load. If consumers won’t wait one second for Amazon, they won’t wait for your database to come back online.

And that’s just the direct bottom-line impact. Poor database performance has other negative effects, but you can follow steps to avoid these problems.

Read the full article here.

I've gotten a lot of positive feedback from my post on upgrading temporal columns from MySQL 5.5 to MySQL 5.6 format, both in the blog comments and directly from people who have used my query to identify which columns are candidates to be upgraded to the new format. Based on the feedback and some changes in more recent MySQL releases, I think it's worth doing a follow-up post.

Partioned tables

It was pointed out to me that the SQL query I used in my previous post does not work for partitioned tables. The reason is the join between information_schema.tables and information_schema.innodb_sys_tables in my query. For non-partitioned tables the value in information_schema.innodb_sys_tables.name will be <table_schema>/<table_name>, …

Check Out Our Latest Technical Resources for MySQL, MariaDB, Postgres and MongoDB

This blog is packed with all the latest resources and tools we’ve recently published! Please do check it out and let us know if you have any comments or feedback.

Live Technical Webinar

• What: Become a MySQL DBA - Which High Availability Solution
• When: Tuesday July 28th
• Who: Krzysztof Książek, Senior Support Engineer, Severalnines
• Where: Register Here

In this webinar, we will look at some of the most widely used HA alternatives in …

make sure you completely removed old openssl and added “allow_vulnerable_openssl” in the “security” subsection of “radiusd.conf”

allow_vulnerable_openssl = ‘CVE-2014-0160′

Check my blog post for fixing this issue:

https://lalitvc.wordpress.com/2014/06/26/freeradius-refusing-to-start-with-libssl-version-openssl-security-advisory-cve-2014-0160/

Hi
I have the following error message when issuing radiusd -X, any experience? Thanks

Debugger not attached
Refusing to start with libssl version OpenSSL 1.0.1e-fips 11 Feb 2013 0x1000105f (1.0.1e release) (in range 1.0.1 dev – 1.0.1f release)
Security advisory CVE-2014-0160 (Heartbleed)
For more information see http://heartbleed.com
Once you have verified libssl has been correctly patched, set security.allow_vulnerable_openssl = ‘CVE-2014-0160′

Are you still running yesterday’s database? Technology and workloads have changed, so it might be time to re-examine your trusty standby. But how do you determine whether the benefits of new data storage technology are worth the cost and effort of evaluating and switching?

Perhaps you think your current data retrieval system is “good enough,” but that “just fine” system might be creating huge technical debt that could come back to haunt you. To keep up with the times, you might need to re-evaluate your database. This could result in a leaner, meaner, and more modern back end that can grow with your business and save you money.

Technology changes rapidly, and data storage technologies are no exception. Innovations such as solid-state drives are creating entirely new sets of tradeoffs and advantages. Meanwhile, the sheer amount of data being collected continues to explode. Older solutions simply cannot find good footing in …

Have you ever wondered what could happen if your MySQL database goes down?

Although it’s evident such a crash will cause downtime – and surely some business impact in terms of revenue – can you do something to reduce this impact?

The simple answer is “yes” by doing regular backups (of course) but are you 100% sure that your current backup strategy will really come through when an outage occurs? And how much precious time will pass (and how much revenue will be lost) before you get your business back online?

I usually think of backups as the step after HA fails. Let’s say we’re in M<>M replication and something occurs that kills the db but the HA can’t save the day. Let’s pretend that the UPS fails and those servers are completely out. You can’t failover; you have to restore data. Backups are a key piece of “Business Continuity.” Also factor in the frequent need to restore data that’s been …

This Log buffer edition covers Oracle, SQL Server and MySQL blog posts about new features, tips, tricks and best practices.

Oracle:

• Traditionally, assigning specific processes to a certain set of CPUs has been done by using processor sets (and resource pools). This is quite useful, but it requires the hard partitioning of processors in the system. That means, we can’t restrict process A to run on CPUs 1,2,3 and process B to run on CPUs 3,4,5, because these partitions overlap.
• Parallel_Degree_Limit, Parallel_Max_Degree, Maximum DOP? Confused?
• JDeveloper 12c – …

Introduction

The names of databases and tables within MySQL are known as identifiers. In the simplest case these identifiers are just strings of certain ASCII characters (the basic Latin letters, the digits 0-9, the dollar sign and the underscore). However, if an identifier is placed in quotes, it can contain any character of the full Unicode Basic Multilingual Plane (except U+0000). We say that a character is a special character if it is permitted in a quoted identifier but not in an unquoted identifier.

MySQL Enterprise Backup (MEB) 3.12.1 introduces support for proper handling of table and database names with special characters. In MEB versions prior to 3.12.1 database and table names were represented as ASCII strings and the same string was used on the command line, internally within MEB and in filenames.  This caused MEB to fail some …