Coba bantu ya..., btw file sql server kan ada 2 : ".mdf" dan ".ldf".
apa dua2nya juga dah dipindahin. klo mdf aja yang dipindahin, ya jelas
g bisa. harus ada ldf - nya juga.

semoga membantu

--- In [email protected], "Sodik Ihwan" <[EMAIL PROTECTED]>
wrote:
>
> Thx Mas, uraiannya lengkap, tapi sayangnya kondisi saat ini file mdf
tsb  
> bukan dalam posisi suspect.
> jadi waktu itu engine nya ane matiin trus file nya ane pindahin ke
folder  
> lain. nah pas mo di attach lagi sama sekali tidak bisa.
> anyway, Thx a lot mas,
> salam,
> sodik
> On Thu, 10 Apr 2008 08:14:44 +0700, wiltek.ghozali  
> <[EMAIL PROTECTED]> wrote:
> 
> > Hm... SQL Server memang sensitif dengan mati listrik.
> > Ini ada kutipan solusi dari web tetangga :
> >
> >     http://www.nigelrivett.net/
> >
> >     -- Recover a corrupt database
> >     Author Nigel Rivett
> >
> >     The first step is to attach the database as suspect
> >     Create a database with an mdf of the same size as the old one
> >     stop the server.
> >     Copy the corrupt mdf over the newly created one.
> >     Restart the server - the database should be suspect.
> >
> >     Get the server to retry recovery
> >     Reset the suspect flag
> >         this can be done by executing sp_resetstatus 'mydbname'
> >         or by
> >         update master..sysdatabases SET status = status ^ 256
where name
> >     = 'mydbname'
> >     Restart the server
> >
> >     If the database is still suspect set it to emergency mode
> >     This will be the case for torn pages - if you get a torn page
error
> >     go straight to this step.
> >         update master..sysdatabases set status = 32768 where name =
> >     'mydbname'
> >         (for v7 I believe it was update master..sysdatabases set
status
> >     = -32768 where name = 'mydbname')
> >
> >     The database should now be in emergency mode and allow you to
access
> >     the data.
> >
> >     The data should now be transferred to another database via
dts, bcp
> >     or queries (I prefer bcp native format).
> >     You will get an error when trying to access the corrupt data but
> >     should be able to access all the rest of the data.
> >     Use indexes to access data around the corrupt pages.
> >
> >     To allow the above commands to work you will have to allow updates
> >     to system tables
> >     Sp_configure 'allow updates', 1
> >     Reconfigure with override
> >
> >     Remember to set it back afterwards
> >
> >
> > semoga membantu.
> >
> > Sodik Ihwan wrote:
> >> Dear All,
> >> Mohon bantuannya, kemaren kompi yg ada ms-sql server nya ndak sengaja
> >> kecabut kabel powernya ama orang yg lg benerin listrik, stelah itu
> >> database di ms-sql nya jadi suspect.
> >> ane udah coba beberapa cara tapi belum ada yg berhasil, terakhir
waktu
> >> file .mdf mo di attach lagi muncul error message
> >>
> >> Microsoft SQL-DMO (ODBC SQLState: HY000)
> >> error 823: I/O error (torn page) detected during read at offset
> >> 0000000000000000 in file 'D:\KerjaanGW\DatabaseGW.MDF'.
> >>
> >> Mohon bantuan gimana caranya supaya bisa kembali normal, soale
database
> >> kerjaan kantor.
> >>
> >> Thx All.
> >> sodik
> >>
> >>
> >
> 
> 
> 
> -- 
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> 
> Send instant messages to your online friends
http://asia.messenger.yahoo.com
>


Kirim email ke