Running from command line

[ Follow Ups ] [ Post Followup ] [ SQL Script Builder Forum ]

Posted by Nic. P. 82.253.201.7 on November 24 2007 12:26:31:

Congrats on this great tool! I gave a try migrating to PostgreSQL 8.2 a FoxPro database of up to 52 tables/ ~1 G) and succeeded in one shot. I will give another try from Pervasive -> PostgreSQL but I am already convinced.

I intend to use the tool from batch files or others programs and to perform scheduled tasks automatically (data backups in context of smooth migration plan). I think that the implementation of a set of Command Line parameters would help perform theses tasks within SQL Script Builder without having to do so manually.

Common parameters might be:
/ODBC_Source (the name of the ODBC system source)
/SCRIPT_Filename (the output sql filename where the script in saved after completion)
/LOG_Filename (the log for this conversion)
/CONVERT_Format (convert to output format: PostgreSQL, Pervasive…)
/CONTENT (Table, Data or Table&Data)
/DROP_Table (On or Off)
/QUOTES (Yes or No)
/DATE_Formating (set format for date/time)
/MISC_Options
/LOGIN (user_name+password)

For the best convenience, these startup parameters might be handled in a text file which name is passed as argument to the application running in silent mode.
I am convinced that this feature will provide this tool with a level of automation enough to have it integrated in an heterogeneous databases maintenance system.

Regards,

NP

Follow Ups:

Re: Running from command line - Dave 00:50:29 November 28 2007 (0)

Post a Followup

* : (Required)

* Name:
E-Mail:

* Subject:

* Comments:
> Congrats on this great tool! I gave a try migrating to PostgreSQL 8.2 a FoxPro database of up to 52 tables/ 1 G) and succeeded in one shot. I will give another try from Pervasive -> PostgreSQL but I am already convinced. > > I intend to use the tool from batch files or others programs and to perform scheduled tasks automatically (data backups in context of smooth migration plan). I think that the implementation of a set of Command Line parameters would help perform theses tasks within SQL Script Builder without having to do so manually. > > Common parameters might be: > /ODBC_Source (the name of the ODBC system source) > /SCRIPT_Filename (the output sql filename where the script in saved after completion) > /LOG_Filename (the log for this conversion) > /CONVERT_Format (convert to output format: PostgreSQL, Pervasive) > /CONTENT (Table, Data or Table&Data) > /DROP_Table (On or Off) > /QUOTES (Yes or No) > /DATE_Formating (set format for date/time) > /MISC_Options > /LOGIN (user_name+password) > > For the best convenience, these startup parameters might be handled in a text file which name is passed as argument to the application running in silent mode. > I am convinced that this feature will provide this tool with a level of automation enough to have it integrated in an heterogeneous databases maintenance system. > > Regards, > > NP

Optional Link URL:
Link Title:
Optional Image URL:

Enter the code shown :

[ Follow Ups ] [ Post Followup ] [ SQL Script Builder Forum ]