Teratrax Database Manager

Teratrax Database Manager has been discontinued. Please refer to the following help file (v4.6) for details on using an existing copy of this product:

 

Help File

Teratrax Database Manager is a streamlined SQL Server and MSDE administration tool designed to help you work with your databases in an easy and efficient way.

Supported Database Servers

SQL Server 2005
SQL Server 2005 Express
SQL Server 2000
MSDE 2000
SQL Server 7.0
MSDE 1.0

Supported Operating Systems

Windows XP
Windows 2000 (SP3 or higher; ADO 2.7 or higher)
Windows Server 2003

Teratrax Database Manager requires the Microsoft .NET Framework 2.0

Connecting to SQL Server and MSDE

Before you can work with Teratrax Database Manager, you need to establish a connection to your SQL Server. Whether you are connecting over the Internet, intranet, or simply locally, you need to enter the required information in the Connect dialog.

The Connect Dialog

The Connect dialog is used to connect to an instance of Microsoft SQL Server or MSDE. Enter the following information in the Connect dialog:

  • Server Name: name or IP address of the server you are connecting to. For example, SQLServ or SQLServ\Instance2 for a named instance. Use “(local)” for the local server. For the default SQL Server 2005 Express Edition, use (local)\SQLEXPRESS.
  • Windows Authentication: indicates that the connection will be authenticated using your Windows account.
  • SQL Server Authentication: indicates that the connection will be authenticated using a SQL Server account.
  • Login Name: the login name if you are using SQL Server Authentication.
  • Password: the password if you are using SQL Server Authentication.
  • Remember connection parameters to this server: this option allows you to save the information entered in this window so next time it will connect automatically. Information will be saved with basic encryption.
  • Client Network Utility: See Client Network Utility.

Client Network Utility

The Client Network Utility button allows you to configure the client protocols and aliases that Windows should use when connecting to the server. The Client Network Utility is part of the Microsoft Data Access Components (MDAC), which contains ADO.

If you need to connect to a server over the internet, or if your local network supports TCP/IP only, you need to use the TCP/IP protocol. Make sure that TCP/IP is enabled in the Client Network Utility and given top priority (moved to the top of the list or used as the only protocol). If the connection is failing, you can tell which protocol you are using from the error message you get. If the error message starts with [DBNETLIB], you are connecting under TCP/IP. If it starts with [DBNMPNTW], you are using Named Pipes.

In ADO 2.8, no protocols are enabled by default. This does not mean that you cannot connect. It simply means that a default sequence will be engaged in connecting to determine the protocol that will first succeed. Not all versions of ADO default to the same protocols. ADO 2.5 for example, defaults to Named Pipes.

Changing TCP/IP Port

The Client Network Utility lets you change the way ADO connects to SQL Server and MSDE by changing the protocols used. It also provides support for changing the default port (1433) SQL Server is listening on. To change the default port, highlight the TCP/IP protocol then click on the Properties button. Change the port number to new port number and click Ok. If you connect to more than one server and they have different ports, you can create an alias for the server that listens on ports other than 1433 from the aliases tab.

Troubleshooting Connections

To reduce the risks of security vulnerabilities, Microsoft constantly adds security features (like those added in Windows XP SP2) to prevent attacks and secure SQL Server environment. These features make connecting to SQL Server increasingly difficult to troubleshoot. One of the most common error messages users get is “SQL Server does not exist or access denied” or “Specified SQL Server not found”. To troubleshoot connection problems, follow the following steps:

  1. Verify that SQL Server or MSDE is installed and running: Right-click the “My Computer” icon and select “Manage”. Once the management consol is open, navigate to Services and Applications ->  Services. If MSSQLSERVER is in the list of services, then the default instance of SQL Server or MSDE is installed on the computer. Other instances may exist, in which case they will be listed as MSSQL$****, where the asterisks indicate the name of the instance.
  2. If you are connecting remotely (to a server on a different machine), make sure your connection is not blocked by any firewalls on either machines including Windows built-in Internet Connection Firewall (ICF) and/or Windows Firewall. Contact your system administrator for firewall configuration.
  3. If you are referencing an instance of SQL Server 2000 or MSDE 2000 other than the default instance, use the convention <server_name>\<instance_name> (example ProdServ\Sales).
  4. Make sure you don’t have an older ADO version (see ADO Versions below for details).
  5. Make sure your client protocols are configured properly (see Client Network Utility for details).
  6. If you are connecting to a remote server and the server name is not resolved with DNS, use the IP address itself instead of the server name.

