A user requests this:

"In the "Backup Database as an SQL Dump" feature, please add an option to place the generated SQL in the windows clipboard instead of, or in addition to, saving it to a file."

same applies to other export options, refer to Forums post:

http://www.webyog.com/forums//index.php?showtopic=4563

One user requested for an additional action button on the SQL Dump dialog to read the exported file into a new query editor tab.

Refer to Forums post: http://www.webyog.com/forums//index.php?showtopic=4785

One more user requested the same "copy sql statements to the clipboard instead of exporting it" in Support Ticket = 8934

couldn't you open a new query window and paste the results into that or put the queries at the end of the current query window?

Comment deleted

Another user requested for "EXPORT TO CLIPBOARD". Ticket number:#9860

Issue 1375 has been merged into this issue.

One user is forum requested: Add an option to EXPORT (CTRL+ALT+C) to CLIPBOARD in ExportAs.. dialog. This would be another checkbox that allows the output to go to the Copy/Paste clipboard buffer instead of a file.

In fact, maybe instead of just the clipboard, SQLyog would load the clip buffer AND automatically create a new Query Tab (CTRL+T) and paste this SQL into it.

Refer to: http://www.webyog.com/forums/index.php?showtopic=5216

One user is forum requested: Add an option to EXPORT (CTRL+ALT+C) to CLIPBOARD in ExportAs.. dialog. This would be another checkbox that allows the output to go to the Copy/Paste clipboard buffer instead of a file.

related: in http://www.webyog.com/forums/index.php?showtopic=6289 user requested a direct context menu option to CREATE TABLE based on result set.

• http://www.webyog.com/forums/index.php?showtopic=6311

Issue 1791 marked as a duplicate.

• http://www.webyog.com/forums/index.php?showtopic=6577

Ticket HS 15583382/2529/: user requests an option to generate INSERT statements for selected rows (a variation of 'copy selected rows to clipboard' -- but generating SQL INSERT statements and not CSV-formatted data.

There may be some overlap of http://code.google.com/p/sqlyog/issues/detail?id=1983 (refer ticket referenced in previous comment)