It is not a SafeCom problem if the person installing SafeCom accidently chose to install the SQL database on the wrong partition. But in case e.g. the database has outgrown the drive, and needs to be moved to another drive, the following process can be used. This process it not to be used if the SafeCom server or SQL database is clustered.
P.S. As this is a change in the SQL Management studio, a database can only be moved to a drive that is seen as local to the SQL Management studio. It is advisable to have the encrypted password for the safecom sql user owning the 4 SafeCom databases. If Windows authentication is used instead of SafeCom authentication, then the login and password for the Windows user currently being used to run the SafeCom service on the master server, needs to be known.
As the physical files are moved to a new location, then you need to ensure that the Windows accounts with permissions to the folder currently holding the SafeCom database files (scccore.mdf, sccore.ldf, scevent.mdf, scevent.ldf, scpurse.mdf, scevent.ldf, sctrackingw.mdf, sctrackingw.ldf) is granted the same permissions on the new folder.
1. Use SQL Mangement Studio to take a full backup of the 4 SafeCom databases, sccore, scevent, scpurse, sctracking.
2. The SafeCom database files (scccore.mdf, sccore.ldf, scevent.mdf, scevent.ldf, scpurse.mdf, scevent.ldf, sctrackingw.mdf, sctrackingw.ldf) needs to be located on the Sql server. Default file location is often:
C:\Program Files\Microsoft SQL Server\MSSQL10_50.SAFECOMEXPRESS\MSSQL\DATA (if Sqlexpress) or
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA (if full blown SQL)
When found, then take properties for the folder. Note down the rights as seen in the Security tab.
3. Stop the SafeCom service and the print spooler service on the master server. If the server is also running other SafeCom services, then stop those also.
4. Start up Microsoft SQL Management studio, and connect to the sql database. It is recommended to be logged in as the safecom sql user (or if the installation is running with windows authentication, be logged in as the windows user setup to run the SafeCom service)
5. In SQL management studio, one by one, right click the 4 safecom databases (sccore, scevent, scpurse, sctracking) and chose Tasks, Take Offline (close the confirmation box)
6. In SQL management studio, one by one, right click the 4 safecom databases (sccore, scevent, scpurse, sctracking) and chose Tasks, Detach (Tick the “Drop connections” box, and hit OK.)
7. Now it is time to move the physical files to the new folder. Remember that the folder must be on a drive that is visible from Sql Management studio. This means that the drive used must be seen as a local drive. Network drives can not be used.
8. After moving the SafeCom database files to the new location, make sure that the folder holding the SafeCom files are assigned same rights as the old folder has. See step 2.
9. In SQL Mangement studio, (still logged in as the same user), right click “Databases” and choose “Attach”
Click the Add button, and browse to the folder you copied the 8 SafeCom database files to.
Highlight the sccore.mdf file and hit the OK button.
Click the OK button to add in the database.
10. Repeat step 9 and one by one add in the scevent.mdf, scpurse.mdf and sctrackingw.mdf database.
11. One by one, rightclick the added SafeCom databases and take properties. In the General tab, verify that the correct user is listed as owner for the database.
12. If the safecom sql user was intended to be the owner of the databases, but that is not the case, then you can run the sql script scChangeOwner.sql as a querry in SQL management studio. The file is found in the Safecom installation folder.
13. Close the SQL Management Studio. On the Master server start the SafeCom service, the Print spooler service, and eventual other services you closed down in step. 3
14. Open up SafeCom Administrator, and verify that you can login to the SafeCom Database.