Database - I am moving or renaming my db; what do I need to know?

×

Only Renaming Database

  1. Ensure all users are out of Macola.
  2. Stop Job Master on the database server and wait for the jobs to clear.
  3. Edit BirdDogSoftware.JobMaster.exe.config in the Job Master folder and update the database name="new database name"  entry.
  4. Stop any local websites using that database.
  5. Edit the Birddog.config in the local web site folder and update the entry.
  6. Restart the web site and test.
  7. Restart Job Master and check logging to ensure there are no issues.

  

Moving Database to New Database Server and/or Renaming Database

  1. Ensure all users are out of Macola.
  2. Stop Job Master on the database server and wait for the jobs to clear.
  3. Stop any local websites using that database.
  4. Detach or backup the databases on the old server. 
  5. Move the database to the new server and restore or reattach.
  6. Ensure permissions on the databases are set correctly.
  7. Install Job Master on the new database server.
  8. Edit BirdDogSoftware.JobMaster.exe.config in the Job Master folder and update it with the new database information.
  9. Edit the Birddog.config in the local web site folder and update it with the new database information. (click here for instructions)
  10. Start the local websites up and correct any issues.
  11. Start Job Master up and check logging for any issues.

Note 1. If you are moving the database by backing them up, it is recommended that once you have backed them up to put them in read only mode so no one can accidently utilize them.

 

   Macola ES Instructions

How should Macola ES be moved from one server to another?

Revision Date: 12/14/2010
Module:
Version: Macola ES

Description: How should Macola ES be moved from one server to another?

Solution:
  1. Backup all Macola ES databases.
  2. Install ES on the new server using the ProductUpdater_T6_AE.exe.
    For installation instructions and to download the Product_T6_AE.exe from your Exact Customer Portal, go to Macola ES Support Center, Reference Library, Macola ES Release Notes, click on the applicable version of ES, and go to the Update Information section. Click on the link to the Installation instructions. There is a link to the Macola ES Product Updater near the bottom of the Installation instructions screen.
  3.  Restore all Macola ES databases to the new SQL server.
  4. Within SQL Enterprise Manager/SQL Management Studio add the domain users to Security, Logins.
  5. At each workstation browse to the ES Network Installation folder on the new server and run Wsetup.exe.
  6. Open Macola ES and create an empty or demo company per document 21.573.386 to create the MSLLOCKDB database.
  7. Remove and recreate the Macola ES Crystal User (ESCRWUser) per document 17.427.722.
Attachments: None

Key Words: move migrate ES new different server

Additional Resource:
Additional knowledgebase documentation - Knowledgebase
FREE on-demand training - Document: 10.040.533 - Americas Training Start Page

 
  Macola Progression Instructions    

New Progression SQL server - same Progression application server

Revision Date:02/10/2012

Module:  System

Version: Progression 7.7.6xx

Description: Replacing the old SQL Server and moving Progression databases to it. The application server will remain unchanged.The following outline is necessary to properly move the databases and properly configure the application server to see the new SQL Server.

SolutionStep1:  The following list of instructions will need to be followed for the New SQL server:

1. Install Microsoft SQL server as the default option, not an instance, using mixed mode authentication.

Beginning withProgression 7.7.600, this version of Progression software will run on the Microsoft SQL 2008r2 server platform.Earlier versions of Progression software will need to be updated before moving to this platform.

Please Note: log on to the network as the "Domain Administrator".

Prerequisite:For SQL 2008r2 you will need to install the SQL backward compatibility components (SQL-DMO part) on the server and client side to run Visual Menu Builder and the Progression Setup Utility.  
 
Please Note:Because of the technical nature of the prerequisite the compatibility components should be completed by a qualified SQL server IT person or Exact Business Partner. Exact can recommend an Exact consultant to help as well. Please contact your Exact account manager. 
 
The MSI is located athttp://www.microsoft.com/downloads/en/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en

If the Server and workstation is 32 bit, use X86 Package (SQLServer2005_BC.msi) - 11273 KB

