VT3000 - Scripting SQL Databases

From Versacall Support
Jump to navigation Jump to search
Call Now 858-677-6766 SubmitTckBtn.png EmailUsBtn.png





GeneralHeader.png

Overview
Use the instructions below to script an SQL database. This method is only needed when the user is attempting to use a newer version database in an older version. Example: Use a SQL Server 2017 database on an SQL 2012 Server. This guide will explain how to create the script, there is another guide on running the script inside SQL Server.


Requirements
See Requirements Here
1. The VT3000 Core Software installed and running on your system.
2. The Databases must already exist in your SQL Server Instance.
3. A backup file saved to the Computer/Server that the SQL Server Instance is running on.
4. SQL Server Management Studio installed on the Computer/Server running the SQL Server Instance or on a computer that can access the computer from your network.
5. SQL Server Instance name (IP Address/Computer Domain Name & SQL Server Instance Name).
6. SQL Server Instance login (Username & Password).





InstructionHeader.png

Step 1.
Open the VT3000 web-interface - select VT3000 - select Administration - select System Settings - select Global.
3114 1.png
Icon systemsettings.png
Icon globalsettings.png
Administration System Settings Global




Step 2.
Under the Database Locations heading, expand the details for one of the databases.
Global2.png




Step 3.
If the SQL Server Name field looks like the image below, you will need to access the VersaCall computer. User Name & Password will differ, we are representing it with (X).
Global3.png




Step 4.
If the SQL Server Name field has anything different from the image in Step # 3, you will need to access the Server that is storing the databases. You may need to contact your IT department for assistance.




Step 5.
Navigating to the Backup files can be difficult inside SQL Server. We suggest creating a new folder to place all the database files in. Open Windows File Explorer by selecting the icon on your computer.
SQL15.png
File Explorer




Step 6.
Select the C: Drive - right click in the drive and select Add New - select Folder. Name the folder SQL Backup.
SQL16.png
SLQ51.png
SQL17.png
C: Drive New Folder SQL Backup




Step 7.
Select the Windows Start button - find the Microsoft SQL Server 2008 R2 (or your version up to SQL Server 2016) folder - select the folder to expand it.
If you are using SQL Server 2017 or above you will select the SQL Server Tools (your version) folder.
SQL18.png
SQL19.png
SQL22.png
Windows Start 2008 to 2016 Versions Versions above 2016




Step 8.
Find the SQL Server Management Studio icon - select it.
SQL20.png




Step 9.
On the Log In page enter the following for the Default VersaCall setup where SQL Express is being used - click on the Connect button. If you are accessing another server, please contact your IT department for the sign in information.
SQL21.png
Server Name - 127.0.0.1\SQLEXPRESS
Login - sa
Password - SQLServer123




Step 10.
Expand the Databases folder - all of the VersaCall databases available will show.
ResSQL2.png




Step 11.
Click on the Database you want to script so that it is highlighted.
ResSQL3.png




Step 12.
Right click on the selected database and select Tasks - Generate Scripts.
Script6.png




Step 13.
A Generate Scripts wizard will show on the screen - select the Next button.
Script7.png




Step 14.
Ensure the "Script entire database and all database objects" is selected - click on the Next button.
Script8.png




Step 15.
Select "Save to File" and "Single File".
Script9.png




Step 16.
You will need to select the folder that you want to save the Script file to - select the ... button next to the File Name field.
Scripting1.png




Step 17.
If you created the SQL Backup folder explained in the previous steps - use the file tree to navigate to C:\SQL Backup - click on the folder so that it is highlighted. If you have a different folder that you want to use, navigate to its location.
ResSQL6.png




Step 18.
You will need to rename the file. Click in the File Name field and edit the script.sql file name to be the name of the database you have selected.
For our example we will change the file name to VT3000_Configuration.sql.
Scripting2.png
Scripting3.png




Step 19.
Click on the Advanced button.
Script10.png




Step 20.
An Advanced Scripting Options window will load. Scroll down the list of options until you get to the Script for Server Version option - click on it so that it is highlighted.
Script11.png




Step 21.
Click on the down arrow in the version field - select the SQL Server version you will be moving the database to. Example shows SQL Server 2012.
Script12.png




Step 22.
Scroll down the list of options until you find Types of data to script - click on it so that it is highlighted.
Script13.png




Step 23.
Double check that both settings are correct - click on the OK button.
Script15.png




Step 24.
Click on the Next button on the Generating Scripts Wizard window.
Script16.png




Step 25.
On the Summary window - ensure that the Target is correct and that the file name has been changed - click on the Next button.
Script17.png




Step 26.
On the Summary window - ensure that the Target is correct and that the file name has been changed - click on the Next button.
Script18.png




Step 26.
Repeat the steps to make scripts of any additional databases. Ensure that you name each one by the database name. Once you have scripted all of the databases that are required, your SQL Backup folder should look similar to the image below. Close all open windows.
Scripting4.png





RelatedHowTos.png
Select a Guide Here
Backup VersaCall Databases using SQL Server
Update VersaCall Databases using SQL Server
Backup VersaCall Databases using VT3000 - Download Files
Backup VersaCall Databases using VT3000 - Make a Local Backup
Backup VersaCall Databases using VT3000 - Send the Backup to VersaCall
Update VersaCall Databases using VT3000
Restore VersaCall Databases using VT3000
How to Fix the "Database Connection Closed" Error



SearchHeader.png




VC Footer.png
Follow Us On LinkedIn View our Blog