Devart Forums

I really love using dbForge but the one thing I find which is terribly annoying and which currently poses a huge inconvenience for me is the behavior of the software when exporting data.

I have several DB connections, one of which is localhost. Now lets say I want to export the data, whether in a single file or all the tables as separate files, I find that I am unable to remove the database name from the .sql file via a setting. More often than not the data which is being exported is for use in another database with a different name.

With the INSERT command I have this

INSERT INTO database_name.table_name

what I want is the following:

INSERT INTO table_name - without the database name.

Every time I export data I now have to do this in singular files then have to do a search and replace to remove the database name from the .sql files.

Is there perhaps some setting somewhere that I can set to change this default behaviour? I also find that the during the export process - if I have selected multiple tables to export I am unable to edit the destination table or database name - this destination table name would be more useful if it could be the destination DB name or perhaps have the option to select a destination table and destination database. Its all fine and well when you exporting a single table but is not all that practical when exporting multiple tables.

You can change this in the 'Destination table name' field being on the 'Options' page of the 'Data Export' wizard. Please also see the 'SQL Document Options, Data Export Wizard' topic in the product's Help documentation.

Unfortunately, this still can't be changed when exporting multiple tables at once. However, we will review such an option when developing the next product version.

Yes I am aware of the fact that you can change the table destination name but that can only be done if you are exporting a single table, but as of yet when exporting the entire database there is no option to change the destination database name - that is something that is actually quite necessary.

No one exports an entire database for import in another database table for table and that is exactly what one has to do if you want to use that "destination table" feature either that or you have to do a search and replace in each individual table name and remove the database name. Then another thing, if that database is a very large database, you cant even use the search and replace because dbForge freezes up.

A simple task like this export a DB for import into another DB should not have to be as time consuming task like this. Im actually very surprised that the software doesnt not make provision for this.

I hope to see this feature in the software soon.

We would like to let you know that we have released a new version 4.0 of dbForge Studio for SQL Server where the feature you requested is implemented http://www.devart.com/dbforge/sql/studio/download.html

Thank you for your help in improving dbForge Studio for SQL Server.