Comments for dbForge Team Blog

Comment on dbForge Studio for MySql on Linux family operating systems by Rui Marques

Rui Marques — Tue, 30 Aug 2011 09:40:18 +0000

Greate. Waiting for a full functional version on linux.

With current mono evolution why not a full port to Mono enabling MAC, WIN and Linux users to enjoy this great tool?

Comment on Export a MySQL Table to a CSV File Methods Overview by Peter Laursen

Peter Laursen — Tue, 31 May 2011 09:31:07 +0000

Every GUI client I can think of have similar client-side functionalities for exports (to CSV and other formats).

Comment on Export a MySQL Table to a CSV File Methods Overview by Stephen

Stephen — Tue, 31 May 2011 01:52:09 +0000

through .NET component, export data to csv can be much easier maybe. And please allow me introduce you Free Data Export Component. you can get more info here: http://www.e-iceblue.com/Introduce/free-dataexport-component.html

Comment on Export a MySQL Table to a CSV File Methods Overview by Shlomi Noach

Shlomi Noach — Mon, 30 May 2011 12:23:09 +0000

Hi,
You can also:
* mysqldump –tab=/path/for/export
This still means you have to invoke it locally (ie on the server side), but it solves the “single file” problem

Or, you can:
* mysql -h remote_host -e “SELECT * FROM my_schema.my_table” –batch –silent > my_file.csv
Which solves all aforementioned problems.

Regards

Comment on How To: Create a Database Diagram Using a Sketch Image by .jp

.jp — Wed, 06 Oct 2010 08:35:17 +0000

Thank you for the good question. Really, if one developer works on database structure and its further implementation, than it is not necessary for him to create a database sketch with the help of another tool and to repeat the same actions in a database designer. It’s easier for him to start creating a database with the tool right away. But in most cases a sketch of the future database is drawn on a blackboard or paper before database implementation. After that it is being discussed, corrected, approved. And if the project is a distributed one, and analytics, managers and developers work in different offices, tasks from a database designer come to a developer as a set of documents with requirements among which can be this database sketch as a set of entities drawn on paper (or prepared as a digital document, for example, in MS Visio). And it is more convenient for a developer to have such sketch in front of him directly in the instrument, as it was described in our article.

Comment on How To: Create a Database Diagram Using a Sketch Image by Justin Swanhart

Justin Swanhart — Wed, 06 Oct 2010 05:21:02 +0000

I don’t understand why you wouldn’t just make the model in dbForge (or MySQL workbench)? You really build your schema in an image application before you build it in a modeling application?

Comment on How To: Kill User Sessions in Oracle by .jp

.jp — Mon, 30 Aug 2010 13:30:26 +0000

Thank you for your comment! You are right, using "execute immediate" reduces the size of code significantly, and makes the code simpler and easier for interpretation. Really we've created a script using "execute immediate" in the beginning, but we had to rewrite it using the DBMS_SQL package, because this package can be executed on all Oracle servers regardless of the version. As it was written in the article, we used this scripts in autotests for our new product, dbForge Data Compare for Oracle, that supports all Oracle server versions from 7.3 to 11g.

Comment on How To: Kill User Sessions in Oracle by Chris Neumueller

Chris Neumueller — Mon, 30 Aug 2010 08:31:08 +0000

Hi!

Even for a DBA script, you should be aware of sql injection, so use bind variables. Also, it’s not necessary to use dbms_sql. This should suffice (untested, just wrote it ad hoc):

declare
c_user constant varchar2(30) := ‘SCOTT’;
v_kill_stmt varchar2(4000) := ‘alter system kill session ”{SID},{SERIAL}”’;
begin
for i in (select sid,serial#
from v$session
where username=C_USER) loop
execute immediate replace(replace(v_kill_stmt,
‘{SID}’,i.sid),
‘{SERIAL}’,i.serial#);
end loop;
end;
/

Regards,
Chris

Comment on How to: Create MySQL Database in One Shot by .jp

.jp — Mon, 26 Jul 2010 12:36:56 +0000

Yes, you may be right on the one hand that for a small database it’s more convenient to type scripts manually instead of performing a lot of clicks on visual editors. But on the other hand, when you have to think over the design of a future database or redesign an existing one, from our point of view it’s more convenient to see the created (or modified) database structure as a database diagram with database relations displayed on it and perform the changes in the database structure on this database diagram.

Comment on How To: Export/Import Large MySQL Database by Aleksandr Serdyuk

Aleksandr Serdyuk — Mon, 26 Jul 2010 11:42:07 +0000

I agree with you that in case when you need a regular backup for multi-terabyte database it is faster to suspend MySQL server and dump file system. Because our product is more developer-oriented than DBA-oriented, article merely talks about making development snapshots (i.e. exports). And there are cases when database developer simply is not allowed to accomplish all operations you described. So he must wait for export to complete.