Płatnik
Repair of damaged .mdb Access databases and SQL migrations.
Dysk i Spółka • Databases / B2B
Database recovery and repair for Płatnik, Optima, SQL and Subiekt
We diagnose damaged databases, log files, backups and business environments without further repair attempts on production data.
Płatnik / Optima
SQL Server
Subiekt / Access
NDA / B2B
B2B mode / production bases
The database will not start, SQL Server reports suspect mode, or data is missing after a server failure? Secure the environment first.
First we secure the copy, then we check the database, logs and application environment. The repair is only after diagnosis.
In business cases, the database file itself is only part of the picture. Log consistency, service configuration and a safe B2B procedure matter as well. Before repair or migration, we first determine whether the problem involves the media, SQL engine, database files, volume or the whole server environment.
Płatnik
Optima
Subiekt
SQL Server
Access
accounting databases
Scope of systems
Which databases do we handle?
We restore financial, accounting, warehouse and business database environments.
Optima / XL
Recovery of Microsoft SQL Server databases (.mdf, .ldf).
Subiekt / Auditor
Database repair after power or drive failures.
SQL Server
Diagnosis of SQL databases, data files and logs after consistency errors.
.mdb / .accdb
Work with Access databases used by Płatnik and office systems.
Accounting and warehouse databases
Finance, HR and warehouse systems after environment failures.
.mdf / .ldf / .db
Database files, transaction logs, working copies and exports from the last working day.
VM / NAS / RAID
Diagnosis of databases running on servers, RAID arrays, NAS devices and virtual machines.
Crash scenarios
When can we help?
Hardware failure
The server or disk containing the database stopped working, for example after physical damage or RAID offline. We create a sector copy and recover the most consistent database file possible.
Database corrupted / page fault
The database is visible, but the SQL engine reports a consistency check error or page fault.
Suspect Mode
SQL Server marked the database as damaged after a restart or interrupted write.
Deleted database
Accidental deletion of database files or formatting of the volume.
Failure after power loss
The database stopped working after a power outage, system hang or server restart.
Problem after repair or migration
A failed update, manual index repair or backup restore made the environment worse.
Rescue procedure
B2B security
We know company downtime is expensive, so the process starts with securing the current state and risk.
Business priority
Database cases are triaged by business impact; after-hours mode can be agreed for critical operational failures.
Confidentiality and NDA
We sign NDAs. Your financial data is safe; we work offline.
Work on a copy
We secure the source material first and run diagnostics on a working copy.
Operation verification
Before payment, we check whether the database can be mounted and whether the latest invoices and declarations can be viewed.
First Decisions
Database failure - what to do immediately so you do not make it worse
When a database such as Płatnik, Optima, SQL or Subiekt stops opening, repeated repairs and repeated launch attempts are the worst option. The cause may be damaged database files, disk errors or lack of space, and each additional attempt can write new bad data.
With SQL Server suggest mode, corrupt MDF/LDF files, Płatnik errors, Optims or Subiekthis first secure a copy of the catalogues, logs and the last correct condition. Do not run automatic modification procedures on production if this is the only copy of data.
Do now
- stop work on the computer or server and secure a copy of the current database files
- record error messages with a screenshot - they are often key to diagnosis
- if settlements or declarations are time-sensitive, mark that in the request
Do not
- do not install anything or move files hastily
- do not run multiple repairs or overwrite old database files with new ones
- do not keep working on the original media if read errors appeared
In the lab, we first make a safe image of the storage device, then we work on a copy. That way you don't risk losing any other data.
Diagnostic decision
How to tell a database problem from a disk problem without going too deep
If the computer suddenly slows down, files take a very long time to open or copy errors appear, the issue often lies in the media rather than the application itself. Messages about a damaged database, no table access or consistency errors may come from an interrupted write.
Logical problem
Messages about a damaged database, no table access, consistency check error, page fault or suspect mode after restart.
Drive or server problem
Slow reads, copy errors, disappearing files, power failure, RAID offline or system hangs.
consistency errors
long reading
copy errors
suspect mode
broken record
power failure
In practice, it is safest to treat the situation as a potential data failure: do not generate new records and secure the state of "here and now".
MDF / LDF / Accounting applications
Damaged MDF/LDF or Płatnik database, Optimy or Subiekta? Stop the production procedures.
If SQL Server reports supspect mode or MDF/LDF file cannot be connected, stop the modification procedures on production. The same applies to the Płatnik, Optima and Subiekt after the disk failure.
Do not run REPAIR_ALLOW_DATA_LOSS on the only copy of the data. First secure MDF, LDF, logs, backups and information about SQL and program.
In the notification, indicate whether the database was running on the server, the RAID array, the NAS or the virtual machine when the last efficient copy was created and what messages the application shows.
MDF / LDF / suggest mode
Save the error message, SQL Server version and the last efficient copy. Do not disconnect or overwrite logs if the database was on the array, NAS or server.
The accounting database does not run
Prepare a program directory, database files, logs and information if anyone has tried to import, update or automatically modify the procedure after the crash.
Path for companies and accounting
If the interruption blocks invoices, staff or settlements, describe the business priority in the notification. It helps to take a safe next step.
Contact regarding RAID or NAS failure
Is this a database problem or a wider business-environment failure?
If the problem concerns the Płatnik, Optima, SQL or Subiekta, select this path. For the accounting unit and the general B2B failure you have separate pages.
Before repairing a database
Related guides for database and business failures
Review these paths before running another repair, restore or import on the original data.
Accounting data failure and GDPR duties
How to secure accounting and HR data after a disk or database incident.
Read the guideWhat a professional lab does
A B2B action plan when databases live on a server, RAID or NAS environment.
Read the guideQuick consultation
Submit a database for laboratory analysis
Have questions? Contact us before further repair attempts overwrite files or logs.
How to prepare files, logs and the environment for database diagnosis
In database cases, not only .mdf, .ldf, .db files and working copies matter. Context also speeds things up: application name, system version, last successful write and error messages from the console or application.
Database files
.mdf, .ldf, .db, .mdb, kopie robocze i oryginalne katalogi programu.
SQL / application logs
Error messages from the console, SQL Server or accounting application.
backup / snapshot
A current backup, snapshot or export from the last working day.
Application version
Application name, system version and whether the database was on a server or computer.
Error messages
Error text, screenshot and the last time it started correctly.
Last correct work
Information on whether anyone ran SQL repair, an update or backup restore after the failure.
Source Environment
Database from a disk, server, NAS or backup - secure the original first
In Płatnik, Optima, Subiekt and SQL cases, the problem often is not limited to the database file. A disk, RAID, NAS or backup failure can cause consistency errors, missing logs, damaged indexes or no access to the latest writes. That is why we do not import data on the original without a plan and do not overwrite the last working copy without a plan.
Shortening of diagnosis
Which files and information actually speed up diagnosis
We work fastest when the database comes with basic context: application folder structure, server logs, user names and the date of the last correct write. It also matters whether the issue appeared after a power failure, disk error, system update or ransomware attack.
application folder structure
server logs and user names
date of the last correct write
information about copying files while the system was live
manual index repair or backup restore
decision: logical copy, media image or database structure
Risk tests
What not to do after a database error
- Do not run several repair tools one after another hoping something will work.
- Do not restore old backups over the same files without preserving the original.
- Do not compress or move a damaged database between computers without a binary copy.
- Do not assume the issue is only software-related if there were disk errors, power loss or system hangs earlier.
When to Escale
When contacting a laboratory makes the most sense
If the application stopped opening the database after a power failure, the system reports read errors, the server disappears from the network or files have unnatural sizes, it is better not to make more attempts on the original.
Read or copy errors
The problem may go beyond the database and involve the media or server environment.
Power failure or restart
An interrupted write can damage database, log and application-folder consistency.
Server disappears from the network
Secure the current state before further attempts increase the chaos.
Files have unusual sizes
This is a signal that calm diagnosis is needed instead of improvised repair on the original.
Logic or media
When is a database problem logical, and when can it mean media failure?
Not every database error means physical disk damage, but some signals require that possibility: delayed writes, copy problems, system hangs or disappearing files.
FAQ
FAQ - recovery and repair of Płatnik, Optima, SQL and Subiekt databases
Do you repair the database or recover it from a copy?
It depends on the case. Sometimes the database structure needs repair, and sometimes it is safer to restore or recover data from a working copy or damaged environment.
Which files and information should I prepare before diagnosis?
Prepare database files, logs, system version information, error messages and a description of the failure moment. This shortens the path to the right diagnosis.
Do you handle time-sensitive accounting and business cases?
Yes. These failures often block current operations. Scope and mode are agreed after risk assessment and source-material availability checks.
Can data consistency be checked after repair?
Yes. Technically, we can assess whether the database starts correctly and keeps the required structure. The test scope depends on the system and input data.
Environmental protection
Secure the database before further attempts overwrite data
We work in B2B mode, on a copy, with NDA available and database operation verified before handover.