If the Server and workstation is 64 bit, use the X64 Package (SQLServer2005_BC.msi) - 18569 KB

 

 
2. Loginto Progression as the SUPERVISOR, and change the Progression Supervisor's password to "SUPERVISOR" on the current SQL server. Log back into into Progression as SUPERVISOR to verify the change has taken place. 

3. From the old SQL server, detach the SCREENS, PWE, MSLLOCKDB, and all Progression DATA databases.

4. Copy the SCREENS, PWE, MSLLOCKDB, and all Progression DATA databases to the new SQL server and attach them.

5. Start Management Studio, File, Open, File, navigate to the Progression installation folder (ie: Macsql), open the SQLScript folder and select the msl_locking.sql script. Change the dropdown arrow on the toolbar from MASTER to MSLLOCKDB and execute the SQL script.

6. From Management Studio, New Query, execute the following against ALL Progression databases:
    (SCREENS, PWE, MSLOCKDB, and all Progression DATA databases)

   sp_dropuser supervisor_sql

   sp_dropalias supervisor_sql 

7. From Management Studio, File, Open, File, navigate to the Progression installation folder (ie: Macsql), open the SQLScript folder and select the User7.sql script. Change the dropdown arrow on the toolbar to MASTER and execute the SQL script.  

8. From Management Studio, Security, Logins, right click on SUPERVISOR_SQL,select Properties. Then select User Mapping, select each Progression databases as well as Public and  DB_OWNER Database role membership for: window.

  9.

9.Since this was not a new Progression install there are several SQL Stored Procedures that will not be present and are needed for Progression to operate. Using the attached file (SQL 2008 Progression Stored Procedures.txt) to create the stored procedures, copy the text file to the New server. Open Management Studio, File, Open, File and navigate to where you placed this file on the server, copy and paste into New Query. Execute each SQL script against MASTER.

10. Once the SQL scripts have run, check that the scripts actually created. From Management Studio navigate to Databases, System Databases, Master, Programmability, Stored Procedures. Four Stored Procedures should be shown as...

 dbo.sp_MacMSSLockEraser

 dbo.sp_MSLGetLCID8

 dbo.sp_MSLGetSQLVer

 dbo.sp_MSLOpenTableEraser

SolutionStep 2:  The following list of instructions will need to be followed for the existing Application server:

1. From the Progression installation folder (Macsql) edit the file MACSQL.cfg changing each line SERVER= to designate the New SQL server name.    

[SQL_INFO]

Companies_Installed=2

[Company_005]

Name=Johnnies Bakery

Server=

Database=Data_005

LOCKDB=MsllockDB

FRL=False

[Company_100]

Name=Bobbies Bakery

Server=

Database=Data_100

LOCKDB=MsllockDB

FRL=False

[ENGLISH]

Server=

Database=SCREENS

LockDB=msllockdb

2. From the Progression installation folder (Macsql) navigate to the PWE folder. Locate the PWE.tam file, uncheck read-only, then edit the file to specify the new server name.

[DbInfo]
Server=New SQL servername
Database=PWE
[WebPages]
Support-Name=Search the &Web (Google)
Support-Address=http://www.google.com
Misc-Name=Macola &Home Page
Misc-Address=http://www.macola.com
Misc2-Name=&Exact Software Home Page
Misc2-Address=http://www.exact.nl/custom/PubWebStart.asp?Language=1

3. Log into Progression as Supervisor and open System Manager, Maintain, Visual Menu Builder. From the Visual Menu Builder toolbar select, Tools, Synchronize With SQL...

SolutionStep 3:  The following list of instructions will need to be followed for each of the client workstations as well as the SQL server:

Select Start, Run and type cliconfg, then select OK.



Select a protocol to enable\disable from the right hand side of the screen Enabled protocols by order.

Please Note:If selecting Named Pipes, also select the Alias tab and remove the Alias before saving any changes. You will need to confirm the Named Pipes protocol is enabled on the SQL server.  

Attachments:SQL 2008 Progression Stored Procedures.txt

Key Words:Progression SQL server, application server, SQL server

Additional Resources:
Additional Knowledgebase documentation -Knowledgebase
FREE on-demand training - Americas Training Start Page