Moving Database and Log Files

After installing the Plant Applications Server, you can move the Plant Applications or Unified Manufacturing Database (UMDB) database file and log file to a separate physical disk to optimize performance.

About this task

The physical disk should be part of the disk subsystem,
Note:
  • For more information on optimizing SQL Server performance, contact Support at Support.
  • If upgrading SQL Server to a newer version, run sp_revokeDBAccess for ProficyDBO, ComxClient, and ProficyConnect. Next, run spSupport_ChangeDBOAccount to reconfigure the SQL User Accounts.

An SQL Server database consists of MDF (database file) and LDF (log file) files. By default, these two files are located in the following directory:

C:\Program Files\Microsoft SQL Server\MSSQL\Data

Procedure

  1. Locate the MDF and LDF files.
    1. Start SQL Server Management Studio from the Windows Start menu.
    2. Navigate to the database, right-click it, then select Properties to display the Database Properties dialog box.
    3. Under Select a page, right-click Files to view the location of the MDF and LDF files.
  2. Stop the following Plant Applications Server services:
    • Proficy Server Manager
    • Proficy Server Router
    • Proficy Server License Manager
  3. Stop the Proficy Server, Proficy Publisher, and Proficy STS Services used for SOA.
  4. In SQL Server Management Studio, take the database offline.
    1. Select Plant Applications SQL Server, then select Databases.
    2. Right-click the Plant Applications database, select Tasks, and then select Take Offline.
  5. Detach the database (refer to SQL Server documentation).
  6. Copy the MDF and LDF files to the SQL Server instance.
  7. Attach the database to the SQL Server instance.
  8. Bring the database online, then verify the location of the MDF and LDF files.
  9. Restart the Plant Applications Server and SOA services.
  10. After the database has been restored, verify that permissions are set up correctly in the Plant Applications database. From SQL Server Management Studio, run the following script to rebuild the SQL permissions:
    exec sp_Revokedbaccess 'ProficyDBO'Plant Applications
go
exec sp_Revokedbaccess 'ComXClient'
go
exec sp_Revokedbaccess 'ProficyConnect'
go
exec SpSupport_ChangeDBOAccount 'Proficydbo','ProficyDBO'