User Interface

The main window of Teratrax Database Manager is composed of the Server Explorer pane and the Items pane. The Server Explorer pane lets you navigate all your server objects (including servers and databases) in a hierarchical structure composed of multiple nodes. Each node represents a different type of database objects. You can add your enterprise servers to the Server Explorer with a single right-click. By default, you have the “(local)” server added so you can start working with databases on the local computer right away. The Items pane displays a list of all items contained in the selected node of the Server Explorer. Right-click on objects in the Items pane to see a list of features applicable to that object (For example, if you right-click on a stored procedure name, the compile option will be visible). The moving Splitter separates the Server Explorer pane from the Items pane and allows you to resize the two panes. Click inside a pane to make it the active pane. Alternatively, you can use the Tab key to move between panes.

Importing Data Into SQL Server Databases

The Import Data dialog allows you to import both Excel and CSV files in to your SQL Server database. You can import Excel and CSV files into an existing table or into a new table. If you are importing into an existing table ensure that the total number of columns in the Excel file or CSV file matches the number of columns in the destination table.

The maximum number of columns supported when importing into a new table is 32 columns. Import will create a new table based on the name supplied. Table columns will be created as nvarchar(2000).

The Import Data dialog

  • Import File: If you know the path and name of the file you wish to import, enter them in the Import File text box. If you are uncertain, click on the browse button to locate the file you wish to import. If an Excel file is chosen, the Excel Sheet drop down will list the various sheets in the Excel book.
  • Excel Sheet: This drop down is enabled when an Excel file is chosen. Select the sheet you wish to import from the list.
  • Server: Displays the Server instance you are connected to. This is a static option and is for informational use only.
  • Database: This is a list of all available databases to the current user.
  • Import data into a new table: To import into a new table select this option and enter the table name you wish to create. Columns will be created based on the number of columns defined in your import file up to a maximum of 32.
  • Import data into an existing table: A list of tables will be available based on the current database selected. If this option is chosen ensure that the destination table selected have the same number of columns as in your import file.

Importing XML Files

The import XML feature uses the three files generated during the XML export. These files have the same name but different file extensions:

XML: Contains the actual data content of the exported table or view.

XSD:  Contains the schema definition of the exported table or view.

TXD: Contains additional schema definition proprietary to Teratrax.

The XSD and TXD files must be kept in the same folder and with the same names as the XML file in order for Teratrax Database Manager to import the XML file into a SQL Server database. Do not delete or rename these files. The following list illustrates the table structure elements that are preserved after importing XML files:

Structure Element Preserved
Data Types YES
Column Size, Precision, & Scale YES
Allow Nulls Indicator YES
Identity Indicator YES
Collation YES
Computed Column Indicator YES
Defaults NO
ANSI Padding NO
Rules (Deprecated in SQL Server 2005) NO
Triggers NO
Indexes NO
Primary Keys NO
Foreign Keys NO
Unique Constraints NO
Check Constraints NO

Exporting SQL Server Data

The Export Data dialog allows you to export SQL Server table and view content into CSV files.

