SQLPro Studio does not have Export SQL option

[tjdraper]

I like the interface and presentation of SQLPro Studio, but it's missing a crucial feature: the ability to import/export SQL files. I was sort of surprised that this ability was missing since SQLPro for SQLite at least has the option to export SQL.

[noah-goodrich]

I have been a long-time user of SQL Pro for MySQL which has a File -> Export option which allows me to export all database objects for a given MySQL database.

I had my employer purchase a copy of SQLPro Studio yesterday so I could work in both MySQL and MSSQL and was surprised to find this feature missing from the Pro Studio offering.

Is this in the works? If not, what would be required to get this feature added and do you have a recommended workaround in the meantime?

[iammoen]

Yea honestly I was just about to buy SQLPro Studio but this is a deal breaker. +1 to the request. I'll have to look elsewhere for now.

[nkev]

I just assumed I could export database schemas and just went ahead and bought it... I'm very disappointed.

[tamm]

Just ran into this issue, +1 to adding this asap

[natsu90]

+1 to this request

[mholtzhausen]

Same Here +1 Disappointing not to have this in studio

[diegoulloao]

It's a essential feature, but unfortunately missing. So, what are dev waiting for? +1 to the request!

[mcmanussean]

gorgeous interface with zero ability in import / export databases... the only thing I need it to do...

[hankinsoft]

Export will be available for MSSQL databases in the next version. I'll be investigating MySQL, Postgres and Oracle soon. Please let me know which type of database you wish to export from as that helps me prioritize the list.

[iammoen]

Export will be available for MSSQL databases in the next version. I'll be investigating MySQL, Postgres and Oracle soon. Please let me know which type of database you wish to export from as that helps me prioritize the list.

Thats wonderful. Main thing for me is MSSQL as I have other programs to use for MySQL and Postgres. But one unified program for all wouldn't be bad. MySQL would be second in line for me.

[diegoulloao]

Export will be available for MSSQL databases in the next version. I'll be investigating MySQL, Postgres and Oracle soon. Please let me know which type of database you wish to export from as that helps me prioritize the list.

Perfect. Go on!! I think MySQL is essential. Push into the list ;)

[robbyemmert]

Postgres is also essential. I think they all are. This is a pretty basic feature.

[hankinsoft]

Just wanted to note, exports are available for MSSQL in all the latest version of SQLPro for MSSQL and SQLPro Studio. Features of export as as follows:

• Choices of what to export, such as Tables, Views, Stored Procedures, etc.
• Options to include export data or not and whether to generate batch insert statements or individual.
• Choices to save directly to a file, generate to new tab, or copy to clipboard.
• Context sensitive, so if you right click the database node and choose export then every will be selected for export (tables, views, types, procedures, etc), but if you were to right click a table and choose export, then only that table would default as selected.

Notes: Opening a large script may be slow if you are using Mojave and have Word Wrap disabled. There are multiple issues with Mojave with Word Wrap (textedit does not allow word wrap to be disabled). The quick solution if you run into this issue is to ensure word-wrap is enabled.

MySQL support will be next, followed by Postgres. If you run into any issues or have any suggestions for export, please let me know.

[cgenevier]

Is there any update on the ability to export Postgresql?

[djheru]

Exports are a basic feature. Would love to see this added. I'd probably be able to convince management to buy licenses for the rest of the team

[suderman]

Is MySQL import/export coming to the iPadOS version? I want to buy this (pricey) app, but that basic feature is the deal breaker.

[AllenEllis]

One more vote - came here looking to move a Postgres database from one machine to another. Will uninstall for now but will definitely keep an eye on the project!

[house9]

Looks like export was added for Postgres at some point, although very hidden and doesn't come up when searching the help

look for export icon in results pane:

[djheru]

Following up on my comment from December of last year, SQL export would be a big plus. Unfortunately, the team has settled on a competing free product that has this functionality. I'm regretting coming out of my own pocket for the license for this now 😞

[zixufang]

+1 to the request!

[samuelsylvander]

First of all, thank you for a great product. I've used it for a year now and love it.

However, I am also surprised that it doesn't have this export functionality for Postgres. So here is another +1 request for this functionality.

[hankinsoft]

I am actively working on the export Postgres. I hope to have the first draft of it available late next week.

[rliessum]

I run into issues that stored procedures are not exported properly. @hankinsoft do you want a separate issue for it or is it a know bug? Using SQLPro for MSSQL.

Generated SQL:

IF EXISTS ( SELECT * FROM sysobjects WHERE  id = object_id(N'DDI.usp_tblRequestDDI_Domain_Del') AND OBJECTPROPERTY(id, N'IsProcedure') = 1 )
	DROP PROCEDURE DDI.usp_tblRequestDDI_Domain_Del
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
<null>
GO

[hankinsoft]

@rliessum could you post this as a new issue? Ideally letting me know your server version would be appreciated as well.

[hankinsoft]

Also, for those waiting for Postgres export, both Tables and Views are ready for the next build which will be available early next week. Procedures, etc will be coming afterwards.

[rliessum]

@rliessum could you post this as a new issue? Ideally letting me know your server version would be appreciated as well.

Sure thing, will collect the information.

[cvillalobos]

@hankinsoft, Is there any reason my SQLPro is not showing the Stored Procedure option to export?

[hankinsoft]

@cvillalobos What do you get for results when you run this query:

SELECT
	specific_schema + '.' + specific_name AS fullName,
	specific_schema AS objectName,
	specific_name AS objectName,
	'Procedures' AS TYPE,
	5 AS sortOrder
FROM
	INFORMATION_SCHEMA.ROUTINES
WHERE
	routine_type IN('PROCEDURE')
	AND LEFT(Routine_Name, 3) NOT IN ('sp_', 'xp_', 'ms_')
	AND specific_schema NOT IN ('sys')

[cvillalobos]

I don't get any results.

[hankinsoft]

In Microsoft SQL Server, the sp_ prefix is generally reserved for system stored procedures and as such they are not included in sql server exports by default. I'll take a look at making this case specific for the next build, as that should let you continue, but not export system procedures for others.