Installing SQL Server Retail to Replace Expired Trial Version

 01/22/2007

As from 12/17/2006 the trial version of SQL Server 2005 expired (somebody had an issue with maths) we need to switch from the trial to the retail version.

Here is a procedure out of my mind following the similar incident we got with Vmware Virtual Center.

The data is located here: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data but the files are locked as the services are still running.

From here 2 options:

  1. create another SQL server following the current procedure from Roger (I suggest it to have the same name and IP to not confuse the system)
  2. deinstall and reinstall SQL server on the same server

Option 1:

  • install W2k3 R2 SP1 and run a Microsoft Update to have the operating system ready. Use a different name and IP for installing purposes. Use a RAID1 hard drive configuration for safety
  • install SQL server 2005 following Roger's procedure
  • install SQL server SP1
  • restart former Liberi and only after make a backup of the C:\Program Files\Microsoft SQL Server\MSSQL.1 directory which contains the softricity.mdf database and log files associated (if you make a backup before the restart, the services are still running and are locking the database)
  • when the backup is done (279Mb), shutdown former Liberi
  • run the dsa.msc management console on the domain, right click on the Liberi server and click "reset", this will allow to keep the name in the proper OU
  • go on the new Liberi then change its name to "Liberi" then restart
  • after the restart, join the server to the domain using administrator credentials (your sys account)
  • restart the server
  • make sure you are logging into the gccaz domain using your sys account
  • restore the backup in its default location C:\Program Files\Microsoft SQL Server\MSSQL.1
  • go to "Microsoft SQL Server Management Studio"
  • go to "Databases" and right click on it
  • select "Attach" then select the database location C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data and select softricity.mdf
  • in "Databases" you should see Softricity now
  • restart the server
  • make a test, you should be done

Option 2:

  • update the server with Windows Update
  • restart the server
  • upon restart the SQL services won't start as the trial version has expired
  • make a backup of the C:\Program Files\Microsoft SQL Server\MSSQL.1 directory which contains the softricity.mdf database and log files associated (if you make a backup before the restart, the services are still running and are locking the database)
  • go to Control Panel then click on add/remove program
  • select Microsoft Sql server 2005
  • select other components if any
  • restart the server and log into the gccaz domain
  • install SQL server 2005 retail version following Roger's documentation
  • install SP1
  • restore the backup in its default location C:\Program Files\Microsoft SQL Server\MSSQL.1
  • if you get a message "cannot copy files because it is being locked", continue (actually we just need the softricity.* in the \Data directory)
  • go to "Microsoft SQL Server Management Studio"
  • go to "Databases" and right click on it
  • select "Attach" then select the database location C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data and select softricity.mdf
  • in "Databases" you should see Softricity now
  • restart the server
  • make a test, you should be done
    As we decided to go with Option 1, I set up a new SQL server (following Roger's documentation) called Liberi2 with the IP 10.1.50.26

 01/23/2007

According to this link, it is possible to move or copy the database from one server to another using the wizard without service interuption (in theorie). However, we still have the following steps to do to accomplish the task:

  • copy the database from Liberi to Liberi2 using the copy database wizard
  • stop the SoftGrid Virtual Application Server service on Marozzo to avoid applications to be served from Softricity (1.    From the SoftGrid Virtual Application Server, launch Services from Administrative Tools
    2.    Stop the SoftGrid Virtual Application Server service)
  • reconfiguring the SoftGrid communication configuration files (SoftGrid Virtual Application Server from sg1, sg2 and sg3, rename the liberi2server.conf to server.conf)
    1.    From the SoftGrid Virtual Application Server, explore to C:\Program Files\Softricity[SoftGrid] Server\conf
    2.    Edit server.conf with a text editor
    3.    Change the host name between <location> and </location> to the target SQL Server host name
    4.    Save the change and exit)
  • SoftGrid Management Server (if installed)
    1.    From the SoftGrid Management Server, explore to C:\Program Files\SoftricitySoftGrid Server\conf
    2.    Edit manager.conf with a text editor
    3.    Change the host name between <location> and </location> to the target SQL Server host name
    4.    Save the change and exit
  • SoftGrid Management Web Service (on sg1 and sg2 only)
    1.    From the SoftGrid Management Web Service server, explore to C:\Program Files\Softricity[SoftGrid] Management Service
    2.    Go to the Properties of [SftMgmt].udl
    3.    Go to the Connection tab
    4.    For Select or enter a server name, enter the name of the target SQL Server and select OK
    1.    From the SoftGrid Management Web Service server, launch Data Sources (ODBC) from Administrative Tools
    2.    Go to the System DSN tab
    3.    Configure the [SoftGridReporting] System Data Source
    4.    For Server enter the target SQL Server host name
    5.    Select Finish
    6.    For ODBC Microsoft SQL Server Setup select OK
    7.    Select OK again
  • Resetting the SoftGrid Management Web Service (on sg1, sg2 and sg3)
    1.    From the SoftGrid Management Web Service server, launch Services from Administrative Tools
    2.    Stop and Start the World Wide Web Publishing Service
  • Reconfiguring the database logging (on sg1 only)
    1.    Launch the SoftGrid Management Console and connect to the SoftGrid Management Web Service
    2.    Expand SoftGrid Systems >
    Unknown macro: {server_name}

    > Server Groups
    3.    Go to the Properties for the Default Server Group
    4.    Go to the Logging tab
    5.    Edit the existing SQL Database Type
    6.    Change the DNS Host Name to the target SQL Server host name
    7.    Select OK then select OK again
    8.    For "You must restart the SoftGrid Virtual Application Server services in this group for them to reflect the changes made" select OK

  • SoftGrid Virtual Application Server (sg1, sg2 and sg3)
    1.    Reboot the SoftGrid Virtual Application Server
    SoftGrid Management Server
    Note: If the SoftGrid Management Server is the same server as the SoftGrid Virtual Application Server that was previously rebooted, this step can be skipped.
    1.    From the SoftGrid Management Server, launch Services from Administrative Tools
    2.    Stop and Start the following services:
    o    SNMP Brass Management Multiplexer Agent
    o    SNMP EMANATE Master Agent
    o    SoftGrid Management Server
    o    SoftGrid SNMP Monitor