The Export Data Dialog

  • Server: Displays the SQL Server instance you are connected to. This is a static box and is for informational use only.
  • Database: Displays the SQL Server database you are connected to. This is a static box and is for informational use only.
  • Table/View: Displays the SQL Server table or view you are exporting. This is a static box and is for informational use only.
  • Export All Rows: Check this box to export all rows in the table or view. To export a subset of the rows, uncheck this box and click on Edit SQL, then add a WHERE clause to the default query. If you are exporting into XML, do not change the original part or the query.
  • Save To: The location of the exported file.

Exporting XML Files

The export XML feature generates three files with the same file name and the following extensions:

XML: Contains the actual data content of the exported table or view.

XSD:  Contains the schema definition of the exported table or view.

TXD: Contains additional schema definition proprietary to Teratrax.

The XSD and TXD files must be kept in the same folder and with the same names as the XML file in order for Teratrax Database Manager to import the XML file into a SQL Server database. Do not delete or rename these files.

Backup and Restore Individual Tables Using XML

The XML export and import features in Teratrax Database Manager provide a way to backup and restore an individual table in your database. You can restore a table that has been exported into XML by simply importing it back into the database. You can import the table on the same instance or any other SQL Server instance creating a copy of the table. During the import, you can specify a new table name to create the table alongside the old table if you are importing into the same database. You can export a table from a SQL Server 7 or SQL Server 2000 instance and import it on a SQL Server 2005 instance under any existing schema by simply specifying the full name of the new table ([Schema].[Table]).

When exporting a table into XML, Teratrax Database Manager stores schema definition information about the exported table in the .XSD and .TXD files. When importing an XML file, Teratrax Database Manager uses the .XSD and .TXD files associated with it to recreate the table the same way it was at the time of the export. The following list illustrates the table structure elements that are preserved after importing XML files:

Structure Element Preserved
Data Types YES
Column Size, Precision, & Scale YES
Allow Nulls Indicator YES
Identity Indicator YES
Collation YES
Computed Column Indicator YES
Defaults NO
ANSI Padding NO
Rules (Deprecated in SQL Server 2005) NO
Triggers NO
Indexes NO
Primary Keys NO
Foreign Keys NO
Unique Constraints NO
Check Constraints NO

 

Copy Tables Between SQL Server Instances

The Copy, Paste Structure, and Paste Data features in Teratrax Database Manager provide an easy and convenient way to duplicate tables in the same database or different databases on the same SQL Server instance. To copy a table from one SQL Server instance to another, you need to use the XML export and import features.

The XML export and import features in Teratrax Database Manager provide a way to copy an individual table from one SQL Server instance to  another. Simply export the table to your local computer in XML format and import it into a database on a different SQL Server instance. You can export a table from a SQL Server 7 or SQL Server 2000 instance and import it on a SQL Server 2005 instance under any existing schema by simply specifying the full name of the new table ([Schema].[Table]).

When exporting a table into XML, Teratrax Database Manager stores schema definition information about the exported table in the .XSD and .TXD files. When importing an XML file, Teratrax Database Manager uses the .XSD and .TXD files associated with it to recreate the table the same way it was at the time of the export. The following list illustrates the table structure elements that are preserved after importing XML files:

Structure Element Preserved
Data Types YES
Column Size, Precision, & Scale YES
Allow Nulls Indicator YES
Identity Indicator YES
Collation YES
Computed Column Indicator YES
Defaults NO
ANSI Padding NO
Rules (Deprecated in SQL Server 2005) NO
Triggers NO
Indexes NO
Primary Keys NO
Foreign Keys NO
Unique Constraints NO
Check Constraints NO

Backup and Restore SQL Server and MSDE Databases

The backup and restore features provide an important safeguard for protecting data stored in Microsoft SQL Server databases.

Database Backup

