Emerson Exchange 365

• Not Answered

MS SQL upgrade

I am upgrading our DeltaV and one of the items in Read before you start is this:

When upgrading from DeltaV v12.2 or before, Microsoft SQL is upgraded to SQL 2012. To perform this upgrade, the services SQL Server (MSSQL) and SQL Server Agent (SQLAGENT) must have the 'Log on as' option set to Local System account. Any other setting causes the upgrade of Microsoft SQL to not complete successfully. To verify this setting, open Administrative Tools | Services. Right click the service name and select Properties. On the Log On tab, verify that the 'Log on as' option is set to Local System account.

But when I checked my Services, I found out this:

Which of the SQL Server item above is the one referring in Read Before You Start?

Do I need to change the account name under the "Log on as" for all the SQL Server to Local System?

And lastly, do I have to do this before or after the upgrade?

Thanks for answering.

Rein

• 31 Oct 2018 12:33 PM
• Cancel

3 Replies

• Tim Alexander

  

  • 1 Nov 2018 4:40 AM

  The SQL Servers can run as Local System.
  
  This account is defaulty a member of the Local Windows Administrator group all of which have the system admin role in the SQL servers.
  
  The DeltaVAdmin Account is also in that Group so it can do everything it needs to with the database.
  
  DELTAV_ADV_CONTROL is used for insight, predict, predictpro
  
  DELTAV_CHRONICLE is your Event Chronicle
  
  Emerson2005 is the AMS Server Plus database

  • Cancel
• Rein

  

  • 1 Nov 2018 7:43 PM

  In reply to Tim Alexander:

  Thanks Tim.
  However, I went ahead with the Upgrade and while in the process of extracting some SQL file under installing the DeltaV SQL 2012 , I encountered an error that says, "Extraction Failed (Data Error-Cyclic Redundancy Check) as "DeltaV Chronicle Install Failed".
  I tried to reboot the machine and rerun again Disk1, and the outcome is the same.
  Could someone tell me what should be done to resolve this issue?
  Thanks again for responding.

  • Cancel
• Tim Alexander

  

  • 2 Nov 2018 1:03 AM

  In reply to Rein:

  That would be worth checking with GSC on the workaround.
  
  What I think is happening is that during the version upgrade of the SQL data it encountered corruption in the database. Some work would have to be done using manual commands to repair that data.
  
  However i dont know how DUW can recover from where it left off. I have never used it and prefer doing upgrades manually.

  • Cancel