db recovery

hi,
i have a failure on a server controller and i have lost some volumes where
logs and index files of a db so now i have only the db (.mdf file) and none
backup.
SQL versione 7.0 sp3
Anyone can tell me if is it possible to do something to recover the db?
thanks
VTOf course, the first response is to use your backups. (If only the world
were so predictible.)
The following may 'save' the database (at least what is in the mdf file),
but it may be in a severe inconsistant state. And I understand that it may
be all you have. (Make a copy of the mdf file before doing anything.)
If you have only the mdf file, you should be able to detach the db, and then
re-attach the db. If you don't provide a log file, you will get a warning
that a new log file will be created. (Caveat: I can't remember how it works
in SQL v7, but these steps should work in SQL v2000.)
If this successfully attaches, you should rebuild the indexes. And then
thoroughly investigate the state of your data. You will have lost all data
changes that were in the log file but not yet written to disk. You will have
lost all incomplete transaction activity.
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"VT" <VT@.discussions.microsoft.com> wrote in message
news:04F7C77A-5D3F-4019-A067-A3C852B8C468@.microsoft.com...
> hi,
> i have a failure on a server controller and i have lost some volumes where
> logs and index files of a db so now i have only the db (.mdf file) and
> none
> backup.
> SQL versione 7.0 sp3
> Anyone can tell me if is it possible to do something to recover the db?
> thanks
> VT|||And if you are very, very lucky, you will not have lost your job for not
having current backups. ;-)
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:OHvVsnsqGHA.5108@.TK2MSFTNGP05.phx.gbl...
> Of course, the first response is to use your backups. (If only the world
> were so predictible.)
> The following may 'save' the database (at least what is in the mdf file),
> but it may be in a severe inconsistant state. And I understand that it may
> be all you have. (Make a copy of the mdf file before doing anything.)
> If you have only the mdf file, you should be able to detach the db, and
> then re-attach the db. If you don't provide a log file, you will get a
> warning that a new log file will be created. (Caveat: I can't remember how
> it works in SQL v7, but these steps should work in SQL v2000.)
> If this successfully attaches, you should rebuild the indexes. And then
> thoroughly investigate the state of your data. You will have lost all data
> changes that were in the log file but not yet written to disk. You will
> have lost all incomplete transaction activity.
> --
> Arnie Rowland
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "VT" <VT@.discussions.microsoft.com> wrote in message
> news:04F7C77A-5D3F-4019-A067-A3C852B8C468@.microsoft.com...
>|||don't warry for my job... server is of a customer...
i don't know how was configured the db when it was ok.
i tried to attach the db using thhe only file i have available:
EXEC sp_attach_db @.dbname = 'test-prod', @.filename1 =
'w:\databases\JDE_PRODUCTION.mdf'
server response was:
Changed language setting to us_english.
Server: Msg 5105, Level 16, State 5, Line 1
Device activation error. The physical file name
'd:\databases\JDE_PRODUCTION_INDICI.NDF' may be incorrect.
Server: Msg 5105, Level 16, State 1, Line 1
Device activation error. The physical file name
'd:\databases\JDE_PRODUCTION_INDICI2.NDF' may be incorrect.
Server: Msg 945, Level 14, State 1, Line 1
Database 'test-prod' cannot be opened because some of the files could not be
activated.
Server: Msg 1813, Level 16, State 1, Line 1
Could not open new database 'test-prod'. CREATE DATABASE is aborted.
any good idea?
"Arnie Rowland" wrote:

> And if you are very, very lucky, you will not have lost your job for not
> having current backups. ;-)
> --
> Arnie Rowland
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:OHvVsnsqGHA.5108@.TK2MSFTNGP05.phx.gbl...
>
>|||Do you have the ndf files? If you don't have the ndf files, you may have los
t significant amounts of data.
This link may provide some useful information.
[url]http://www.spaceprogram.com/knowledge/sqlserver_recover_from_deleted_log.html[/url
]
Always make backup copies of your files before attempting any recovery techn
iques whether documented or undocumented.
If that doesn't help, you may need to open a case with PSS.
--
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"VT" <VT@.discussions.microsoft.com> wrote in message news:E0A8B29D-227F-4782-8ED3-1884DBDB73
7D@.microsoft.com...[vbcol=seagreen]
> don't warry for my job... server is of a customer...
>
> i don't know how was configured the db when it was ok.
>
> i tried to attach the db using thhe only file i have available:
> EXEC sp_attach_db @.dbname = 'test-prod', @.filename1 =
> 'w:\databases\JDE_PRODUCTION.mdf'
>
> server response was:
> Changed language setting to us_english.
> Server: Msg 5105, Level 16, State 5, Line 1
> Device activation error. The physical file name
> 'd:\databases\JDE_PRODUCTION_INDICI.NDF' may be incorrect.
> Server: Msg 5105, Level 16, State 1, Line 1
> Device activation error. The physical file name
> 'd:\databases\JDE_PRODUCTION_INDICI2.NDF' may be incorrect.
> Server: Msg 945, Level 14, State 1, Line 1
> Database 'test-prod' cannot be opened because some of the files could not
be
> activated.
> Server: Msg 1813, Level 16, State 1, Line 1
> Could not open new database 'test-prod'. CREATE DATABASE is aborted.
>
> any good idea?
>
>
>
>
> "Arnie Rowland" wrote:
>