To backup a database, select the Databases node in the Server Explorer pane then, in the Items pane, right click the database you want to backup. In the Backup File box, enter the path and file name of your backup file then click Backup to perform the backup. Note that the path and file name you enter in this box are relative to the server. If you are connecting to the local server, the backup file will be created on the computer you are working on. If you are connecting to a remote server (LAN, WAN, or Internet), the backup file will be created on the remote server (for example, C:\MyBackups\DB1.bkp would be created on the C:\ drive of the remote server). To perform a backup from one computer and leave the backup file on another computer, you need to use mapped network drives. For example, if you want to perform a backup of a database on computer A and leave the backup file on computer B, then computer A has to be able to access computer B’s hard drive via a mapped network drive (for example, X:\). The account used to run the SQL Server service on computer A needs to have write privileges to X:\ . The default “system” account does not have privileges to other computers.

If your database is hosted on the Internet and the use mapped network drives are not allowed by your database hosting provider, ask you hosting provider to create a folder for your backups on the server and give you the path of that folder so you can use it in your backup. Your provider should also be able to give you FTP access to that folder so you can download your backup files to your local computer.

Backup Files Containing Multiple Backup Devices

SQL Server backup files can contain more than one backup device. Backup files generated by Teratrax Database Manager can contain one backup device only. When restoring a database from a backup file that contains multiple backup devices, Teratrax Database Manager restores the first backup device in the file.

Database Restore

To restore a database, right click the Databases node in the Server Explorer pane and select “Restore…” to open the Restore Database dialog box. The dialog box contains the following:

  • Backup File: Enter the path of the backup file you want to restore. If you are connected to the “(local)” server, you can click the browse button next to this edit box to locate the backup file. If you are connected to any other server, the browse button will be disabled, in which case you have to type the path and file name of the backup file manually. The path and file name you enter are relative to the remote server (for example, C:\Backup\MyBackupFile.bkp references the C: drive on the server machine not the local computer).
  • Restore Database As: Enter the name that you want to give to the database that will be restored. If you are restoring a database with the same name as a currently existing database, Teratrax Database Manager will overwrite the current database. If the name you enter in the “Restore Database As” box is not the same as any database that currently exists, the restored database will be created with the new name irrelevant of the original name (useful if you are creating another copy of a database).
  • Move Files To: This edit box is equivalent to the WITH MOVE option in the RESTORE DATABASE command. When you perform a database backup, the location (folder) of the physical database files are saved in the backup file itself. When you do a restore, the server reads this information and attempts to recreate the physical database files in the same folder it came from. This can cause a problem if the original folder does not exists on the server anymore or if the backup file is from a different server with a folder path that does not exist on the current server. To override the original folder, specify a new path in the “Move Files To” edit box. Leaving this edit box empty will default to the original folder path. The “Move Files To” edit box is crucial if you want to create a copy of a database using backup and restore. If you do not specify a valid folder path in the “Move Files To” edit box, the server will generate an error saying that the files could not be created (because they are already in use by the original database).

Restoring a Database from a Backup File on a Remote Server to the Local Server

To restore a database from a file that is located on a different computer (for example, restoring from a mapped network drive), the Windows account used to start the SQL Server service has to be a non-system account with full control privileges to the backup file.

Restoring a Database from a Local File to a Remote Server

If you are restoring from a local file to a remote server, use a mapped network drive that points to your local drive from the remote server. The Windows account used to start the remote SQL Server service has to be a non-system account with full control privileges to the backup file.

Restoring Backup Files on Older Versions of SQL Server

You cannot restore a SQL Server 2000 backup file on a SQL Server 7 instance. Likewise, you cannot restore a SQL Server 2005 file on a SQL Server 2000 or SQL Server 7 instance.

Zipped Backup and Zipped Restore

The Zipped Backup and Zipped Restore options work in almost the same way as a regular backup and restore except for compression. The backup file in a Zipped Backup or Zipped Restore operation is compressed using the gzip compression algorithm in order to save disk space. The Zipped Backup operation compresses the backup file by up to 90% allowing you to create more backups using the same disk space. Zipped backups and restores are supported on local servers only and cannot be scheduled. The name of the server must start with “(Local)”. The compression algorithm does not support backup files larger than 4GB.

