Help‎ > ‎

Databases (SQL Server)

SQL Server databases

The first step in backing up SQL Server databases is to download Microsoft's SQL Server library. We do not distribute that library due to its licence conditions. At the time of writing it can be found at Extract the files and find sqljdbc.jar in the resulting folder.

Then copy sqljdbc.jar to:

1) the directory <Bonkey>\plugins\. If you selected the default installation directory, this will most likely be c:\Program Files\Bonkey\plugins\.

2) the directory <Bonkey>\plugins\BonkeyCore_1.0.0\lib.

Then use Start->Run to run "net stop BonkeyService" and then "net start BonkeyService" (without quotes). Alternatively, you can use the Services control panel to restart the Bonkey service. Finally, restart the Bonkey front-end by quitting and starting the application anew.

Note for Java 1.6+: if you are using version 1.6 or higher of the Java runtime, you will need to use the most recent version of the library (available on the same page). When downloaded, this is named sqljdbc4.jar. Rename it to sqljdbc.jar and follow the instructions as above.

Configuration in Bonkey

To backup an SQL Server database, create a location and choose the  'SQL Server database' type.

The directory into which SQL Server puts a copy of the database must be configured. This can be set by going to File->Preferences and selecting the 'Databases' preference page. The directory must be on which SQL Server has permission to write to (<SQL Server>\MSSQL.1\MSSQL\Backup is generally suitable). Note that this is not the final backup location, it is merely where the backup file is put by SQL Server before being copied by Bonkey.

Once the database location has been created, browsing the location will show the accessible databases. To backup one of these databases, drag the database into a backup group. The database will then be backed up according to the settings for that group.

Backup up remote SQL Server databases

The process described above applies for SQL Server instances running on remote machines (ie machines other than that on which Bonkey is running). The only extra consideration is that the directory chosen in the Preferences dialog must be writeable by SQL Server on the remote machine, and must be accessible to Bonkey from the local machine.

The best way to achieve this is for the directory to be set to a shared directory. The shared directory should allow both reading and writing. The directory should be entered in the Preferences dialog using its network path (for example, \\Server01\SQLBackup\). Most computers running Windows XP have such a directory at \\<ComputerName>>\SharedDocs.

Back to contents