---
title: Database Migration (DK) - Sync
description: null
tags:
  - "2026"
  - "project"
  - "dk"
peopleInvolved: null
type_: null
date: 2025-12-03T13:00:00.000Z -> 2025-12-03T13:30:00.000Z
dnb: dk
status: Done
type: Meeting
---

# Database Migration (DK) - Sync

event:: Database Migration (DK) - Sync
Description: Microsoft Teams Meeting
Attendees:
- Paweł Domański (pawel.domanski@outlook.com)


### Notes

# Mötesanteckningar

### Data flow and replication

- Andrey explained that the current data flow involves daily database replication using a stored procedure in the master database, which caused issues when moving to the test environment.

- Andrey identified how the application reads data from the database and proposed eliminating the need for database replication, but emphasized that thorough testing is still required before making changes.

### Migration blockers

- Paweł agreed to help Andrey recreate the stored procedure in the test environment, but mentioned that it is a blocker for the upcoming migration.

- Paweł stated that the server is not ready and lacks necessary system information, which is another blocker for migration.

- Paweł stated they need additional time to configure and review the procedures related to the database setup.

- Andrey explained that the lack of documentation and internal knowledge is making the application testing and migration process more challenging

### Migration planning

- Andrey indicated that migration will not happen next week due to these obstacles and suggested removing the need for database replication by consolidating to a single database server.

- Naser proposed setting January 31st as the target date for completing application testing and migration, with flexibility to finish earlier if possible

### Data preparation

- Andrey stated they are progressing with data manipulation scripts and will spend this and next week setting up and deploying them as a Kubernetes job

### Testing requirements

- Andrey emphasized the need for thorough application testing to ensure all functionality works correctly after the database changes

# Uppföljningsuppgifter

| Uppgift                                                                                                                                       | Tilldelats till | Förfallodatum | Hink |
| :-------------------------------------------------------------------------------------------------------------------------------------------- | :-------------- | :------------ | :--- |
| Test the application with the new database setup to confirm it reads data correctly and safely before removing replication (Andrey)           |                 |               |      |
| Set a preliminary migration date for the end of January, with the final date to be confirmed after testing is complete (Naser, Andrey, Paweł) |                 |               |      |
| Request firewall opening for the server to enable database access for applications (Andrey)                                                   |                 |               |      |