Working with Queries and Scripts

The SQL Query window in Teratrax Database Manager is a powerful graphical query tool designed to help you work with Structured Query Language (SQL) queries and scripts in an easy and efficient way. The SQL Query window allows you to:

  • Create, execute, and save scripts and queries
  • Quickly modify query results (grid)
  • Save query results as XML, HTML, and Excel
  • Easily write SQL scripts with syntax highlighting, parameter hinting, and code completion

The user interface is composed of multiple panes. The Editor pane is a text editor where you can enter SQL statements. The Results pane displays the returned recordset. The Errors pane displays error messages. If the SQL batches in the Editor pane return more than one recordset, a list of all returned recordsets will be made visible in the Recordsets pane. The Recordsets pane will not be displayed if your SQL batches return a single recordset. The moving Splitter separates the Editor pane from the rest of the panes. Click a pane to make it the active pane. Alternatively, press F6 to move between panes.

The Results pane displays the columns and rows from a table or query in a grid. You can modify the data in the grid. You can also insert and delete rows. If more than one recordset is returned, some of the recordsets may be returned as read only for performance purposes. The Recordsets pane will display the status of all recordsets as either “Read Only” or “Live”. Usually the first recordset in the batch is live.

Editor Pane

You can execute a complete script or only selected SQL statements in the SQL Query window. To execute a complete script, create or open the script in the Editor pane and press F5. To execute only selected SQL statements, highlight the lines of code in the Editor pane and press F5. Click on Working with SQL Batches and Statements for more information on the Results pane.

Syntax Highlighting, Parameter Hinting, and Code Completion

The Editor pane in the SQL Query window provides a convenient way to write SQL queries and scripts. The Editor’s syntax-highlighting, function parameter hinting, and SQL keyword auto completion features are designed to add visual elements to your SQL code.

Syntax Highlighting

Syntax-highlighting provides color coding to all T-SQL language elements, making your script easier to read and understand. The various color codes are:

  • T-SQL keywords (for example SELECT, SET, etc…) are blue
  • T-SQL functions (for example GETDATE(), COUNT, @@VERSION, etc…) are fuchsia
  • SQL operator and query joins keywords (for example ALL, LIKE, LEFT JOIN) are gray
  • Quoted strings are red
  • Comments are teal
  • Brackets and commas (,()[]) are maroon

Parameter Hinting

Function parameter hinting produces a list of expected parameters every time you type the name of a T-SQL function followed by a bracket. The hint saves you the hassle of going back to the manuals to retrieve function syntax.

Code Completion (Ctrl+<space bar>)

Code completion is an easy and convenient way to complete keywords after providing the first few letters of their spelling. This feature saves you time by not having to type the complete word and gives you a list of all possible ways your T-SQL keyword can be completed. Keywords include all T-SQL keywords plus system stored procedures and system tables. Start typing the command or SP name then press Ctrl+<space bar> to activate suggestions.

Working with SQL Batches and Statements

The Editor pane in the SQL Query window allows you to write SQL statements and batches and execute them against the database server you are connected to. You can execute a complete script or only selected SQL statements. To execute a complete script, create or open the script in the Editor pane then press F5. To execute only selected SQL statements, highlight the lines of code in the Editor pane then press F5.

SQL Statements vs. Batches

A SQL statement is a single SQL command (for example, SELECT * FROM table1 or SET NOCOUNT ON). A batch on the other hand, is a number of SQL statements sent to the server for execution as a whole unit. The statements in the batch are compiled into a single execution plan. Batches are separated by the GO command.

Users must follow the rules for batches. For example, any execution of a stored procedure after the first statement in a batch must include the EXECUTE keyword. The scope of local (user-defined) variables is limited to a batch, and cannot be referenced after a GO command.

The GO Command

