Upscene releases Database Workbench 5.1.0
For immediate release: http://www.upscene.com/news/item/20150624 Upscene releases Database Workbench 5.1.0 Upscene Productions is proud to announce a new release of the popular multi-DBMS development tool: “ Database Workbench 5.1 This version is the next big release after version 5 and includes new features, enhancements and fixes. The change log is available here: http://www.upscene.com/go/?go=trackerv=5.1.0id=12 Version 5 added numerous new features and improvements to existing tools and the new, more consistent user interface is better than ever and works fine under Wine on Linux. Version 5.1 includes additional data export functionality, Firebird 3 support, improved Oracle XML and Object-type support, Diagramming enhancements and new printing features as well as improvements in other areas. Database Workbench now comes in multiple editions with different pricing models, there's always a version that suits you! For more information, see What's new in Database Workbench 5? ( http://www.upscene.com/database_workbench/whatsnew ) Database Workbench supports MySQL, MariaDB, Firebird, Oracle, MS SQL Server, SQL Anywhere, NexusDB and InterBase, comes in multiple editions and is licensed based on selectable modules. It includes tools for database design, database maintenance, testing, data transfer, data import export, database migration, database compare and numerous other tools. About Database Workbench Database Workbench is a database developer tool, over 10 years in the making and is being used by thousands of developers across the globe who have come to rely on it every day. From database design, implementation, to testing and debugging, it will aid you in your daily database work. About Upscene Productions Based in The Netherlands, Europe, this small but dedicated company has been providing database developers with useful tools for over 12 years. Slowly expanding the product portfolio and gaining recognition amongst InterBase and Firebird database developers, they now offer tools for a whole range of database systems, including Oracle and Microsoft SQL Server.
Re: server-side logging of query errors?
From: Singer X.J. Wang w...@singerwang.com Subject: Re: server-side logging of query errors? You could log all queries using the audit plugin, 15% hit.. Fair point, though: maybe one of the different audit plugins has the capability to specifically log faulty requests. Have a look through the slides from Percona Live London 2014, there was a talk about auditing. -- Unhappiness is discouraged and will be corrected with kitten pictures.
Re: server-side logging of query errors?
The performance hit of the Percona Audit is 15% for disk logging and for remote syslog we found it is lower. It logs everything including bad queries (eg. select fark from fark from fark fark fark from frak). You should be able to write a JSON parser that extracts what you want based on the log (eg. STATUS, COMMAND, NAME). On Wed, Jun 24, 2015 at 11:05 AM, Johan De Meersman vegiv...@tuxera.be wrote: -- *From: *Singer X.J. Wang w...@singerwang.com *Subject: *Re: server-side logging of query errors? You could log all queries using the audit plugin, 15% hit.. Fair point, though: maybe one of the different audit plugins has the capability to specifically log faulty requests. Have a look through the slides from Percona Live London 2014, there was a talk about auditing. -- Unhappiness is discouraged and will be corrected with kitten pictures.
Re: Refresh slave state
2015-06-22 13:45 GMT+02:00 Ben RUBSON ben.rub...@gmail.com: 2015-06-19 12:08 GMT+02:00 Ben RUBSON ben.rub...@gmail.com: 2015-06-18 22:52 GMT+02:00 shawn l.green shawn.l.gr...@oracle.com: On 6/18/2015 2:10 PM, Ben RUBSON wrote: Hello, In order for the slave to quickly show a communication issue between the master and the slave, I set slave_net_timeout to 10. show slave status then quickly updates, perfect. I would also like the master to quickly show when the slave is no more reachable. However, show processlist and show slave hosts take a very long time to update their status when the slave has gone. Is there any way to have a refresh rate of about 10 seconds, as I did on slave side ? There are two situations to consider 1) The slave is busy re-trying. It will do this a number of times then eventually disconnect itself. If it does disconnect itself, the processlist report will show it as soon as that happens. Yes, I confirm. 2) The connection between the master and slave died (or the slave itself is lost). In this case, the server did not receive any I am going to disconnect message from its client (the slave). So as far as the server is concerned, it is simply sitting in a wait expecting the client to eventually send in a new command packet. That wait is controlled by --wait-timeout. Once an idle client connection hits that limit, the server is programmed to think the idiot on the other end of this call has hung up on me so it simply closes its end of the socket. There are actually two different timers that could be used, --wait-timeout or --interactive-timeout and which one is used to monitor the idle socket depends entirely on if the client did or did not set the 'interactive flag' when it formed the connection. MySQL slaves do not use that flag. Now, if the line between the two systems died in the middle of a conversation (an actual data transfer) then a shorter -net-write-timeout or --net-read-timeout would expire and the session would die then. This is the interesting part yes, when the connection dies (whatever the link status is at this moment, idle or not). So I set wait_timeout=10. When the link is up, we clearly see that the idle connection is reset every 10 seconds : the show processlist clearly shows that the slave TCP source port changes, and time is reset from 10 to 0. Perfect. Well this behavior is due to slave_net_timeout, not to wait_timeout. So neither wait_timeout nor interactive_timeout (expected), net_read_timeout, net_write_timeout helped. However, when the link dies, the Binlog Dump process stays in the show processlist, I have to wait more than 1000 seconds for it to disappear. I made tests adding interactive_timeout=10, net_read_timeout=10 and net_write_timeout=10, however the behavior is the same. Did I miss something ? Of course goal is to monitor replication, from the slave (done and working thanks to slave_net_timeout), but from the master too (some more tuning needed), as we never know which one will be able to transmit the alert properly. Thank you very much Shawn. Hello, Would you have any further advice on this topic please ? Thank you again, Best regards, Ben -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: server-side logging of query errors?
Yep, as shown below:
root@audit-db.ec2:(none) select fark from fark from fark fark fark from
frak;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use
near 'from fark fark fark from frak' at line 1
root@audit-db.ec2:(none)
Jun 24 16:29:52 audit-db percona-audit:
{audit_record:{name:Query,record:217_2015-06-24T16:29:52,timestamp:2015-06-24T16:29:52
UTC,command_class:error,connection_id:59,status:1064,sqltext:select
fark from fark from fark fark fark from frak,user:root[root] @
localhost [],host:localhost,os_user:,ip:}}
error 1064
On Wed, Jun 24, 2015 at 11:40 AM, Tomasz Chmielewski man...@wpkg.org
wrote:
Normal general log also logs everything including bad queries (i.e. SLCECT
BLAH BLAH;) - although does not say if it was an error (i.e. syntax) or not.
Does the audit plugin log the actual error?
Tomasz
On 2015-06-25 00:32, Singer Wang wrote:
The performance hit of the Percona Audit is 15% for disk logging and
for remote syslog we found it is lower. It logs everything including
bad queries (eg. select fark from fark from fark fark fark from frak).
You should be able to write a JSON parser that extracts what you want
based on the log (eg. STATUS, COMMAND, NAME).
On Wed, Jun 24, 2015 at 11:05 AM, Johan De Meersman
vegiv...@tuxera.be wrote:
-
FROM: Singer X.J. Wang w...@singerwang.com
SUBJECT: Re: server-side logging of query errors?
You could log all queries using the audit plugin, 15% hit..
Fair point, though: maybe one of the different audit plugins has
the capability to specifically log faulty requests. Have a look
through the slides from Percona Live London 2014, there was a talk
about auditing.
--
Unhappiness is discouraged and will be corrected with kitten
pictures.
Re: server-side logging of query errors?
Normal general log also logs everything including bad queries (i.e. SLCECT BLAH BLAH;) - although does not say if it was an error (i.e. syntax) or not. Does the audit plugin log the actual error? Tomasz On 2015-06-25 00:32, Singer Wang wrote: The performance hit of the Percona Audit is 15% for disk logging and for remote syslog we found it is lower. It logs everything including bad queries (eg. select fark from fark from fark fark fark from frak). You should be able to write a JSON parser that extracts what you want based on the log (eg. STATUS, COMMAND, NAME). On Wed, Jun 24, 2015 at 11:05 AM, Johan De Meersman vegiv...@tuxera.be wrote: - FROM: Singer X.J. Wang w...@singerwang.com SUBJECT: Re: server-side logging of query errors? You could log all queries using the audit plugin, 15% hit.. Fair point, though: maybe one of the different audit plugins has the capability to specifically log faulty requests. Have a look through the slides from Percona Live London 2014, there was a talk about auditing. -- Unhappiness is discouraged and will be corrected with kitten pictures. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
