Sorry, I don't have a Unity in front of me. But what you do is go into Windows Services. You can stop Unity from the Tray (righ click and stop.) Then go into Services. Look for all the AV services and manually stop those. Unity will finally shut itself down, and essentially stop using SQL, IIS, etc. Once all the Unity Services are stop in Windows
This is done as a precautionary step. This will allow us to have a good backup of the database up to the time of the move. (I actually do this before I make any changes to a database; you can never have too many backups!)
1. Open Enterprise Manager, and navigate to databases.
2. Right-click the database being backed up, select 'All Tasks' and then click 'Backup Database…'.
3. Verify and make note of database name and the backup destination path. I usually change the destination path to 'd:\temp\dbname.bak'. It isn't necessary to change it, but ensure you can find it if you need it.
4. Under the 'Overwrite' section, select 'Overwrite existing media'.
5. On the 'Options' tab, put a check next to 'Verify backup upon completion'.
6. Click 'OK'.
Detach the Database
1. Right-click the database, select 'All Tasks', and then click 'Detach Database…'.
2. At this point the current number of connections to the database will be displayed. If there are any connections, they must be cleared before the database can be detached. Click 'Clear'. You will then be prompted with 'This will end all active transactions in this database which is required before the database can be detached. Is it OK to proceed?' Click 'OK'. The next prompt is regarding notifying users. It will ask 'Do you want to notify the currently connected users that their sessions in the database will be ended?' I always click 'No' for web applications. And then click 'OK' to detach the database.
3. At this point the database is detached (it will not appear in Enterprise Manager).
Next, you'll need to copy the data file (.mdf) and transaction log (.ldf) file to the new server. By default, SQL server will create databases and put these files in the same directory (it's usually \Program Files\Microsoft SQL Server\MSSQL\Data). However, for performance gains, this may be changed so the transaction log file is put on another hard drive. Be sure to check the new SQL server to see how it is setup. If the transaction log files are setup on a different hard drive, it should be copied there and the data file should be put in its appropriate directory. And, when attaching the database, be sure the paths to the files are correct.
Attaching the Database
1. Right-click the database, select 'All Tasks', and then click 'Attach Database…'.
2. Navigate to the data file by clicking the button that has 3 dots on it (…).
3. Once you've selected the database .mdf file, you'll see the data file path (which should be verified for both the data and transaction log file) and have the option to choose the database name and owner. Attach it as the database name, and ensure the owner name is 'sa'.
4. Verify the path for the transaction log file is correct. If the path isn’t correct, update it to the appropriate directory.
5. Click ‘OK’.
Note: If you didn't move the transaction log file to the new server with the data file, you'll be prompted to create a new one. If you choose to create a new one, it will be done for you automatically.
hope this helps. Try it with a test database like the northwinds one or create a test database in SQL. SQL looks scary, but it's actually pretty easy to do this stuff
