97 Data Migration Guide Between Different Databases

1. Open SQL Server Management Studio (SSMS).
   
2. Connect to the source instance.
   
3. Expand Databases, right-click the database to be copied → Tasks → Back Up…
   
4. Configure the backup:
   
   • Backup type: Full
     
   • Backup to: Local or shared disk location
     
5. Start the backup by clicking OK.
   CreateTheBackup

1. Locate the newly generated .bak file. If you're unsure where to look, right click on the SQL Server Instance → Properties → Database Settings
2. Copy it to the machine hosting the destination SQL Server instance, in a location accessible by SQL Server.
   CopyingBKP

1.3 Restsore the database on the target instance

1. Connect to the target instance in SSMS.
   
2. Right-click Databases → Restore Database…
   
3. Configure the restore:
   
   • Source: Device → select the .bak file
     
4. Under Files, verify the paths of the MDF and LDF files and adjust if necessary.
5. In the Options page, check the option "Overwrite the existing database (WITH REPLACE)".
6. Click OK to start the restore.
   Example > RestoreTheBackup

• Ensure the database is accessible and intact.
  
• Verify users and access permissions.

It is important to also check if the Service Broker is enabled and the Trustworthy status of the DB. To do so, execute the following query on the DB:

SELECT IS_BROKER_ENABLED, IS_TRUSTWORTHY_ON FROM SYS.DATABASES WHERE NAME = '[DB NAME WITHOUT SQUARE BRACKETS]'

If the result/s displayed are 0, it means that the broker is not enabled and/or trustworthy is off

To activate a new service broker, execute the following query on the DB:

ALTER DATABASE [DB NAME WITHOUT SQUARE BRACKETS] SET NEW_BROKER WITH ROLLBACK IMMEDIATE

To set trustworthy status to "On", execute the following query on the DB:

ALTER DATABASE [DB NAME WITHOUT SQUARE BRACKETS] SET TRUSTWORTHY ON

Once the new instance has been tested, proceed with the configuration of ETERE to maintain playlist and asset data consistency.
       PostRecoveryChecks

• Both databases (A and B) must initially be cloned and identical.
  
• On DB A, a workflow called AFTER AN ASSET UPDATE must be active and set as default for each asset modification. This workflow triggers whenever an asset is new or its metadata/fleximetadata is modified.
  
• On both databases, a FLEXI called DELIVERY must be created to perform necessary checks.
  WfAfterAssetUpdated
  DeliveryFlexi

Case 1: Creation of a new Asset

1. User creates an asset on DB A.
   
2. The workflow AFTER AN ASSET UPDATE is automatically activated.
   
3. Workflow copies the associated video file.
   
4. Workflow generates an XML file containing all asset information.
   
5. Both files (XML + video) are saved in a shared watch folder accessible by both sites.
   
6. On DB B, Active Sync scans the folder every 5 minutes:
   
   • Detects the XML and video files.
     
   • Performs asset creation using the same CODE and flexi, placing the video as configured by the workflow.

Case 2: Modification of FlexiMetadata Only

1. User modifies one or more fleximetadata fields in DB A.
   
2. The workflow AFTER AN ASSET UPDATE detects changes and triggers.
   
3. Workflow generates an XML file with updated information, without copying the unchanged video file.
   
4. XML is copied to the shared watch folder.
   
5. On DB B, F90 continuously scans the watch folder every 5 minutes:
   
   • Detects XML file.
     
   • Updates the corresponding asset (based on the same code) in DB B.

Case 3: Modification of FlexiMetadata + Metadata

1. User modifies an asset in DB A, updating both fleximetadata and hires metadata.
   
2. The workflow AFTER AN ASSET UPDATE detects changes on both fronts.
   
3. Workflow generates an XML file and copies the updated video to the watch folder.
   
4. On DB B, Active Sync:
   
   • Detects new files.
     
   • Updates metadata, flexi, and video as required, keeping assets synchronized.

Technical Notes:

• The watch folder must be accessible for writing from DB A and reading from DB B.
  
• F90 and AS modules must be correctly configured to export XML and handle video files.
  
• XML structure must comply with the import model used by F90 and Active Sync.

Step 1 – Export from Source Site

1. Each time changes occur in EE (Executive Editor) on DB A, an XML file is generated containing updated playlist data for the modified day.
   
2. Use EXPORT → STANDARD → GENERIC → XML in Etere to generate the XML.
   
3. Save the XML to a shared folder accessible to both source and target databases, with read/write permissions for all involved services.
   

Step 2 – Import into Destination Site

1. Configure import on DB B using IMPORT → STANDARD → GENERIC → XML via F90.
   
2. F90 continuously scans the shared watch folder for new XML files.
   
3. When a new XML file is detected, F90 imports the data into DB B, updating the relevant playlists.
   
4. After import, the system automatically notifies the operator to update playlists in EE using:
   
   • F4: update duration
     
   • F6: update duration + secondary events
     
   • F8: explode assets from correct EDL
     
5. Create a WF AFTER PLAYLIST IMPORTED to control and notify the operator to update EE media, preventing OnAir issues.
   WfAfterPlaylistImported