FAQs - ApexSQL Script

The application supports SQL Server 7.0, SQL Server 2000 and SQL Server 2005 versions.

No, this possibility is not supported by ApexSQL Script.

Yes. You can select multiple databases for scripting either in the Project Wizard or in the Select Database panel.

Yes. The generated script can be changed and saved with the Script Editor, where the script displays after its generation.

Yes. You can set up file extensions in the Options dialog. The extensions can be used on scripting the objects into individual files. For more information see {extension} tag in the help file.

There are several output types supported: T-SQL, VBScript, .Net Executable and C# Project. The output type can be set up in the Output Type step of the Script Wizard.

At the Script Wizard File step the Script All Objects to a Single File option should be turned ON. All the objects will be scripted into a single file with the name, specified by a template.

In the Script Wizard File step the Script All Objects to an Individual File option should be turned ON. All the objects will be scripted into individual files with the names, specified by a template.

Yes. Just choose your objects and select Both Structure and Data option in the Script Wizard. This will combine both modes.

You can change the default Author name in the Options dialog. It will affect the script headers if you will specify {author} tag.

Yes, see Output tab of the Options dialog.

Yes, the Create and Check In Script to Source Control option of the Output Options step of Script Wizard allows you to use the Source Control as storage for your scripts.

ApexSQL Script is full functional with Visual Source Safe and other SCC-compliant source control systems.

Yes. Make sure that Create Directory for Each Object Type option is ON. Check the help file for more information.

Yes, it could be started as MS-DOS application from command line with the specified ".com" extension. To see the available options, the executable should be started in command line mode with /? or /help options.

To run the packages, the .NET environment version 1.1 or higher should be present.

The owner/schema for the objects can be changed/mapped in the Owner Mapping step of the Script Wizard. The Manage Owners and Change Owner options should be set.

No, ApexSQL Script can't script encrypted objects.

No, the application does not generate the object existence check.

The grid values are saved within a project file. Your values will be restored after loading the previously saved project.

It determines a maximum count of the rows to be scripted for a particular table.

Make sure that Include Transaction Handling option is ON. It encloses the scripted statements within a transaction that will be rolled back on any error.

Yes, it manages Referential Integrity problems related to triggers and constraints; this is controlled by the Integrity Tab of the Script Wizard. Make sure that Disable All Triggers and Constraints Prior To Loading Data option is ON if you want to disable the triggers and constrains prior to loading data.

Yes, in the Main Grid it is possible to set the new alias for scripting the table/view by editing the Alias columns for the specified object.

Yes. You can use /inc and /exc switches for such purpose. They allow you specifying several objects at once.

Yes. Use /ft switch. It allows you specifying the literals in combination with the existing accepted tags.

The /d switch supports pointing the list of the databases. You should split them by a space.

ApexSQL Script offers you explicit options for working with Visual Source Safe and SourceGear Vault systems. You can also set up your SCC-compliant system in the Structure Wizard in Graphical mode and save the settings within a project file. Then you can use your saved project file in /pf switch.

Yes. You can either set them up explicitly by the defined switch set, or set them up in your project file and then use the project file instead in /pf switch.