Dev Hound uses TurboDB as its default database however SQL Server can also be used.

Custom fields can be created in Dev Hound using the configuration tool available on the Dev Hound Web Server PC. To access the configuration tool choose Start -> Programs -> Dev Hound -> Configuration :

• Click on the Database tab
• Enter the name of the field
• Choose the type of the field
• If you choose the String type you need to enter the number of characters into the size field
• Click on the Add button to add the field to the database

Custom fields can be deleted by clicking on the field from the list box and clicking the delete button 

The Dev Hound database is located in one file called devhound.tdbd (if the default database is used: see notes). This file can be backed up by:

• Click on the Admin tab
• Click the Backup Database link
• The database will be backed up to two different files. One with the weekday and one with the month. For example devhound.tdbd.backup_friday, devhound.tdbd.backup_july

Note: By default Dev Hound performs an automatic backup each day (this is configured in default settings). A backup file for each day of the week is kept and each month of the year. This way you should always have a backup for at least a week and a history of backups for the year. It is also important that the backups are kept offsite.

For SQL Server database the filename will depend on the SQL Server setup however will generally be called devhound.mdf and located in the data folder of the installation. If you have created multiple databases the filename will change according to the name you gave to the database. Also note that whilst Dev Hound will attempt to backup this file it may not succeed as the SQL Server database may be in use at the time. For backups it is recommended that a dedicated database backup tool be used (such as the Microsoft Backup tool that comes with Windows XP)
Backup History

To show the history of backups completed:

• Click on the Admin tab
• Click on the Backup History link
• You will be shown a list of backups completed with the date and time they have been completed

Your database can be restored by replacing the devhound.tdbd file located in the data directory. You may use one of the automatic backups. It is advisable that you shut down your web server before restoring to prevent anyone from interfering with the restore procedure 

You may view and edit tables in the Dev Hound database or export data in Microsoft Excel format through the Dev Hound configuration tool. To do this:

• Click Start -> Programs -> Dev Hound -> Configuration
• Click on the Database tab (the following screen will appear)

Dev Hound can use either its built-in database TurboDB or SQL Server. The TurboDB database has the advantage of only consuming a small amount of resources, is compact, doesnt require additional installation or configuration and can be used on externally hosted windows boxes that do not support databases. Converting to SQL Server has the advantage of the solid support provided by Microsoft as well as speed enhancements and options for futher integration and access from other products (eg Crystal decisions or custom applications).

Converting to SQL Server
To convert your existing database to SQL Server first make sure you have MDSE or the full SQL Server installed on your PC. It is possible to have Dev Hound create a database on a different PC to your web server however this is not recommended for speed reasons.

• Click Start -> Programs -> Dev Hound -> Configuration
• Click on the Database tab
• Change the Data Provider from TurboDB to SQL Server
• Click on the Settings button and provide the SQL Server settings and click Apply
• Click on the Upgrade button and click on Next
• Your existing database will be converted to SQL Server
• You will need to restart the Web Server

Reverting from SQL Server back to TurboDB
You can change the data provider back to TurboDB at any time and resume using your old database however any data entered into the SQL Server database will be lost

Converting multiple databases
If you have previously created multiple databases in Dev Hound it is possible convert all of these to SQL Server database but it is not automatic (yet). You will need to be familiar with SQL Server. First convert your main database to SQL Server and rename the devhound SQL Server database to something else. Then move one by one the file devhound.tdbd from the subfolders of the data folder. Click the Upgrade button to convert the database again and recreate the devhound SQL Server database. Rename the SQL Server database to an appropriate name. Repeat the process for each database then rename your original devhound SQL Server database as devhound. This process can be time consuming and requires some skill - if required please email Nexus Concepts for help

Multiple Dev Hound Databases
Dev Hound can access multiple Dev Hound databases either with TurboDB or SQL Server. These multiple databases are stored on the same server PC. To create a new blank database:

• Click Start -> Programs -> Dev Hound -> Configuration
• Click on the Database tab
• Click on the New button
• Enter a database name and click Next
• An empty Dev Hound database will then be created

To access a different database use the url: http://servername/devhound/devhound.dll?db=databasename where databasename is the name of the database you created above. If not using IIS then remove the /devhound part. 

The following fields are available for use in SQL statements: 

To get your Dev Hound database started a feature is available to import clients, issues, etc from an XML file. To do this:

• Open the Configuration tool from Start -> Programs -> Dev Hound
• Click on the Import tab
• Click on the Import button and choose the XML to import

XML Templates
The template for the required XML is available from the configuration tool in the import tab. Simply choose from the drop down menu the table you would like a template for. It will show the template with an example record.

Importing Notes
Dev Hound has some requirements when importing records. Firstly, if you are importing issues then the field base must be equal to 1 (This must equal 2 for support calls, 3 for knowledge base articles).

Some fields are lookup values - for example in Issues the field software is a lookup value into the table software. See the section on table list and table relationships for more information.

It is also possible to use the SQL tab to modify the data in Dev Hound. For example if you have imported issues and your software id's do not match Dev Hounds you could use an SQL statement like update issues set software = 3 where software = 29. If you are unsure getting your data into Dev Hound please email support@nexusconcepts.com for advice.