GO is not a Transact-SQL statement; it is a command recognized by SQL utilities and Teratrax Database Manager to signal the end of a batch of SQL statements. Teratrax Database Manager interprets GO as a signal that it should send the current batch of SQL statements to the server. The current batch of statements is composed of all statements entered since the last GO, or since the start of the script if this is the first GO. If the last batch does not include a GO at the end, one will be added by Teratrax Database Manager.

A SQL statement cannot occupy the same line as a GO command. GO has to be the only command in the line.

Session Configuration (SET Options)

These are default settings for SET options for all ad-hoc queries in the SQL Query window:

Option

Default Setting

SET NOCOUNT OFF
SET CONCAT_NULL_YIELDS_NULL ON
SET ANSI_DEFAULTS ON
SET ARITHABORT ON
SET ANSI_NULLS ON
SET ANSI_NULL_DFLT_ON ON
SET ANSI_PADDING ON
SET ANSI_WARNINGS ON
SET CURSOR_CLOSE_ON_COMMIT OFF
SET IMPLICIT_TRANSACTIONS OFF
SET QUOTED_IDENTIFIER ON

 

Working with Results (Results Grid)

In addition to the Editor pane, in which you can manipulate data with the INSERT, UPDATE, and DELETE statements, The SQL Query window provides the Results pane, which is a graphical interface for viewing or modifying data.

The Results pane has a number of features that you can access from the Results Toolbar. The following is a list of the features on the toolbar from left to right:

  • First Row: Moves the row indicator to the first row in the Results grid.
  • Previous Row: Moves the row indicator to the row before the current row in the Results grid.
  • Next Row: Moves the row indicator to the row after the current row in the Results grid.
  • Last Row: Moves the row indicator to the last row in the Results grid.
  • Delete Current Row (Ctrl+Del): Deletes the current row after prompting for confirmation.
  • Insert New Row (Ctrl+Ins): Inserts a new and empty row in the grid. Fill in the data in the columns of the new row and move off the row to save the changes.
  • Saves Results As CSV: Saves the data in the Results grid to a comma-separated values (CSV) file, with column names as a header row, for use with Microsoft Excel. This option limits the results that you can save in a CSV file to the first 65536 rows in the grid (including header row). To export all rows into CSV, use the Export Data feature.
  • Save Results AS HTML: Saves the data in the Results grid to a HyperText Markup Language (HTML) file with column names as a header row.

Updating Data

You can update data in a row by simply editing the text and moving off the row to save the changes. Clicking inside a cell switches it to edit mode with the text inside the cell selected. Press Enter or F2 to unselect the text and move the cursor to the end of the cell. Once the cell is in edit mode, you can type your changes or right-click to have access to Undo, Cut, Copy, Paste, Delete, and Select All commands from the context menu. Press ESC to cancel changes before leaving the row.

To process the update in the database, Teratrax Database Manager searches for a unique index or primary key to uniquely identify the row in order to run the update against the database. If a unique index or primary key is not found, Teratrax Database Manager uses all columns in the table to uniquely identify the row. If there are other rows that are identical based on all columns (possible if table does not have a primary key or unique index), the update will fail with the following error message:

“Key column information is insufficient or incorrect. Too many rows were affected by update.”

Column Width

You have complete flexibility with the size of columns in the grid. Initially, Teratrax Database Manager defaults the width of all columns in the grid to 110 pixels. Drag the edge of the column to resize it. If you resize columns, Teratrax Database Manager will save the new column size the next time you run a query.

Grid Behavior with textntexttimestampvarbinaryimage, bit, and uniqueidentifier

Columns of data type text, ntext, timestamp, varbinary, and image are not displayed in the grid. Instead, an indicator (for example, MEMO) is displayed. Use the CONVERT function to display the underlying values for these data types. The following explains the various grid indicators:

  • Columns of type text and ntext are displayed in the grid as either “Memo” if the cell does not have data in it or “MEMO” if it contains a value.
  • Columns of type timestamp are displayed in the grid as either “Byte” if the cell does not have data in it or “BYTE” if it contains a value.
  • Columns of type varbinary are displayed in the grid as either “VarBytes” if the cell does not have data in it or “VARBYTES” if it contains a value.
  • Columns of type image are displayed in the grid as either “Blob” if the cell does not have data in it or “BLOB” if it contains a value.

