Showing entries 26183 to 26192 of 44105
« 10 Newer Entries | 10 Older Entries »
Find Query Per certain Seconds

Do you need to find qps for peak hours not avg qps through mysql life.

The MySQL 5.1 offers new GLOBAL_STATUS information schema tables. These can be used to report certain performance metrics, such as the number of queries processed per certain seconds, NOT overall avg queries per second, Its good to know how much qps in peak hours.

http://forge.mysql.com/tools/tool.php?id=217

WebStack 1.5 - Your (L)AMP Stack

Sun's LAMP support is assembled from two pieces: the L is from our Linux/GNU Support (see SunSolve entry), while the AMP comes from the GlassFish WebStack, which, in its latest incarnation includes Apache HTTP Server, lighttpd, memcached, MySQL, PHP, Python, Ruby, Squid, Tomcat, GlassFish (v2.1) and Hudson (features).

The inclusion of Hudson is a bit of an opportunistic move (more on that in a bit), the rest comprises a well tested, integrated, …

[Read more]
Evil replication management

When one wants to script automated replication chain building, certain things are quite annoying, like immutable replication configuration variables. For example, at certain moments log_slave_updates is more than needed, and thats what the server says:

mysql> show variables like 'log_slave_updates';
+-------------------+-------+
| Variable_name     | Value |
+-------------------+-------+
| log_slave_updates | OFF   |
+-------------------+-------+
1 row in set (0.00 sec)

mysql> set global log_slave_updates=1;
ERROR 1238 (HY000): Variable 'log_slave_updates' is a read only variable

Of course, there are few options, roll in-house fork (heheeeee!), restart your server, and keep warming up your tens of gigabytes of cache arenas, or wait for MySQL to ship a feature change in next major release. Then there are evil tactics:

mysql> system gdb -p $(pidof mysqld)
                       -ex "set opt_log_slave_updates=1" -batch …
[Read more]
Decommissioning old servers, saving money…

Of course it’s not quite that simple. I’ve just decomissioned an old Red Hat 7.1 box (hosted dedicated server) that had been in service since 2002, so about 7 years. Specs? Celeron 1.3GHz, 512M, 60GB HD. Not too bad in the RAM and disk realm. It did a good job but goodness am I glad to be rid of it!

Not having that box online is safer for the planet, although it (perhaps amazingly considering the age of some of the externally facing software components) has never been compromised – I consider that mostly luck, by the way, I’m not naive about that. But it’s not easy to move off old servers, it’s generally (and also has been in this case) a lot of work.

Of course hosting has moved on since 2002, places like Linode offer more for less money/month. Of course they virtualise (Xen based in this case) and that’s not been my favourite (particularly for DB servers but depending …

[Read more]
Automated MySQL data comparison and synchronization: how it works

In dbForge Studio for MySQL you can find Data Compare, a tool which allows you to compare and analyze tables data in databases, for example, to check that data in the synchronized databases are identical. Besides, it  allows synchronizing the data differences to get identical databases. The following picture illustrates comparison and synchronization of two MySQL databases.

Data Comparison Workflow

To compare data, the program automatically selects columns with a primary or unique key as comparison keys. Of course, you can set comparison keys manually, however, in such cases key repetition may occur which can cause conflicted records after comparison. Such records are not compared.

[Read more]
Workbench 5.2 Alpha

In case you have not already noticed, Workbench 5.2 alpha / preview release of MySQL's premier development and design tool, has been announced.

For an independent preview, you can also see here

Workbench 5.2 Alpha

In case you have not already noticed, Workbench 5.2 alpha / preview release of MySQL's premier development and design tool, has been announced.

For an independent preview, you can also see here

The NoSQL community needs to engage the DBA’s

The NoSQL movement has been gaining some steam lately, with discussion forums and mailing lists popping up all around the web.  Despite having a career that has been centered on the RDBMS, I have made no secret that I think we have gone too far down with our RDBMS for everything mindset.  I think we need to add a few more tools back into our data toolbox. 

Today, 99.5% of new data centric developments started will use a RDBMS by default.  Maybe .5 of a % will consider using something as obtuse as a NoSQL platform.  By experience I know the majority of people discussing NoSQL platforms today are web developers.  In fact there is almost a sense of trying to trying to keep this under the radar of DBAs.  If we don’t talk to the DBAs about this stuff then they won’t bother us with all that …

[Read more]
OpenSQL Camp comes to Portland, OR! November 14-15, 2009

Stealing the announcement news from Selena’s blog post:

I’m happy to announce that Portland, OR will be host to the next OpenSQL Camp, Portland. We’ll be holding it November 14-15, 2009.

Patterned after the first Open SQL camp held in Charlottesville, Virginia, USA, in November 2008, we’re inviting any and all database practitioners (even the non-SQL, non-relational ones!) to join us for two days of deep database geeking.

To quote:

“Attendees of this conference are mostly open source developers and end users/open source enthusiasts. The goal of this event is to spread the word about the vibrant communities and large ecosystems around Open Source Databases and to educate the attendees about what alternatives exist to …

[Read more]
Autoincrement Semantics

In this post I’m going to talk about how TokuDB’s implementation of auto increment works, and contrast it to the behavior of MyISAM and InnoDB. We feel that the TokuDB behavior is easier to understand, more standard-compliant and offers higher performance (especially when implemented with Fractal Tree indexes).

In TokuDB, each table can have an auto-increment column. That column can be used as any part of a key, but it doesn’t have to be part of any key. The value produced by auto incrementing is always greater than the previous maximum value for that column. There are some cases where auto-incremented values are skipped, such as when a transaction aborts, which “uses up” auto-incremented values.

This behavior is close to that required for SQL:2003 (see SQL:2003 at wikipedia), which specifies that each table provides one unnamed sequence which behaves essentially in the way we implemented auto increment. The …

[Read more]
Showing entries 26183 to 26192 of 44105
« 10 Newer Entries | 10 Older Entries »