WWW.MSDE.BIZ ‘MSDE Backup / Restore’ Instructions
Registering a MSDE / SQL Server
Connecting to the MSDE / SQL Server
Editing MSDE / SQL Server Connection
Properties
Viewing MSDE / SQL Server
Information
Viewing MSDE / SQL Server Error Logs
Viewing Contents of a Backup Device
Action: "Database -
Differential"
Important Information Regarding
Un-Installing
Two default options are provided for starting MSDE Backup. The first option is to double click the ‘MSDE’ icon (icon show below) that can be found on the Windows Desktop and the second option is to use the Windows Start menu. To use the use start menu click on the following ‘Start | Programs | MSDE Backup’.
![]()
Figure 1: Icon for MSDE Backup
When MSDE Backup is started it first always displays the MSDE Backup end user licence agreement. Please read this agreement and then tick the box in the bottom left corner of the screen if you understand and agree to the licence agreement. Once this latter box is ticked you can press the ‘OK’ button and MSDE Backup shall start. If you do not understand or agree with the licence agreement you should press the ‘Terminate’ button. When terminate is pressed, MSDE Backup shall close down.
When the MSDE Backup has loaded the initial screen like the following is displayed.

Figure 2: Initial Screen
If this is the first time that you have used MSDE Backup it is first necessary to register a server group and then register MSDE Server. Please see ‘Registering a Server Group’ and ‘Registering a MSDE / SQL Server’ for more information.
MSDE Backup allows you to organise your MSDE servers and SQL Servers into groups. For example if you have a couple of SQL Servers that are only used for accounting you may want to set-up a server group called accounting, or perhaps you also have a couple of SQL Servers that are used only for marketing so again you may wish to create a marketing group. For an example of what this would like see below.

Figure 3: Example of Server Groups
To register a Server Group, do the following:

Figure 4: Register New Server Group
Please note that a server group can only be unregistered if it does not contain any registered SQL Servers. To un-registered a Server Group do the following:
To register a SQL Server, do the following:

Figure 5: Registering a SQL Server

Figure 6: Register SQL Server Dialog

Figure 7: SQL Server Registered
To connect to the registered MSDE / SQL Server simply press the ‘+’ against the SQL Server in the tree view. A connection is then attempted and if successful the tree view shall expand. An example of this is shown below.

Figure 8: Successful Connection
Should the connection be un-successful see the ‘Editing MSDE / SQL Server Connection Properties’ section below.
If you are unable to connect to a MSDE / SQL Server this is possible due to the incorrect username or password being used. To edit these latter details do the following:

Figure 9: Edit Server Registration Properties
Note it is not possible to edit the name of the SQL Server that you are connecting to. Your only option here is to delete the SQL Server registration and create a new SQL Server registration.
If the attempt to connect to your MSDE / SQL Server was un-successful an error message shall be displayed. If this is the case it is recommended that you first verify that the SQL Server is running. This can be achieved by following these instructions:

Figure 10: SQL Server Service Manager (Copyright of Microsoft)
If you are still unable to connect it is likely that your connection settings are incorrect. To establish and update your connection settings do the following:

Figure 11: Edit Server Registration Properties
Hopefully you should now be able to connect. Note the default MSDE password for user ‘sa’ is a empty password.
To view MSDE / SQL Server information, do the following:

Figure 12: Server Version Information
To view the MSDE / SQL Server Error Logs, do the following:

Figure 13: SQL Server Error Logs
· Using the mouse, select the error log that you require to view.
To create a ‘Backup Device’ on your MSDE / SQL Server using ‘MSDE Backup’, do the following:

Figure 14: New Backup Device

Figure 15: New Backup Device Dialog
· Enter a name for new backup device in the ‘Device Name’ edit box. The device name represents a logical name that is meaningful to yourself
· Select the corresponding disk or tape option.
· You should now enter the full path on the SQL Server of where the new backup device is going to be stored.
· If the disk option is selected the ‘Browse’ button ‘…’ can be pressed which allows you to browse the directories on the SQL Server. You should browse to a directory that already exists and can then select a file that already exists, or enter a name of a new file. Please note the ‘Browse’ option does not allow you to create new directories. An example of the ‘Browse’ dialog is shown below.

Figure 16: Browse Dialog

Figure 17: New Backup Device Dialog Populated
To delete an existing MSDE / SQL Server backup device, do the following:

Figure 18: Backup Devices

Figure 19: Deleting a Backup Device
To view the contents of a backup device follow the same instructions as ‘Deleting A Backup Device’, however select ‘View Contents’ from the context menu that is displayed when the mouse is right clicked (see Figure 19). An example screen of the contents of backup device are shown below.