Columns of type bit will display “True” for 1 and “False” for 0. To edit these cells, Type “True” or “T” for 1 and “False” or “F” for 0. The values in the database will still be saved as 1 and 0.

Columns of type uniqueidentifier will be displayed with the actual value. To edit these cells, Type a uniqueidentifier value (for example, {A9AEC7AB-88A5-41A0-9684-8A79ECD64547}).

When you save grid results, the underlying values (not the indicator) will be saved in the CSV, or HTML files.

Creating and Scheduling Jobs

To create a job, right-click the Jobs node in the Server Explorer and select New. This will open the Job dialog box which is composed of the following elements:

  • Job Name: the name you prefer to give to this job. Teratrax Database Manager defaults this field to “Job1”.
  • Server: the server name where the job will be created. This field contains the name of the current server in the Server Explorer pane.
  • SQL Script: the SQL code you want to run when this job is triggered. It’s always a good practice to select your database context first thing in the code so subsequent statements don’t end up executed against another database.
  • Schedule: determines when you want the job to run. The following options can be selected:
    1. When SQL Server Agent starts: job will be triggered when SQL Server Agent starts or re-starts.
    2. When server becomes idle: job will not be triggered as long as SQL Server is busy.
    3. Daily: job will be triggered every day at the time specified in the “Run this job at” field.
    4. Weekly (M T W Th F S Su): job will be triggered once a week on the specified day at the time specified in the “Run this job at” field.
    5. Monthly (occurs on day — of every month): job will run once a month on the specified day at the time specified in the “Run this job at” field.
  • Run this job at: the HH (hour on a 24-hour clock) and MM (minute) fields in this box determine the time the job should run. “Run this job at” is ignored for schedule options 1 and 2.

Once you have entered all necessary information for your job, click Ok to create and schedule the job. After the job has been created, you can manually trigger the job to run by right-clicking the job and selecting Start Job.

Select the jobs node in the Server Explorer pane to view job information listed in the Items pane. The columns in the list include “Last Run Status”, “Last Run”, and “Next Run”. These columns can help you determine if your job and schedule are working properly.

Creating Backup Job

Follow the following steps to create a scheduled backup job:

  1. Right-click the database name and select “Backup”.
  2. Enter a file name in the Backup File edit box.
  3. Click the “Schedule” button to open the Job window.
  4. Set the time for the schedule.
  5. Click OK to create the schedule and go back to the Backup Database window.
  6. At this point, the job has been created. Click cancel to leave the Backup Database window or “Ok” to run a regular backup.

After completion of these steps, you should see the job details in the Items pane when you select “Jobs” in the Server Explorer pane on the left hand side.

Customizing Menus

Teratrax Database Manager allows you to customize menus and toolbars creating quick shortcuts to the features that you use the most. You can add and remove buttons on menus and toolbars, and hide or display toolbars. You can customize the main menu bar the same way you customize any toolbar but you can’t hide the main menu bar.

To customize your menus and toolbars, select Customize Menus from the Tools menu in the main window or the SQL Query window. This will open the Customize dialog box.

The Actions Tab

To add an item to a menu or toolbar, drag any item from the Categories or Actions box and drop it on the appropriate location.

To add a separator, drag the “Drag to create Separators” button to the appropriate location.

To remove an item, simply drag it out of its location.

The Toolbars Tab

The Toolbars tab allows you to customize the display of text in the various toolbars. Select the target toolbar then change the Caption Options to None (for no text at all) or All (to show available text captions).

The Options Tab

The Options tab allows you to personalize your menus and toolbars. You can chose to show recently used items first, enlarge the size of icons, and change menu animations.