This procedure (option2) should work also for Arcserve as far as the default database is not part of the default setting (uninstalling will then remove the database).

02/06/2007  -- rlb
Adding to the above procedure/checklist. Combine the SQL installation documentation, and SQL DB migration from one server to another from MS and from Softricity.  * RDP into Liberi2, Run MS SQL Server Management Studio, connect to both L1 and L2 using the SA account (password documented in secret).

    • Find and detach the Softricity database.
    • Copy the Softricity database files from L1 to L2.
      Data file is SOFTRICITY.mdf,
      log file is SOFTRICITY_log.LDF
      • In L1 they are both located in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data.
      • Place them in L2 in separate locations to make more accessible.
        Data in C:\datafiles
        Log in C:\logfiles
      • Or use the copy database wizard however it will place files in the same directories.
  • Verify the roles and users on L2 match L1
    • From the MS SQL Server Management Studio, go to the security folder of the SOFTRICITY database, then roles, database roles. The following roles should have these users as members  
      role:SFTadmin, users:softgrid, "gccaz\softgrid admins"
      role: SFTuser, user:softgrid
      role: SFTeverone, will have all the other roles and all the users, users: softgrid, "gccaz\softgrid admins", SFTadmin, SFTuser, SFTview
      role:SFTview has no direct members.
    •  
  • RDP into each server and do the following on each SG1, SG2 & SG3 (marozzo, maniocilino, tigger), SG3 will have less.
  • Stop the SoftGrid Virtual Application Server service to avoid applications to be served from Softricity
    • launch Services from Administrative Tools
    • Stop the SoftGrid Virtual Application Server service
  • Reconfigure the SoftGrid communication configuration files
    • Explore to C:\Program Files\Softricity[SoftGrid] Server\conf
    • Copy server.conf to serverold.conf
    • copy the liberi2server.conf file to server.conf
      All this changes is the host name between <location> and </location> to the target SQL Server host name
  • Management Web Service (on sg1 and sg2 only)
    • From the server, explore to C:\Program Files\Softricity[SoftGrid] Management Service
    • Go to the Properties of [SftMgmt].udl
    • Go to the Connection tab
    • For Select or enter a server name, enter the name of the target SQL Server [Liberi2] and select OK
  • Management Web Service ODBC connection (on sg1 and sg2 only)
    • From the server, launch Data Sources (ODBC) from Administrative Tools
    • Go to the System DSN tab
    • Configure the [SoftGridReporting] System Data Source
    • For Server enter the target SQL Server host name [Liberi2]
    • Select Finish
    • For ODBC Microsoft SQL Server Setup select OK
    • Select OK again
  • Resetting the SoftGrid Management Web Service (on sg1, sg2 and sg3)
    • From the server, launch Services from Administrative Tools
    • Stop and Start the World Wide Web Publishing Service
  • Reconfiguring the database logging (on sg1 only)
    • Launch the SoftGrid Management Console and connect to the SoftGrid Management Web Service
    • Expand SoftGrid Systems Server Groups
    • Go to the Properties for the Default Server Group
    • Go to the Logging tab
    • Edit the existing SQL Database Type
    • Change the DNS Host Name to the target SQL Server host name [Liberi2]
    • Select OK then select OK again
    • For "You must restart the SoftGrid Virtual Application Server services in this group for them to reflect the changes made" select OK
  • Reboot the SoftGrid Virtual Application Server (sg1, sg2 and sg3)
    • Reboot the SoftGrid Virtual Application Server and the SoftGrid Management Server [these are all the same SG1, 2, & 3]
  • Test the application delivery from a workstation with a clean cache.
    • A56standA and B are still active (2/6/02)  refresh the cache first.

Later

  • Establish and setup maintenance schedules, backups and alerts in Liberi2
    • Some of this is already begun but will need to be redone when finished with the above steps.
    • Suggest a nightly backup which provides an offline copy of the database for arcserve to backup.  Suggest either using an expiring backup or an overwrite backup.
    • Alerts for several volume space capacity levels.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.