Figure 20: Backup Device Contents
In to perform a backup you should have as a minimum already of registered your MSDE / SQL Server with ‘MSDE Backup / Restore’, please see section ‘Registering a MSDE / SQL Server’ for instructions on how to do this. Once you have registered your MSDE Server follow these instructions.
Your data is often one of your most valuable assets to your company and because of this it is essential that you have a disaster recovery plan. The plan should be tested at regular intervals to ensure that your backups are correct and that no problems exist with your media. In order to test your backups it is recommended that you restore your data to a new database.
It is highly recommended that you visit Microsoft's website for detailed information concerning SQL Server backing-up and restores. WWW.MSDE.BIZ or any of its representatives are not liable for the quality of your backups.

Figure 21: Backing-Up

Figure 22: Backup Dialog

Figure 23: Accounts database being selected for backup.
Since SQL Server allows on-line backups it is suggested that "Database - Complete" backups are performed when allowable (i.e. for small databases). The advantage of performing a complete backup is that the restore process is simplified, since only one action is required for a restore (i.e. restore of the complete database).
Should your database be of considerable size it is suggested that you perform a combination of "Database - Complete" backups and "Database - Differential" backups. Using this latter method, for example you could perform a complete backup every Sunday and for every other day you would perform a differential backup. The differential backup, backs-up all the changes that have occurred since the last complete backup. The advantage with this approach is that differential backups should not take as long to perform as complete backups, since only the changes are backed-up. When doing a restore, two actions would generally be required. The first action would be to restore the complete backup and the second action would be to restore the latest differential backup. If you find that your differential backup is taking almost as long to complete as your complete backup, it is suggested that you perform the complete backups on a more regular interval.
"Transaction Log" backups should be used for databases that are extremely large and also have many updates occurring on them. A "Transaction Log" backup, backups all the transactions that have occurred from when the transaction log was last truncated. When implementing transaction log backup it is essential that you first perform a "Database - Complete" and then backup the transaction log at periodic intervals. In order to maintain the integrity of the transaction log backups, it is essential that the log is not truncated. The transaction log can be truncated by the following methods (1) Complete database backup is performed, (2) Backup of transaction log is performed with the truncate on completion option ticked, (3) A manual truncation, (4) The SQL 7 Server "Truncate Log on Check Point" option is on, and, (6) The SQL Server 2000 recovery model is set to Simple.

Figure 24: Backup Feedback
In order to perform a restore using ‘MSDE Backup / Restore’, follow these instructions:

Figure 25: Restoring

Figure 26: Restore Dialog

Figure 27: Selecting a Backup for Restore
· With the ‘Backup Contents’ form you should now select only one of the backups from within the backup set for restore. A backup is selected by using the mouse, and clicking in the ‘Restore’ column. In the above figure, the backup at position 1 has been selected for restore. After selection of the backup you are returned to the ‘Backup’ dialog which has now been updated with information concerning the specific backup to be restored, the figure below gives an example of this.

Figure 28: Restore with Backup to be Restored Selected
· The ‘Restore Database Files To’ information can now be edited if required. The column ‘Restore Physical Location (Editable)’ allows you to manually edit the file paths so that the database and log files can be restored to specific locations. Generally these are left at their default.
· The ‘Database State After Restore’ and the option ‘Database Fully Operational’ should be left checked if you want the database to be fully operational after the restore. If you have additional transaction logs that you require to restore then the ‘Non operational so that additional transaction logs can be restored’, should be checked.
· Press the ‘OK’ button and the restore shall occur. During the restore process, feedback of the percentage completed of the restore is returned as shown in the following figure.

Figure 29: Restore Progress
In order to detach a database from MSDE / SQL Server do the following:

Figure 30: Detaching a Database
· Select the ‘Detach Database’ option from the menu. A ‘Detach Database’ dialog will now be displayed as shown below.

Figure 31: Detach Database Dialog
· Press the ‘Detach’ button and you shall be prompted to confirm the detachment of the database base.
· After confirmation of detachment the database is detached and you shall then be returned to the main form.
To attach a database to a MSDE / SQL Server follow these instructions:

Figure 32: Attaching a Database

Figure 33: Attaching a Database
To un-install MSDE Backup use the Windows application ‘Add or Remove Programs’ and remove the program ‘MSDE Backup’.
The MSDE Backup un-installation program does not remove the SQL DMO library files (i.e. SQLDMO.dll). These library files shall remain in the ‘MSDE Backup’ folder in case any other applications refer to them.
If you manually delete these files, it is possible that another application may fail if they are reliant on SQL DMO.
Should this occur it is suggested that you search your computer’s files system for another SQLDMO.dll file. Once found go to the command prompt (i.e. DOS) and change directory until you are in the directory where you found the SQLDMO.dll file. In the SQLDMO.dll directory type ‘regsvr32 SQLDMO.dll’. This latter command registers the SQLDMO.dll library so it can be found by other applications.
Should you require support regarding this product please email WWW.MSDE.BIZ at Support@MSDE.biz
Please email any suggestions that you may have to Suggestions@MSDE.biz