Converting Classroom Manager to SQL
Requirements
Maplewood for Windows must be installed and Web Updates must be done before proceeding. SQL Server 2000 SP3 (Mixed Mode Authentication is required). SQL Client tools with Backwards Compatibility installed on the workstation from which you are running the conversion.
Limitations
Take-home disks are not available in the SQL version of Classroom Manager. Depending on how your environment is configured, your Maplewood backup may no longer include a backup of the Classroom Manager database.
Conversion Instructions
1. Ensure that all Classroom Manager take-home disks are checked in.
2. Back up the existing Maplewood database, and make sure there are no users in Classroom Manager.
3. Run Maplewood for Windows version 4.5 and login in as the supervisor.
4. Under menu options File, School Setup, School Information, select the „Achievement Settings‟ tab and check the „Use Enterprise Version of Classroom Manager‟ box. Select the „Convert Classroom Manager‟ button.
5. Read the following screen and click Yes if appropriate.
6. Fill out the following fields with your location-specific information. Make sure you click the convert button. You will be given a chance to view any errors that occur at the end of the conversion.
7. Your Classroom Manager database (clsmgr32.mcm) and Comments Database (Comments.mcm) under the Maplewood “Clsmgr” folder will be automatically renamed to Clsmgr.sql and Comments.sql, respectively.
Creating Backups
Depending on your environment there are 2 ways to do this. The two setups both involve the isolation level of your SQL server.
Complete Isolation
The server is not capable of accessing files on any other computer, no other computer can access files on the SQL server it can only be seen via its TCP port. Backup is done via SQL Manager and is stored on the SQL Server. A backup of the SQL DB is not done when you do a backup in Maplewood.
1. Start SQL Server Enterprise Manager.
2. Open the server containing the database to be backed up.
3. Open the Management folder.
4. Right click on backup and select Backup a Database.
5. Select the database to backup.
6. Give the backup a name, select type of backup (we recommend all backups be Database – complete).
7. Add a Destination; in most cases this will be a file in a location reserved for SQL backups on this server. This directory may also be backed up to a secondary media to allow the backups to be taken off site.
8. You should now put the check mark beside schedule and then set the schedule properties. A weekly backup occurring every one week on Monday to Friday either first thing in the morning or last thing at night should be sufficient for most cases. You can create backups more often if you so desire.
9. After setting the schedule you may get a message similar to the following:”The SQLServerAgent on target server „SERVERNAME‟ is stopped. Make sure it is running during the scheduled execution of the job.” If you do get the message, you should check with your system administrator and see if there is a reason that the SQLSERVERAGENT is not running. If there is, you may have to find an alternate way to do backups. If not, set the service to automatically
start and then make sure the service is started manually. If you do not see the message, then the service is already running and you have nothing further to do.
NOTE: When your server runs in isolation mode you must exclude Classroom Manager from your Maplewood backups or the backup will not complete. This includes automatic backups as well as any manual backups.
Limited Access
The server is capable of accessing files on another computer (at least the one containing the Maplewood Administration data). However the servers are not part of a common domain so individual accounts must be created on each computer to allow backups to be successful. In a domain situation not all steps will usually be required.
1. Create an account on the server to act as the SQL Server and SQL Server Agent Service account.
2. Start SQL Server Enterprise Manager.
3. Right click on the Server that contains the Maplewood Data then select properties.
4. Now go to the Security tab. If you notice that the Startup service account section is unavailable there are a few possibilities. The account you are logged into Windows as does not have administration rights, you are trying to administer a different SQL Server that the one you are currently logged in to, or if you are logged in as a domain administrator the SQL server may not be part of the domain and there is no corresponding local administration account (an administrator account with the same username and password as the account on the domain you are currently using) on the standalone server.
5. Change the startup service account option from “System account” to “This account” and then specify the username and password for the account created in step 1 above.
NOTE: It is recommended that you do this through the SQL Server Enterprise Manager to ensure all registry and file system rights get changed appropriately. If you wish to change the account through the Service applet that is in Control Panel you will need to reference the Microsoft TechNet article “How to change the SQL Server or SQL Server Agent Service account without using SQL Enterprise Manager in SQL Server 2000” (http://support.microsoft.com/default.aspx?scid=kb;en-us;238311&sd=tech).
6. Now that we know which account is going to be needing access to the server that contains the Maplewood Administration data, we can ensure that this account is both present on the server containing the data and given rights to both the share and directory where the data exists.
Extra Reading
10 Steps to Help Secure SQL Server 2000
http://www.microsoft.com/sql/techinfo/administration/2000/security/securingsqlserver.mspx
SQL Server 2000 SP3 Security Features and Best Practices
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sp3sec00.mspx