Oct 13, 2014 The sqlcmd utility lets you run entire SQL script files full of t-sql via command prompt. Leveraging this tool, you can create a batch file to run the sql script files in sequence. How To Execute A SQL Script File Via Command Prompt With SQLCMD. Although there are TONS of command line options for executing a sql script. Just executing a sql. VBScript does not 'execute' files. This would be bad. Any website you visited could then potentially 'execute' any file on your computer. In VB you can use the Shell command. I use.SQL files as well, which are pretty much query files to our SQL Server. What are you tryign to accomplish here?

Introduction to Running an SQL File in Postgres

This tutorial will explain how to run an SQL file in Postgres, using the .sql extension, in a terminal or command prompt window. This can be accomplished in one of two ways, from inside of the PSQL command-line interface itself or from outside of PSQL. The article will also provide an overview of the options for the commands used to run a SQL file in Postgres.

Prerequisites to Run an SQL file in Postgres

• PostgreSQL must be properly installed and running. Execute the service postgresql status command to confirm the status of PostgreSQL is active. Press the CTRL + C keys to exit.

• The interactive PSQL command-line for PostgreSQL must be properly installed and working. Execute the psql -V command to confirm the status. The results should resemble the following:

Create a SQL File that will Execute with PostgreSQL

Navigate to the project folder or directory by executing the cd (change directory) command in a terminal or command-prompt window.

Create an SQL file using a text editor or terminal-based editor

Create the SQL file with a text editor or a terminal-based editor like nano, gedit or vim. Execute the following bash command to enter the .sql file in the current directory using nano:

Once inside, enter some SQL commands into the SQL file for later execution. Following is an example of a command used to return all of the record rows in the PostgreSQL table named some_table:

The results should resemble the following:

NOTE: Just press CTRL+O to output any changes to the file in nano. However, be aware this will overwrite any changes to the file, or it will create a new file called test.sql if a file does not already exist.

Run a SQL file in Postgres using the ‘psql’ command

Now execute the SQL file in the terminal window. Confirm there is a database created with some table data that can be used to test the psql command. A role or user for that database will also be required.

Options for the ‘psql’ command to run a SQL file in Postgres

Following is a brief explanation of each of the options, or flags, used for the psql command that will execute the SQL script file:

psql -U USER_NAME_HERE — The -U flag is used to specify the user role that will execute the script. This option can be omited if this option’s username is the first parameter. The default username is the system’s current username, if one has not been explicitly specified.

psql -h 127.0.0.1 — The -h flag is for the remote host or domain IP address where the PostgreSQL server is running. Use 127.0.0.1 for a localhost server.

psql -d some_database — The -d option is used for the database name.

psql -a — The -a or --echo-all flags will print all of the lines in the SQL file that conatin any content.

psql -f /some/path/my_script_name.sql — The -f option will instruct psql to execute the file. This is arguably the most critical of all the options.

Execute the SQL file in PostgreSQL from the terminal

The final step in this process is to execute the file using the psql command while connecting with an username, host and database. Note that this example uses the objectrocket role.

The following command can be used to access the test.sql file created earlier:

Use the ‘-a’ option to print everything while executing a SQL file in Postgres

The -a option, also referred to as the --echo-all option, is used to echo, or print, all of the input lines that contain any content. This includes the SQL comments and the original SQL commands or statements being executed.

The following is an example of the --echo-all option:

The results should resemble the following:

NOTE: Be aware that the -a option will print everything contained in the file, including commands and the original SQL statement.

Connect to PostgreSQL and then run a SQL file using ‘psql’

Run Sql File In Psql

The i command can aslo be used to execute the SQL file from within the psql interface.

Thepsql must be entered though a database and a specified user or by connecting to a database once inside psql, using a ROLE that has access to the database, with the c command.

Connect to PostgreSQL without a database connection

The following example demonstrates how to connect to PostgreSQL with a specified ROLE, but without specifying a particular database:

The following example uses the c command, followed by the database name, to connect to a database before executing the SQL script:

Execute the following i command to run the SQL file:

NOTE: If no path is specified, then PSQL will use the directory that was last accessed before connecting to PostgreSQL in order to execute the SQL file.

The following screenshot provides an overview:

Conclusion to Executing a SQL File in Postgres

Vbscript To Run .sql File Download

This tutorial explained two ways to run an SQL file in Postgres, specifically from inside the PSQL command-line interface or from outside of PSQL using the -f option. The article covered how to create an SQL file using a text editor or terminal-based editor that will execute with PostgreSQL, how to execute the SQL file from the terminal, connect to PostgreSQL and run a SQL file. The tutorial also covered how to run a SQL file in Postgres using the PSQL’ command and the options for the commands along with an explanation of each option. Remember that if no path is specified when connecting to PostgreSQL without a database connection, PSQL will use the directory that was last accessed prior connecting to PostgreSQL to execute the SQL file.

SQL developers can run vb script files from SQL Server t-sql codes by using xp_cmdshell procedure.
It is sometimes a requirement especially for web developers to call vb script from SQL Server engine and execute vbscript from sql code.

Of course calling vbscript from sql can be solved by using CLR in SQL Server after the release of SQL Server 2005.
T-SQL developers and SQL Server database administrators can develop CLR objects and CLR procedures and use .NET Framework objects and methods instead of using sql VBScript.

I hope you will learn SQL Server sql vbscript call methods as many database professionals do on Microsoft data platform after reading this sql tutorial.

Here is a very simple vbscript example where vb script codes are stored in a text file named 'vb-sample.vbs'.
You can also create this vbscript file by running Notepad.exe and copy-paste the below vbscript code into it. Save and name the vbscript file as vb-sample.vbs in root folder of C drive for example.

The above vbscript code create a text file name vbscript-from-sql-server.txt in root of C drive.

Vbscript To Run .sql File Converter

Here is execute VBScript sql query example for tsql developers and SQL Server database administrators can use in their applications.

I can guess how you are astonished when you see how easy it is to call vbscript using sql code in MS SQL Server database.
Using tsql vbscript files can be executed by using the xp_cmdshell stored procedure which can reach Windows server objects as seen in this example.

When xp_cmdshell extended stored procedure is executed, the following error message might come up.
This error thrown from SQL Server engine is caused related with the SQL Server configuration settings.
On the current installed SQL Server instance, execute xp_cmdshell command might be prevented as a matter of security.
The default SQL Server configuration setting for xp_cmdshell is disabled by default with a value of '0' for run-value.

First set 'show advanced options' configuration settings to 1 on the SQL Server 2008 instance using the below t-sql script.

If 'show advanced options' settings parameter is 0 or disabled, trying to configure 'xp_cmdshell' setting will cause the following error message.

So first enable 'show advanced options', then enable 'xp_cmdshell'
Then you are ready to configure xp_cmdshell configuration settings for SQL Server 2008 database instance using the below sql code.

If you have not yet configured xp_cmdshell, run the below sql batch for configuring related parameters.