Veritabanina ait log dosyasi (ldf) olmadan Sadece mdf dosyasi ile attach islemi nasil yapilir

Bir çogumuz SQL Serverda veritabani dosyalarini kullanarak attach islemi yapmisizdir. Attach islemi bir mdf ve birde ldf dosyasi ister. Eger ldf dosyaniz yoksa hata alir ve islemi gerçeklestiremezsiniz. Peki bu durumda ne yapilabilir.

Management Studio dan attach deyip mdf dosyasini seçtiginizde asagidaki hatayi aliriz.

Unable to open the physical file "Dosyanizin yolu.LDF". Operating system error 2: "2(Sistem belirtilen dosyayi bulamiyor.)". (Microsoft SQL Server, Error: 5120)

 

Bu hatayi almanizin sebebi SQL Server attach islemi sirasinda mdf dosyasina ait bir log yani ldf dosyasini bulamamaktadir. Peki, siz veritabanina ait ldf dosyasini zamaninda yedeklemediyseniz sadece mdf dosyasi kullanarak veritabanini nasil olusturabilirsiniz.

Bunun belki birden çok yöntemi olabilir ama en kolay yöntemi sp_attach_single_file_db stored procedure’ünü kullanmaktir. Bu produre gösterdiginiz mdf dosyasina ait ldf dosyasini kendisi otomatik olarak olusturur. Gelelim nasil kullanacagimiza.

.

use master

EXEC sp_attach_single_file_db @dbname = ‘VeriTabaniAdi’,

    @physname = N’mdf dosyasinin fiziksel adresi(örn c:\deneme.mdf)’;

 

Yukaridaki sql cümlesini çalistirdiginizda asagidaki gibi bir output alir ve veritabaninizi attach etmis olursunuz.

File activation failure. The physical file name "C:\VeriTabaniAdi_log.LDF" may be incorrect.

New log file ‘mdf dosyasinin fiziksel adresi\VeriTabaniAdi_log.LDF’ was created.

Converting database ‘VeriTabaniAdi’ from version 611 to the current version 655.

Database ‘VeriTabaniAdi’ running the upgrade step from version 611 to version 621.

Database ‘VeriTabaniAdi’ running the upgrade step from version 621 to version 622.

Database ‘VeriTabaniAdi’ running the upgrade step from version 622 to version 625.

Database ‘VeriTabaniAdi’ running the upgrade step from version 625 to version 626.

Database ‘VeriTabaniAdi’ running the upgrade step from version 626 to version 627.

Database ‘VeriTabaniAdi’ running the upgrade step from version 627 to version 628.

Database ‘VeriTabaniAdi’ running the upgrade step from version 628 to version 629.

Database ‘VeriTabaniAdi’ running the upgrade step from version 629 to version 630.

Database ‘VeriTabaniAdi’ running the upgrade step from version 630 to version 631.

Database ‘VeriTabaniAdi’ running the upgrade step from version 631 to version 632.

Database ‘VeriTabaniAdi’ running the upgrade step from version 632 to version 633.

Database ‘VeriTabaniAdi’ running the upgrade step from version 633 to version 634.

Database ‘VeriTabaniAdi’ running the upgrade step from version 634 to version 635.

Database ‘VeriTabaniAdi’ running the upgrade step from version 635 to version 636.

Database ‘VeriTabaniAdi’ running the upgrade step from version 636 to version 637.

Database ‘VeriTabaniAdi’ running the upgrade step from version 637 to version 638.

Database ‘VeriTabaniAdi’ running the upgrade step from version 638 to version 639.

Database ‘VeriTabaniAdi’ running the upgrade step from version 639 to version 640.

Database ‘VeriTabaniAdi’ running the upgrade step from version 640 to version 641.

Database ‘VeriTabaniAdi’ running the upgrade step from version 641 to version 642.

Database ‘VeriTabaniAdi’ running the upgrade step from version 642 to version 643.

Database ‘VeriTabaniAdi’ running the upgrade step from version 643 to version 644.

Database ‘VeriTabaniAdi’ running the upgrade step from version 644 to version 645.

Database ‘VeriTabaniAdi’ running the upgrade step from version 645 to version 646.

Database ‘VeriTabaniAdi’ running the upgrade step from version 646 to version 647.

Database ‘VeriTabaniAdi’ running the upgrade step from version 647 to version 648.

Database ‘VeriTabaniAdi’ running the upgrade step from version 648 to version 649.

Database ‘VeriTabaniAdi’ running the upgrade step from version 649 to version 650.

Database ‘VeriTabaniAdi’ running the upgrade step from version 650 to version 651.

Database ‘VeriTabaniAdi’ running the upgrade step from version 651 to version 652.

Database ‘VeriTabaniAdi’ running the upgrade step from version 652 to version 653.

Database ‘VeriTabaniAdi’ running the upgrade step from version 653 to version 654.

Database ‘VeriTabaniAdi’ running the upgrade step from version 654 to version 655.

 konuyu forumda tartisin

 

One thought on “Veritabanina ait log dosyasi (ldf) olmadan Sadece mdf dosyasi ile attach islemi nasil yapilir

Bir cevap yazın

E-posta hesabınız yayımlanmayacak. Gerekli alanlar * ile işaretlenmişlerdir