01
Requirements and plan
We review versions, integrations, workload and licences. We agree the scope, maintenance window, acceptable data loss and recovery time: the RPO and RTO objectives.
Database infrastructure
Database deployment and migration
We deploy Microsoft SQL Server, MySQL, MariaDB and PostgreSQL. We configure access, backups and monitoring, migrate agreed data and test the application. Before work starts, we agree the tests, cutover conditions and responsibilities for ongoing support.
Trusted by
Companies and institutions that need stable IT.
The right database for your application
We start with application requirements, engine version, data volume and workload. We select resources, licensing and a recovery approach. Projects can cover a new instance, an upgrade or migration to an on-premises or cloud environment. We assess Redis and MongoDB against the data model and queries; support for other NoSQL databases is confirmed separately.
Action plan The right database for your application
Services supporting your database
A database needs resources, data protection and support after launch. We agree the scope of this work and responsibilities with your application team.
Server platform
Resources and virtual machines sized for workload, data growth and availability needs.System administration
Operating system setup, service accounts, encrypted connections and updates. Applications receive only necessary permissions; administrators use individual accounts.Backup and recovery
Backup schedules and protection, including copies outside the source environment, with database restore tests.IT monitoring
Availability, backups, replication and resource checks, with people assigned to respond to alerts.ISO 27001 · TÜV NORD Polska
TÜV NORD Polska has certified Virtline’s information security management system to PN-EN ISO/IEC 27001:2023-08. The published certificate states its scope and validity.
View Virtline’s certificateDatabase implementation process
We plan the work with the application owner and administrator. A rehearsal on a copy comes before the production change.
02
Setup and rehearsal
We prepare the instance, access, backups and monitoring. We test migration on a copy, check application compatibility and measure the time needed to move the data.
03
Cutover
We agree when to stop writes, complete final synchronisation and roll back if needed. After changing connections, we check data and application behaviour; the designated person approves the next step.
04
Acceptance and handover
We review test results, documentation and exceptions. We agree post-launch observation, reviews and responsibilities for ongoing support.
Practical scope
What you receive at handover
We assess results against agreed criteria and record limitations and any work still required.
A record of instances, resources, roles and application accounts. We document settings, connections, secure storage of passwords and access keys, and logging of access and changes. Replication is covered where it is included in the project.
A record of migrated data, consistency checks, and tests of reads, writes, reports and integrations. Measurements of critical queries allow comparison before and after the change.
Backup configuration, the result of a restore test and the time it took. If the project includes SQL Server Always On Availability Groups, MySQL Group Replication or PostgreSQL streaming replication, we also test failover and application behaviour.
Documentation for monitoring, updates, incident response and capacity planning. We identify responsible people, open risks and the scope of future reviews.
Rollback needs a plan
Keeping the old server does not resolve what happens to data written after cutover. Before the change, we agree when a return is possible, how to stop writes and how to handle new data. We plan backup restoration separately: replication and high availability do not replace backups.
Database deployment questions
Can you migrate between versions and platforms?
+
Yes, after checking application, driver and feature compatibility. We select a migration method, rehearse on a copy and measure the time required. Changing the database engine needs a separate assessment; application changes may be necessary.
How do you plan database backups?
+
We consider the engine, change volume, retention period and agreed RPO/RTO objectives. The scope may include full or differential backups, transaction logs, WAL archiving or logical backups. We check that the backups can be used by restoring them.
Can you support the database after deployment?
+
We can agree ongoing administration, monitoring and optimisation. We review slow queries, locks, indexes and resource use, and assess changes through measurements. Support scope, alert responses and review schedules are agreed separately.
How long does deployment or migration take?
+
It depends on database size, integrations, version compatibility, availability requirements and the maintenance window. We prepare the schedule after assessment and a migration rehearsal. Project duration and application downtime are agreed separately.
Let’s plan your database deployment
Tell us the application, database engine and version, data volume and permitted maintenance window. Describe the problem or planned change. Do not send passwords or database copies through the form.
Discuss your database project