{"id":5901,"date":"2026-06-16T16:15:28","date_gmt":"2026-06-16T16:15:28","guid":{"rendered":"https:\/\/cloudsave.app\/knowledge-base\/mssql-transaction-log-full-recovery\/"},"modified":"2026-06-16T16:49:50","modified_gmt":"2026-06-16T16:49:50","slug":"mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k","status":"publish","type":"post","link":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/","title":{"rendered":"MSSQL tranzakci\u00f3napl\u00f3 megtelt: Megel\u0151z\u00e9si \u00e9s gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1k"},"content":{"rendered":"

Az adatb\u00e1zis-adminisztr\u00e1torok (DBA-k) \u00e9s a Microsoft SQL Servert kezel\u0151 DevOps m\u00e9rn\u00f6k\u00f6k sz\u00e1m\u00e1ra kev\u00e9s riaszt\u00e1s okoz akkora azonnali szorong\u00e1st, mint a 9002-es hiba: A(z) \u201eX\u201d adatb\u00e1zis tranzakci\u00f3napl\u00f3ja megtelt<\/em>. Amikor a tranzakci\u00f3napl\u00f3 megtelik \u00e9s nem tud tov\u00e1bb n\u0151ni, az adatb\u00e1zis gyakorlatilag \u00edr\u00e1sv\u00e9dett\u00e9 v\u00e1lik. Minden INSERT<\/code>, UPDATE<\/code> \u00e9s DELETE<\/code> m\u0171velet le\u00e1ll, az alkalmaz\u00e1sok tranzakci\u00f3i meghi\u00fasulnak, \u00e9s a termel\u00e9s teljesen meg\u00e1ll.<\/p>\n

Az SQL Server tranzakci\u00f3napl\u00f3-architekt\u00far\u00e1j\u00e1nak meg\u00e9rt\u00e9se, a kiv\u00e1lt\u00f3 ok pontos diagnosztiz\u00e1l\u00e1sa \u00e9s a gyors helyre\u00e1ll\u00edt\u00e1si elj\u00e1r\u00e1sok v\u00e9grehajt\u00e1sa kritikus k\u00e9szs\u00e9gek a magas rendelkez\u00e9sre \u00e1ll\u00e1s fenntart\u00e1s\u00e1hoz. Ez az \u00e1tfog\u00f3 \u00fatmutat\u00f3 felt\u00e1rja a tranzakci\u00f3napl\u00f3 m\u0171k\u00f6d\u00e9s\u00e9t, a megtelt napl\u00f3 v\u00e9szhelyzeti megold\u00e1s\u00e1t, valamint azokat az \u00e9p\u00edt\u00e9szeti bev\u00e1lt gyakorlatokat, amelyekkel megel\u0151zhet\u0151 a probl\u00e9ma megism\u00e9tl\u0151d\u00e9se.<\/p>\n

Az SQL Server tranzakci\u00f3napl\u00f3-architekt\u00far\u00e1j\u00e1nak meg\u00e9rt\u00e9se<\/h2>\n

A megtelt tranzakci\u00f3napl\u00f3 hat\u00e9kony hibaelh\u00e1r\u00edt\u00e1s\u00e1hoz el\u0151sz\u00f6r meg kell \u00e9rtenie, hogyan \u00edrja \u00e9s kezeli az adatokat az SQL Server.<\/p>\n

Write-Ahead Logging (WAL) \u2013 El\u0151\u00edr\u00f3 napl\u00f3z\u00e1s<\/h3>\n

Az SQL Server Write-Ahead Logging (WAL) protokollt haszn\u00e1l. Amikor adatm\u00f3dos\u00edt\u00e1s t\u00f6rt\u00e9nik, a v\u00e1ltoz\u00e1st el\u0151sz\u00f6r a mem\u00f3ri\u00e1ban l\u00e9v\u0151 tranzakci\u00f3napl\u00f3ba \u00edrja, majd ki\u00edrja a lemezen l\u00e9v\u0151 fizikai napl\u00f3f\u00e1jlba, miel\u0151tt a t\u00e9nyleges adatlapok friss\u00fcln\u00e9nek az adatb\u00e1zisf\u00e1jlokban (MDF\/NDF). Ez garant\u00e1lja az ACID (atomicit\u00e1s, konzisztencia, izol\u00e1ci\u00f3, tart\u00f3ss\u00e1g) megfelel\u0151s\u00e9get, biztos\u00edtva, hogy \u00f6sszeoml\u00e1s eset\u00e9n az SQL Server k\u00e9pes legyen a tranzakci\u00f3k \u00fajraj\u00e1tsz\u00e1s\u00e1ra (roll forward) vagy visszavon\u00e1s\u00e1ra (roll back).<\/p>\n

Virtu\u00e1lis napl\u00f3f\u00e1jlok (VLF-ek) \u00e9s k\u00f6rk\u00f6r\u00f6s napl\u00f3z\u00e1s<\/h3>\n

Bels\u0151leg a fizikai tranzakci\u00f3napl\u00f3-f\u00e1jl (LDF) kisebb, logikai szegmensekre van osztva, amelyeket virtu\u00e1lis napl\u00f3f\u00e1jloknak (VLF) nevez\u00fcnk. A tranzakci\u00f3napl\u00f3 k\u00f6rk\u00f6r\u00f6sen m\u0171k\u00f6dik. Ahogy a napl\u00f3rekordok \u00edr\u00f3dnak, kit\u00f6ltenek egy VLF-et, majd tov\u00e1bbl\u00e9pnek a k\u00f6vetkez\u0151re.<\/p>\n

Amikor a napl\u00f3 el\u00e9ri a fizikai f\u00e1jl v\u00e9g\u00e9t, megpr\u00f3b\u00e1l visszaugrani az elej\u00e9re. Azonban csak akkor \u00edrhat fel\u00fcl egy VLF-et, ha az inakt\u00edvk\u00e9nt<\/strong> van megjel\u00f6lve. Ha az \u00f6sszes VLF akt\u00edv (ami azt jelenti, hogy olyan napl\u00f3rekordokat tartalmaznak, amelyekre az SQL Servernek m\u00e9g sz\u00fcks\u00e9ge van), a napl\u00f3 nem tud k\u00f6rbefordulni. Ha az automatikus n\u00f6veked\u00e9s (auto-growth) enged\u00e9lyezve van \u00e9s van szabad lemezter\u00fclet, a fizikai f\u00e1jl megn\u0151. Ha a lemez megtelt vagy az automatikus n\u00f6veked\u00e9s korl\u00e1tozott, a 9002-es hib\u00e1t kapja.<\/p>\n

Napl\u00f3 csonk\u00edt\u00e1sa (Truncation) vs. Napl\u00f3 zsugor\u00edt\u00e1sa (Shrinking)<\/h3>\n

Gyakori t\u00e9vhit, hogy a napl\u00f3 csonk\u00edt\u00e1sa cs\u00f6kkenti a fizikai f\u00e1jlm\u00e9retet.
\n* Napl\u00f3 csonk\u00edt\u00e1sa:<\/strong> Az a folyamat, amely sor\u00e1n az akt\u00edv VLF-eket inakt\u00edvk\u00e9nt jel\u00f6lik meg, \u00edgy a ter\u00fclet \u00fajra felhaszn\u00e1lhat\u00f3v\u00e1 v\u00e1lik. Ez nem<\/em> cs\u00f6kkenti az LDF f\u00e1jl m\u00e9ret\u00e9t a lemezen.
\n* Napl\u00f3 zsugor\u00edt\u00e1sa:<\/strong> Az a folyamat, amely sor\u00e1n fizikailag cs\u00f6kkentik az LDF f\u00e1jl m\u00e9ret\u00e9t, \u00e9s a ter\u00fcletet visszaadj\u00e1k az oper\u00e1ci\u00f3s rendszernek.<\/p>\n

A Full (teljes) helyre\u00e1ll\u00edt\u00e1si modellben a napl\u00f3 csonk\u00edt\u00e1sa csak<\/em> akkor t\u00f6rt\u00e9nik meg, ha a tranzakci\u00f3napl\u00f3-ment\u00e9s sikeresen befejez\u0151d\u00f6tt (felt\u00e9ve, hogy m\u00e1s folyamatok nem tartj\u00e1k akt\u00edvan a napl\u00f3t).<\/p>\n

A \u201eTranzakci\u00f3napl\u00f3 megtelt\u201d hiba (9002-es hiba) diagnosztiz\u00e1l\u00e1sa<\/h2>\n

Amikor a napl\u00f3 megtelt, az els\u0151 l\u00e9p\u00e9s ne az legyen, hogy vakt\u00e1ban lemezter\u00fcletet ad hozz\u00e1 vagy zsugor\u00edtja a f\u00e1jlokat. Meg kell hat\u00e1roznia, mi\u00e9rt<\/em> nem tud a napl\u00f3 csonkulni. Az SQL Server be\u00e9p\u00edtett mechanizmust biztos\u00edt annak kider\u00edt\u00e9s\u00e9re, mi akad\u00e1lyozza a napl\u00f3 \u00fajrahasznos\u00edt\u00e1s\u00e1t a sys.databases<\/code> katal\u00f3gusn\u00e9zeten kereszt\u00fcl.<\/p>\n

Futtassa a k\u00f6vetkez\u0151 T-SQL parancsot a sz\u0171k keresztmetszet azonos\u00edt\u00e1s\u00e1hoz:<\/p>\n

SELECT \n    name AS DatabaseName, \n    recovery_model_desc AS RecoveryModel, \n    log_reuse_wait_desc AS LogReuseWaitReason\nFROM sys.databases\nWHERE name = 'YourDatabaseName';\n<\/code><\/pre>\n
A tranzakci\u00f3napl\u00f3k aktu\u00e1lis helykihaszn\u00e1lts\u00e1g\u00e1t a k\u00f6vetkez\u0151 paranccsal is ellen\u0151rizheti:<\/p>\n
DBCC SQLPERF(LOGSPACE);\n<\/code><\/pre>\n
Gyakori log_reuse_wait_desc<\/code> \u00e1llapotok<\/h3>\n
    \n
  1. LOG_BACKUP:<\/strong> Az adatb\u00e1zis Full vagy Bulk-Logged helyre\u00e1ll\u00edt\u00e1si modellben van, \u00e9s mostan\u00e1ban nem k\u00e9sz\u00fclt tranzakci\u00f3napl\u00f3-ment\u00e9s. Ez a leggyakoribb ok.<\/li>\n
  2. ACTIVE_TRANSACTION:<\/strong> Egy hosszan fut\u00f3 tranzakci\u00f3 (pl. egy hatalmas index-\u00fajra\u00e9p\u00edt\u00e9s vagy egy elfelejtett, lez\u00e1ratlan tranzakci\u00f3) akt\u00edvan tartja a napl\u00f3t.<\/li>\n
  3. REPLICATION \/ CDC:<\/strong> A tranzakci\u00f3s replik\u00e1ci\u00f3 vagy a Change Data Capture (CDC) enged\u00e9lyezve van, \u00e9s a Log Reader Agent m\u00e9g nem dolgozta fel a tranzakci\u00f3kat.<\/li>\n
  4. AVAILABILITY_REPLICA:<\/strong> AlwaysOn Availability Group eset\u00e9n egy m\u00e1sodlagos replika le van v\u00e1lasztva vagy t\u00fal lassan szinkroniz\u00e1l, ami arra k\u00e9nyszer\u00edti az els\u0151dleges replik\u00e1t, hogy megtartsa a napl\u00f3rekordokat, am\u00edg azok nem r\u00f6gz\u00fclnek a m\u00e1sodlagoson.<\/li>\n<\/ol>\n
    Gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1k: A probl\u00e9ma megold\u00e1sa \u00e9les k\u00f6rnyezetben<\/h2>\n
    A visszaadott log_reuse_wait_desc<\/code> \u00e9rt\u00e9kt\u0151l f\u00fcgg\u0151en a v\u00e9szhelyzeti v\u00e1lasz v\u00e1ltoz\u00f3 lesz. \u00cdme a gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1k a leggyakoribb forgat\u00f3k\u00f6nyvekhez.<\/p>\n
    1. forgat\u00f3k\u00f6nyv: Hi\u00e1nyz\u00f3 vagy sikertelen napl\u00f3ment\u00e9sek (LOG_BACKUP<\/code>)<\/h3>\n
    Ha a v\u00e1rakoz\u00e1si t\u00edpus LOG_BACKUP<\/code>, a megold\u00e1s egyszer\u0171: el kell k\u00e9sz\u00edtenie a tranzakci\u00f3napl\u00f3-ment\u00e9st.<\/p>\n
    BACKUP LOG [YourDatabaseName] \nTO DISK = 'N:BackupsYourDatabaseName_EmergencyLog.trn' \nWITH COMPRESSION, STATS = 10;\n<\/code><\/pre>\n
    Amint a ment\u00e9s befejez\u0151dik, az inakt\u00edv VLF-ek csonkulnak, \u00e9s az SQL Server folytatja a norm\u00e1l m\u0171k\u00f6d\u00e9st. Ha a ment\u00e9si meghajt\u00f3 megtelt, sz\u00fcks\u00e9g lehet ideiglenes h\u00e1l\u00f3zati megoszt\u00e1sra vagy null eszk\u00f6zre menteni (ez ut\u00f3bbi er\u0151sen ellenjavallt, kiv\u00e9ve, ha az adatb\u00e1zis k\u00f6nnyen reproduk\u00e1lhat\u00f3, mivel megszak\u00edtja a napl\u00f3l\u00e1ncot):<\/p>\n
    -- FIGYELEM: Ez megszak\u00edtja a napl\u00f3l\u00e1ncot \u00e9s vesz\u00e9lyezteti az id\u0151pontra t\u00f6rt\u00e9n\u0151 helyre\u00e1ll\u00edt\u00e1st.\n-- Csak akkor haszn\u00e1lja, ha felt\u00e9tlen\u00fcl sz\u00fcks\u00e9ges, \u00e9s azonnal k\u00f6vesse egy FULL ment\u00e9ssel.\nBACKUP LOG [YourDatabaseName] TO DISK = 'NUL';\n<\/code><\/pre>\n
    2. forgat\u00f3k\u00f6nyv: Hosszan fut\u00f3 akt\u00edv tranzakci\u00f3k (ACTIVE_TRANSACTION<\/code>)<\/h3>\n
    Ha egyetlen tranzakci\u00f3 \u00f3r\u00e1k \u00f3ta fut, az megakad\u00e1lyozza a napl\u00f3 csonk\u00edt\u00e1s\u00e1t a teljes id\u0151tartam alatt. El\u0151sz\u00f6r azonos\u00edtsa a probl\u00e9m\u00e1s tranzakci\u00f3t:<\/p>\n
    DBCC OPENTRAN('YourDatabaseName');\n<\/code><\/pre>\n
    Ez a parancs visszaadja a legr\u00e9gebbi akt\u00edv tranzakci\u00f3t \u00e9s annak folyamatazonos\u00edt\u00f3j\u00e1t (SPID). Tov\u00e1bbi r\u00e9szleteket tudhat meg arr\u00f3l, mit csin\u00e1l az SPID a dinamikus kezel\u00e9si n\u00e9zetek (DMV) lek\u00e9rdez\u00e9s\u00e9vel:<\/p>\n
    SELECT \n    s.session_id,\n    s.login_name,\n    s.host_name,\n    r.start_time,\n    r.status,\n    r.command,\n    t.text AS QueryText\nFROM sys.dm_exec_sessions s\nJOIN sys.dm_exec_requests r ON s.session_id = r.session_id\nCROSS APPLY sys.dm_exec_sql_text(r.sql_handle) t\nWHERE s.session_id = <SPID_FROM_DBCC_OPENTRAN>;\n<\/code><\/pre>\n
    Ha a tranzakci\u00f3 egy elszabadult lek\u00e9rdez\u00e9s vagy egy elakadt folyamat, el\u0151fordulhat, hogy meg kell szak\u00edtania a napl\u00f3 felszabad\u00edt\u00e1s\u00e1hoz.<\/p>\n
    KILL <SPID>;\n<\/code><\/pre>\n
    Megjegyz\u00e9s: Egy hatalmas tranzakci\u00f3 megszak\u00edt\u00e1sa visszag\u00f6rget\u00e9st (rollback) v\u00e1lt ki, ami jelent\u0151s id\u0151t vehet ig\u00e9nybe, \u00e9s \u00e1tmenetileg tov\u00e1bbi napl\u00f3tev\u00e9kenys\u00e9get gener\u00e1l. Ne ind\u00edtsa \u00fajra az SQL Server szolg\u00e1ltat\u00e1st visszag\u00f6rget\u00e9s k\u00f6zben, k\u00fcl\u00f6nben az adatb\u00e1zis helyre\u00e1ll\u00edt\u00e1si m\u00f3dba ker\u00fcl az \u00fajraind\u00edt\u00e1skor.<\/em><\/p>\n
    3. forgat\u00f3k\u00f6nyv: V\u00e9szhelyzeti ter\u00fcletfoglal\u00e1s (a lemez 100%-ban megtelt)<\/h3>\n
    Ha az LDF f\u00e1jl elfoglalta a teljes meghajt\u00f3t, m\u00e9g ment\u00e9st sem tud futtatni, mert az SQL Servernek sz\u00fcks\u00e9ge van egy kis mennyis\u00e9g\u0171 napl\u00f3ter\u00fcletre mag\u00e1nak a ment\u00e9si esem\u00e9nynek a r\u00f6gz\u00edt\u00e9s\u00e9hez. Ebben a forgat\u00f3k\u00f6nyvben egy m\u00e1sodlagos napl\u00f3f\u00e1jlt kell hozz\u00e1adnia egy m\u00e1sik, szabad ter\u00fclettel rendelkez\u0151 meghajt\u00f3n.<\/p>\n
    ALTER DATABASE [YourDatabaseName]\nADD LOG FILE \n(\n    NAME = N'YourDatabaseName_Log2',\n    FILENAME = N'E:TempLogsYourDatabaseName_Log2.ldf',\n    SIZE = 5GB,\n    MAXSIZE = 50GB,\n    FILEGROWTH = 1GB\n);\n<\/code><\/pre>\n
    Ez azonnal leveg\u0151h\u00f6z juttatja az SQL Servert. Amint az adatb\u00e1zis online \u00e1llapotba ker\u00fcl, k\u00e9sz\u00edtsen egy tranzakci\u00f3napl\u00f3-ment\u00e9st, \u00fcr\u00edtse ki a m\u00e1sodlagos napl\u00f3f\u00e1jlt, majd t\u00e1vol\u00edtsa el:<\/p>\n
    -- 1. K\u00e9sz\u00edtsen napl\u00f3ment\u00e9st a napl\u00f3 csonk\u00edt\u00e1s\u00e1hoz\nBACKUP LOG [YourDatabaseName] TO DISK = '...';\n\n-- 2. \u00dcr\u00edtse ki az ideiglenes napl\u00f3f\u00e1jlt\nDBCC SHRINKFILE (N'YourDatabaseName_Log2', EMPTYFILE);\n\n-- 3. T\u00e1vol\u00edtsa el az ideiglenes napl\u00f3f\u00e1jlt\nALTER DATABASE [YourDatabaseName] REMOVE FILE [YourDatabaseName_Log2];\n<\/code><\/pre>\n
    Bev\u00e1lt gyakorlatok a tranzakci\u00f3napl\u00f3 megel\u0151z\u00e9s\u00e9re \u00e9s kezel\u00e9s\u00e9re<\/h2>\n
    A reakt\u00edv hibaelh\u00e1r\u00edt\u00e1s stresszes \u00e9s hat\u00e1ssal van az SLA-kra. A proakt\u00edv \u00e9p\u00edt\u00e9szeti \u00e9s operat\u00edv bev\u00e1lt gyakorlatok bevezet\u00e9se elengedhetetlen a v\u00e1llalati adatb\u00e1zisok stabilit\u00e1s\u00e1hoz.<\/p>\n
    1. Robusztus, automatiz\u00e1lt ment\u00e9si strat\u00e9gia megval\u00f3s\u00edt\u00e1sa<\/h3>\n
    Ha egy adatb\u00e1zis Full helyre\u00e1ll\u00edt\u00e1si modellben van, a gyakori tranzakci\u00f3napl\u00f3-ment\u00e9sek k\u00f6telez\u0151ek. A helyre\u00e1ll\u00edt\u00e1si pont c\u00e9lkit\u0171z\u00e9s\u00e9t\u0151l (RPO) \u00e9s a tranzakci\u00f3k mennyis\u00e9g\u00e9t\u0151l f\u00fcgg\u0151en a napl\u00f3ment\u00e9seknek 5-15 percenk\u00e9nt meg kell t\u00f6rt\u00e9nni\u00fck.<\/p>\n
    A v\u00e1llalati ment\u00e9si megold\u00e1sok, mint p\u00e9ld\u00e1ul a CloudSave, jelent\u0151sen leegyszer\u0171s\u00edtik ezt a folyamatot. A VDI-n (Virtual Device Interface) kereszt\u00fcl az SQL Serverrel k\u00f6zvetlen\u00fcl integr\u00e1l\u00f3d\u00f3 CloudSave lehet\u0151v\u00e9 teszi a DBA-k sz\u00e1m\u00e1ra, hogy h\u00e1zirend-alap\u00fa, nagy gyakoris\u00e1g\u00fa tranzakci\u00f3napl\u00f3-ment\u00e9seket konfigur\u00e1ljanak. Ez biztos\u00edtja, hogy a napl\u00f3k folyamatosan csonkuljanak, biztons\u00e1gosan titkos\u00edtva legyenek, \u00e9s t\u00e1voli vagy megv\u00e1ltoztathatatlan felh\u0151t\u00e1rhelyen legyenek t\u00e1rolva, megel\u0151zve a LOG_BACKUP<\/code> v\u00e1rakoz\u00e1si \u00e1llapotot an\u00e9lk\u00fcl, hogy bonyolult egyedi SQL Agent feladatokra lenne sz\u00fcks\u00e9g.<\/p>\n
    2. A tranzakci\u00f3napl\u00f3 m\u00e9retez\u00e9se \u00e9s a VLF-ek kezel\u00e9se<\/h3>\n
    Az automatikus n\u00f6veked\u00e9sre (auto-growth) hagyatkozni a tranzakci\u00f3napl\u00f3 m\u00e9ret\u00e9nek kezel\u00e9s\u00e9ben vesz\u00e9lyes gyakorlat. Az automatikus n\u00f6veked\u00e9si m\u0171veletek k\u00f6lts\u00e9gesek \u00e9s sz\u00fcneteltetik a tranzakci\u00f3k feldolgoz\u00e1s\u00e1t, am\u00edg a lemez null\u00e1z\u00e1sa megt\u00f6rt\u00e9nik (kiv\u00e9ve, ha az Instant File Initialization enged\u00e9lyezve van, ami azonban nem<\/em> vonatkozik a napl\u00f3f\u00e1jlokra).<\/p>\n
    Ezenk\u00edv\u00fcl a gyakori, kis m\u00e9rt\u00e9k\u0171 automatikus n\u00f6veked\u00e9sek (pl. 10%-os vagy 50 MB-os l\u00e9p\u00e9sekben) VLF-fragment\u00e1ci\u00f3hoz<\/strong> vezetnek. A t\u00f6bb ezer apr\u00f3 VLF-fel rendelkez\u0151 tranzakci\u00f3napl\u00f3 s\u00falyosan rontja az adatb\u00e1zis ind\u00edt\u00e1si idej\u00e9t, a ment\u00e9si teljes\u00edtm\u00e9nyt \u00e9s a replik\u00e1ci\u00f3s k\u00e9sleltet\u00e9st.<\/p>\n
      \n
    • El\u0151re m\u00e9retezze a napl\u00f3t:<\/strong> Elemezze a legnagyobb karbantart\u00e1si m\u0171veleteit (p\u00e9ld\u00e1ul index-\u00fajra\u00e9p\u00edt\u00e9sek), \u00e9s m\u00e9retezze el\u0151re az LDF f\u00e1jlt, hogy n\u00f6veked\u00e9s n\u00e9lk\u00fcl is befogadja azokat.<\/li>\n
    • \u00c1ll\u00edtson be fix automatikus n\u00f6veked\u00e9st:<\/strong> M\u00f3dos\u00edtsa az automatikus n\u00f6veked\u00e9st sz\u00e1zal\u00e9kr\u00f3l fix m\u00e9retre (pl. 1 GB vagy 5 GB), hogy biztos\u00edtsa a VLF-ek eg\u00e9szs\u00e9ges m\u00e9ret\u0171 l\u00e9trehoz\u00e1s\u00e1t.<\/li>\n<\/ul>\n
      A VLF-ek sz\u00e1m\u00e1t a k\u00f6vetkez\u0151 lek\u00e9rdez\u00e9ssel ellen\u0151rizheti (SQL Server 2017+ eset\u00e9n):<\/p>\n
      SELECT \n    db_name(database_id) AS DatabaseName,\n    COUNT(vlf_sequence_number) AS VLF_Count\nFROM sys.dm_db_log_info(DB_ID('YourDatabaseName'));\n<\/code><\/pre>\n
      Ha a VLF-ek sz\u00e1ma 500 felett van, fontolja meg egy csendes id\u0151szak kiv\u00e1r\u00e1s\u00e1t, a napl\u00f3 minim\u00e1lis m\u00e9retre zsugor\u00edt\u00e1s\u00e1t, majd k\u00e9zi, nagy darabokban t\u00f6rt\u00e9n\u0151 vissza\u00e1ll\u00edt\u00e1s\u00e1t a sz\u00fcks\u00e9ges m\u00e9retre.<\/p>\n
      3. Indexkarbantart\u00e1si m\u0171veletek optimaliz\u00e1l\u00e1sa<\/h3>\n
      Az index-\u00fajra\u00e9p\u00edt\u00e9sek teljesen napl\u00f3zott m\u0171veletek, m\u00e9g Bulk-Logged helyre\u00e1ll\u00edt\u00e1si modellben is (az index t\u00edpus\u00e1t\u00f3l f\u00fcgg\u0151en). Egy 500 GB-os index \u00fajra\u00e9p\u00edt\u00e9se legal\u00e1bb 500 GB tranzakci\u00f3napl\u00f3-rekordot gener\u00e1l.<\/p>\n
      A karbantart\u00e1s k\u00f6zbeni napl\u00f3felf\u00fav\u00f3d\u00e1s m\u00e9rs\u00e9kl\u00e9se \u00e9rdek\u00e9ben:
      \n*   Haszn\u00e1lja a SORT_IN_TEMPDB = ON<\/code> opci\u00f3t az indexek \u00fajra\u00e9p\u00edt\u00e9sekor. Ez a rendez\u00e9si f\u00e1zist a TempDB-be helyezi \u00e1t, cs\u00f6kkentve a felhaszn\u00e1l\u00f3i adatb\u00e1zis tranzakci\u00f3napl\u00f3j\u00e1nak terhel\u00e9s\u00e9t.
      \n*   Lehet\u0151s\u00e9g szerint v\u00e1ltson index-\u00fajra\u00e9p\u00edt\u00e9sr\u0151l<\/em> index-\u00e1tszervez\u00e9sre<\/em> (reorganize), mivel az \u00e1tszervez\u00e9sek napl\u00f3hat\u00e9konyabbak, \u00e9s megszak\u00edthat\u00f3k a teljes m\u0171velet visszag\u00f6rget\u00e9se n\u00e9lk\u00fcl.
      \n*   K\u00f6tegelje a nagy DELETE<\/code> vagy UPDATE<\/code> m\u0171veleteket. Ahelyett, hogy 10 milli\u00f3 sort t\u00f6r\u00f6lne egyetlen tranzakci\u00f3ban, t\u00f6r\u00f6lje \u0151ket 50 000-es adagokban, v\u00e9gleges\u00edtve (commit) a m\u0171veletet, \u00e9s lehet\u0151v\u00e9 t\u00e9ve a napl\u00f3ment\u00e9sek sz\u00e1m\u00e1ra a napl\u00f3 csonk\u00edt\u00e1s\u00e1t a k\u00f6tegek k\u00f6z\u00f6tt.<\/p>\n
      4. Magas rendelkez\u00e9sre \u00e1ll\u00e1s \u00e9s replik\u00e1ci\u00f3s topol\u00f3gi\u00e1k figyel\u00e9se<\/h3>\n
      AlwaysOn Availability Groups eset\u00e9n az els\u0151dleges replika nem csonk\u00edthatja a napl\u00f3j\u00e1t, am\u00edg a napl\u00f3rekordok nem r\u00f6gz\u00fcltek az \u00f6sszes szinkron \u00e9s aszinkron m\u00e1sodlagos replik\u00e1n.<\/p>\n
      Ha egy m\u00e1sodlagos replika offline \u00e1llapotba ker\u00fcl, vagy ha a h\u00e1l\u00f3zati s\u00e1vsz\u00e9less\u00e9g nem tud l\u00e9p\u00e9st tartani az els\u0151dleges tranzakci\u00f3-gener\u00e1l\u00e1si sebess\u00e9g\u00e9vel, az els\u0151dleges k\u00fcld\u00e9si sora megn\u0151, \u00e9s a napl\u00f3 megtelik (AVAILABILITY_REPLICA<\/code> v\u00e1rakoz\u00e1si t\u00edpus).<\/p>\n
      Val\u00f3s\u00edtson meg robusztus figyel\u00e9st a SQLServer:Replica > Log Send Queue<\/code> teljes\u00edtm\u00e9nysz\u00e1ml\u00e1l\u00f3ra. Ha egy m\u00e1sodlagos replika v\u00e9glegesen elveszett, el kell t\u00e1vol\u00edtania az Availability Groupb\u00f3l, vagy fel kell f\u00fcggesztenie az adatmozg\u00e1st, hogy lehet\u0151v\u00e9 tegye az els\u0151dleges napl\u00f3 csonk\u00edt\u00e1s\u00e1t.<\/p>\n
      K\u00f6vetkeztet\u00e9s<\/h2>\n
      A megtelt tranzakci\u00f3napl\u00f3val val\u00f3 tal\u00e1lkoz\u00e1s az adatb\u00e1zis-adminisztr\u00e1torok \u201et\u0171zkereszts\u00e9ge\u201d, de nem kell, hogy hosszan tart\u00f3 \u00e1ll\u00e1sid\u0151h\u00f6z vezessen. A Write-Ahead Logging \u00e9s a VLF-ek m\u0171k\u00f6d\u00e9s\u00e9nek meg\u00e9rt\u00e9s\u00e9vel gyorsan diagnosztiz\u00e1lhatja a kiv\u00e1lt\u00f3 okot a sys.databases<\/code> seg\u00edts\u00e9g\u00e9vel, \u00e9s alkalmazhatja a megfelel\u0151 gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1t.<\/p>\n
      A hossz\u00fa t\u00e1v\u00fa stabilit\u00e1s a reakt\u00edv jav\u00edt\u00e1sokt\u00f3l val\u00f3 elmozdul\u00e1son alapul. A napl\u00f3f\u00e1jlok el\u0151zetes m\u00e9retez\u00e9se, a karbantart\u00e1si rutinok optimaliz\u00e1l\u00e1sa \u00e9s az olyan v\u00e1llalati szint\u0171 ment\u00e9si platformok haszn\u00e1lata, mint a CloudSave, a szigor\u00fa, automatiz\u00e1lt napl\u00f3ment\u00e9si \u00fctemtervek betart\u00e1sa \u00e9rdek\u00e9ben biztos\u00edtja, hogy a tranzakci\u00f3napl\u00f3k eg\u00e9szs\u00e9gesek, csonkoltak \u00e9s k\u00e9szen \u00e1lljanak a nagy \u00e1tereszt\u0151k\u00e9pess\u00e9g\u0171 \u00e9les munkaterhel\u00e9sek t\u00e1mogat\u00e1s\u00e1ra.<\/p>\n","protected":false},"excerpt":{"rendered":"
      ** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"MSSQL Transaction Log Full: Prevention & Recovery","rank_math_description":"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.","rank_math_focus_keyword":"MSSQL transaction log full","footnotes":""},"categories":[471],"tags":[969,4064,4065,4066,4067,4068,4069],"class_list":["post-5901","post","type-post","status-publish","format-standard","hentry","category-database-backup","tag-database-administration","tag-error-9002","tag-log-backup","tag-mssql","tag-sql-recovery","tag-sql-server","tag-transaction-log"],"yoast_head":"\nMSSQL Transaction Log Full: Prevention & Recovery<\/title>\n<meta name=\"description\" content=\"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/\" \/>\n<meta property=\"og:locale\" content=\"hu_HU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MSSQL tranzakci\u00f3napl\u00f3 megtelt: Megel\u0151z\u00e9si \u00e9s gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1k\" \/>\n<meta property=\"og:description\" content=\"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/\" \/>\n<meta property=\"og:site_name\" content=\"CloudSave\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-16T16:15:28+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-16T16:49:50+00:00\" \/>\n<meta name=\"author\" content=\"shervinrv\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szerz\u0151:\" \/>\n\t<meta name=\"twitter:data1\" content=\"shervinrv\" \/>\n\t<meta name=\"twitter:label2\" content=\"Becs\u00fclt olvas\u00e1si id\u0151\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 perc\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/knowledge-base\\\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/knowledge-base\\\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\\\/\"},\"author\":{\"name\":\"shervinrv\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"headline\":\"MSSQL tranzakci\u00f3napl\u00f3 megtelt: Megel\u0151z\u00e9si \u00e9s gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1k\",\"datePublished\":\"2026-06-16T16:15:28+00:00\",\"dateModified\":\"2026-06-16T16:49:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/knowledge-base\\\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\\\/\"},\"wordCount\":2326,\"publisher\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"keywords\":[\"Database Administration\",\"Error 9002\",\"Log Backup\",\"MSSQL\",\"SQL Recovery\",\"SQL Server\",\"Transaction Log\"],\"articleSection\":[\"Database Backup\"],\"inLanguage\":\"hu\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/knowledge-base\\\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\\\/\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/knowledge-base\\\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\\\/\",\"name\":\"MSSQL Transaction Log Full: Prevention & Recovery\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/#website\"},\"datePublished\":\"2026-06-16T16:15:28+00:00\",\"dateModified\":\"2026-06-16T16:49:50+00:00\",\"description\":\"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/knowledge-base\\\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\\\/#breadcrumb\"},\"inLanguage\":\"hu\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cloudsave.app\\\/hu\\\/knowledge-base\\\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/knowledge-base\\\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MSSQL tranzakci\u00f3napl\u00f3 megtelt: Megel\u0151z\u00e9si \u00e9s gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1k\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/#website\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/\",\"name\":\"CloudSave\",\"description\":\"CloudSave\",\"publisher\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"hu\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\",\"name\":\"shervinrv\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"hu\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"contentUrl\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"width\":859,\"height\":150,\"caption\":\"shervinrv\"},\"logo\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\"},\"sameAs\":[\"http:\\\/\\\/cloudsave.app\"],\"url\":\"https:\\\/\\\/cloudsave.app\\\/hu\\\/knowledge-base\\\/author\\\/shervinrv\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"MSSQL Transaction Log Full: Prevention & Recovery","description":"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/","og_locale":"hu_HU","og_type":"article","og_title":"MSSQL tranzakci\u00f3napl\u00f3 megtelt: Megel\u0151z\u00e9si \u00e9s gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1k","og_description":"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.","og_url":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/","og_site_name":"CloudSave","article_published_time":"2026-06-16T16:15:28+00:00","article_modified_time":"2026-06-16T16:49:50+00:00","author":"shervinrv","twitter_card":"summary_large_image","twitter_misc":{"Szerz\u0151:":"shervinrv","Becs\u00fclt olvas\u00e1si id\u0151":"13 perc"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/#article","isPartOf":{"@id":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/"},"author":{"name":"shervinrv","@id":"https:\/\/cloudsave.app\/hu\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"headline":"MSSQL tranzakci\u00f3napl\u00f3 megtelt: Megel\u0151z\u00e9si \u00e9s gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1k","datePublished":"2026-06-16T16:15:28+00:00","dateModified":"2026-06-16T16:49:50+00:00","mainEntityOfPage":{"@id":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/"},"wordCount":2326,"publisher":{"@id":"https:\/\/cloudsave.app\/hu\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"keywords":["Database Administration","Error 9002","Log Backup","MSSQL","SQL Recovery","SQL Server","Transaction Log"],"articleSection":["Database Backup"],"inLanguage":"hu"},{"@type":"WebPage","@id":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/","url":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/","name":"MSSQL Transaction Log Full: Prevention & Recovery","isPartOf":{"@id":"https:\/\/cloudsave.app\/hu\/#website"},"datePublished":"2026-06-16T16:15:28+00:00","dateModified":"2026-06-16T16:49:50+00:00","description":"** Discover expert strategies for preventing and resolving MSSQL transaction log full errors (Error 9002). Learn rapid recovery techniques, VLF management, and architectural best practices for DBAs.","breadcrumb":{"@id":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/#breadcrumb"},"inLanguage":"hu","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cloudsave.app\/hu\/knowledge-base\/mssql-tranzakci%c3%b3napl%c3%b3-megtelt-megel%c5%91z%c3%a9si-%c3%a9s-gyors-helyre%c3%a1ll%c3%adt%c3%a1si-strat%c3%a9gi%c3%a1k\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cloudsave.app\/hu\/"},{"@type":"ListItem","position":2,"name":"MSSQL tranzakci\u00f3napl\u00f3 megtelt: Megel\u0151z\u00e9si \u00e9s gyors helyre\u00e1ll\u00edt\u00e1si strat\u00e9gi\u00e1k"}]},{"@type":"WebSite","@id":"https:\/\/cloudsave.app\/hu\/#website","url":"https:\/\/cloudsave.app\/hu\/","name":"CloudSave","description":"CloudSave","publisher":{"@id":"https:\/\/cloudsave.app\/hu\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cloudsave.app\/hu\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"hu"},{"@type":["Person","Organization"],"@id":"https:\/\/cloudsave.app\/hu\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d","name":"shervinrv","image":{"@type":"ImageObject","inLanguage":"hu","@id":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","url":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","contentUrl":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","width":859,"height":150,"caption":"shervinrv"},"logo":{"@id":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png"},"sameAs":["http:\/\/cloudsave.app"],"url":"https:\/\/cloudsave.app\/hu\/knowledge-base\/author\/shervinrv\/"}]}},"_links":{"self":[{"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/posts\/5901","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/comments?post=5901"}],"version-history":[{"count":1,"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/posts\/5901\/revisions"}],"predecessor-version":[{"id":5966,"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/posts\/5901\/revisions\/5966"}],"wp:attachment":[{"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/media?parent=5901"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/categories?post=5901"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cloudsave.app\/hu\/wp-json\/wp\/v2\/tags?post=5901"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}