http://support.microsoft.com/kb/257716 determine instance name of SQL database. See step 12, doesn't look exactly like that but has an "installed instances" key that lists all instances on one line, and then each instance has it's own registry folder below "Microsoft SQL server".
net stop mssql$microsoftsmlbiz (command in batch file at LCFP to stop MSSQL server)
net start mssql$microsoftsmlbiz to start
This worked on Windows XP Pro, but server may be different
Article: 41623
Title: Using Automated Backups With Sage MIP Fund Accounting
This article applies to: All Products, all versions.
Question
I'm using an automated backup program to backup my accounting data. How do I add the Sage MIP Fund Accounting databases to the automated backup program?
Answer
Please Note: Prior to version 7 the ‘INSTANCE_NAME’ was MIP_ENGINE. After version 7 it could be any name. Please refer to KB article#183531 to determine the name of the SQL instance being used by your installation and substitute that name for ‘INSTANCE_NAME’ used in our example.
You may manually backup your database(s) by using the backup utility that is located in the Administration module.
In the Administration module, select File > Backup. By default, the backup files are stored on the server in the C:\Program Files\Microsoft SQL Server\MSSQL$INSTANCE_NAME\Backup folder (or alternate drive selected during the installation of the program).
You may include this folder in your automated backup program's backup routine.
However, if you do not want to rely on manual backups, you can backup the data folder's contents (.mdf and .ldf files) if you stop the MSSQL$INSTANCE_NAME service.
After the MSSQL$INSTANCE_NAME services starts, you will unable to use an automated backup for the application's database(s) because the services' process conflicts with the automated backup program. You must stop the service in order for the automated backup program to backup the files in the Data folder (default location C:\Program Files\Microsoft SQL Server\MSSQL$INSTANCE_NAME\Data).
You may stop/start the MSSQL$INSTANCE_NAME service in two ways:
Option 1 - Manually stop/start the service
Option 2 - Executing a Scheduled Task to stop/start the service
Executing a Scheduled Task takes advantage of the Service Control Manager (SCM) utility within Windows 2000 to stop and start a service. It requires a minimum amount of configuration. Please note: This process requires Local Administrator rights on the server.
(If you configured the MSSQL$INSTANCE_NAME service to start automatically, and you don't reboot your server on a daily basis after the completion of the backup, you will also need to schedule the restart of the MSSQL$INSTANCE_NAME service.)
1. Open the Windows Control Panel (Start > Settings > Control Panel) and select Scheduled Tasks.
2. Select File > New > Scheduled Task. Name the Task and double click on the newly named task.
3. In the "Run" field on the Task Tab type: "C:\Program Files\Microsoft SQL Server\80\Tools\BINN\scm.exe" -Action 6 -Server [Server Name] -Service MSSQL$INSTANCE_NAME -Silent 1 (If the Operating System is not installed on the C: drive, locate the Microsoft SQL Server\80\Tools\BINN\scm.exe file and adjust the path accordingly.) (Include the double quotation marks in the command line.)
4. (If you don't enter anything for the [Server Name], it will default to the computer name. If you enter a Server Name, don't include the brackets.)
5. Select the Schedule tab and enter the appropriate "Scheduled Task" frequency and "Start Times". You may customize additional settings and security to suit your organizations specific needs.
6. Select <Apply>.
7. When prompted for a password, enter your Windows Local Administrator password and confirm.
1. Follow steps listed in a. above.
2. In Step 3, change the command to read: "C:\Program Files\Microsoft SQL Server\80\Tools\BINN\scm.exe" -Action 1 -Server [Server Name] -Service MSSQL$INSTANCE_NAME -Silent 1 (If the Operating System is not installed on the C: drive, locate the Microsoft SQL Server\80\Tools\BINN\scm.exe file and adjust the path accordingly.) (Include the double quotation marks in the command line.)
(Ensure that you schedule enough time for the backup process to execute completely between the stop and start times of the MSSQL$INSTANCE_NAME service.)
Please Note: If users are in the database when the service stops, all unsaved data will be lost.
For version 7.0 and later, if your backup program has the Agent for Microsoft SQL Server 2000 you may configure it to backup the Sage MIP Fund Accounting database using the SA account and the password you assigned during the installation or upgrade to version 7. Please contact that vendor for help configuring the backup software.