-
Title
Considerations when configuring the SQL database for migration purposes -
Description
QMM is shipped with a REDIST folder containing MSDE 2.0 (scaled down SQL 2000 version) which is used during express product setup. Is there any particular reason to choose SQL server instead of MSDE? What would be considered the best practice?
-
Cause
QMM for Exchange requires a database to store some settings and project information. Such a database doesn't require lots of space or special hardware, and because MSDE can be used free of charge, those are the main reasons why QMM comes with it. The fact that MSDE ships with QMM doesn't mean it's recommended and suggested to be utilized for all the scenarios.
-
Resolution
Below are some considerations:
If a company already has an existing SQL server then it might be preferable to useit and place QMM for Ex database there. In this case management and maintenance could be simplified. In order to use an existing SQL server admins just need to create a new DB, give the quest service account admin rights (assign the admin role) and ensure that name resolution from QMM console to this SQL server works.
Considerations for placing QMM for Ex database on an existing SQL server:
PROs:
- Usually such a server is a separate machine and should something happen to QMM console then the SQL DB will not be affected.- Backups and other maintenance jobs are normally performed on a regular basis.
- SQL Administrative tools would be already installed and in use, making access and administering easier. When troubleshooting database related issues, the tables can be opened and analyzed and modified (if support suggests or requests a change).
- If the need arises, then authentication can be changed to Windows authentication, password for the account can be changed quickly or the entire account can be changed and a new account utilized.
- Database can be easily moved to another SQL instance if needed. Backup or Copy (import/export) of database can be performed via few mouse clicks.
CONs:
- SQL server licenses need to be purchased, so this scenario is perfect when there is already SQL server in the environment.
Considerations for placing QMM for Ex database onMSDE instance:
PROs:
- MSDE is free product.
- MSDE entirely based on SQL 2000 Server code with just few limitations that still meet QMM DB requirements.
CONs:
- Setup is not easy and not obvious, often during setup admins are confronted with the issue that the sa account password cannot be blank, they find a workaround and change/populate this password and forget about it. Later, should an issue arise, the password is not readily available and cannot be retrieved easily (unless it was saved in a txt file as precaution).
- Usually MSDE is deployed directly on the QMM console and left as it is, without regular backup being performed. In a disaster scenario, e.g. QMM console machine crashed, the SQL DB is then lost as well.
- Unless special SQL ManagementTools have been downloaded and installed, there is no access to MSDE databse via GUI and such things like maintenance, DB analyzing or switching to Windows authentication cannot be performed as easy as with a regular SQL instance.