Showing posts with label gig. Show all posts
Showing posts with label gig. Show all posts

Wednesday, March 7, 2012

Deleted .LDF File how can the database be brought back online

Ok this morning one of the IT guys deleted the LDF file
from the server for a particular database. The file was
45 gig, he stopped the server then deleted the file,
without detaching the database.
We tried running sp_attach_db @.dbname='', @.physname=''
filling in the blanks but that refused to work.
We still have the 65 gig MDF file but we get error 9004
when we try to attach using enterprise manager.
We saw a knowledge base article saying to install service
pack 3a will this solve the problem, don't necessarily
want to mess about with these things unless absolutely
necessary
I will be very grateful is someone tells me how to sort
this and doesn't say i'm up the creek without a paddle
thanks in advanceYou can try sp_attach_single_file_db instead of sp_attach_db. That is still
not guaranteed to work in this scenario though, it is only _guaranteed_ to
work if you explicitly detach the database, but you might be lucky.
Otherwise you will have to restore from the back up.
--
Jacco Schalkwijk
SQL Server MVP
"Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> Ok this morning one of the IT guys deleted the LDF file
> from the server for a particular database. The file was
> 45 gig, he stopped the server then deleted the file,
> without detaching the database.
> We tried running sp_attach_db @.dbname='', @.physname=''
> filling in the blanks but that refused to work.
> We still have the 65 gig MDF file but we get error 9004
> when we try to attach using enterprise manager.
> We saw a knowledge base article saying to install service
> pack 3a will this solve the problem, don't necessarily
> want to mess about with these things unless absolutely
> necessary
> I will be very grateful is someone tells me how to sort
> this and doesn't say i'm up the creek without a paddle
> thanks in advance|||You also need to seriously suggest firing that IT guy...What he's done
really pissed off DBAs!
"Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> Ok this morning one of the IT guys deleted the LDF file
> from the server for a particular database. The file was
> 45 gig, he stopped the server then deleted the file,
> without detaching the database.
> We tried running sp_attach_db @.dbname='', @.physname=''
> filling in the blanks but that refused to work.
> We still have the 65 gig MDF file but we get error 9004
> when we try to attach using enterprise manager.
> We saw a knowledge base article saying to install service
> pack 3a will this solve the problem, don't necessarily
> want to mess about with these things unless absolutely
> necessary
> I will be very grateful is someone tells me how to sort
> this and doesn't say i'm up the creek without a paddle
> thanks in advance|||Common error. Look at the suggestion by Jasper Smith here
(http://tinyurl.com/5g2ol). Note that rebuilding the log this way is not
supported by Microsoft, and you should make a copy of the mdf file just in
case it does not work for you. Good luck.
--
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Use MiniSQLBackup Lite, free!
"Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> Ok this morning one of the IT guys deleted the LDF file
> from the server for a particular database. The file was
> 45 gig, he stopped the server then deleted the file,
> without detaching the database.
> We tried running sp_attach_db @.dbname='', @.physname=''
> filling in the blanks but that refused to work.
> We still have the 65 gig MDF file but we get error 9004
> when we try to attach using enterprise manager.
> We saw a knowledge base article saying to install service
> pack 3a will this solve the problem, don't necessarily
> want to mess about with these things unless absolutely
> necessary
> I will be very grateful is someone tells me how to sort
> this and doesn't say i'm up the creek without a paddle
> thanks in advance|||> You also need to seriously suggest firing that IT guy...What he's done
> really pissed off DBAs!
Or fire the IT manager who allow for non-trained personnel have this kind or privileges on a database
server... :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:eiYHCg2jEHA.4068@.TK2MSFTNGP10.phx.gbl...
> You also need to seriously suggest firing that IT guy...What he's done
> really pissed off DBAs!
>
> "Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
> news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> > Ok this morning one of the IT guys deleted the LDF file
> > from the server for a particular database. The file was
> > 45 gig, he stopped the server then deleted the file,
> > without detaching the database.
> >
> > We tried running sp_attach_db @.dbname='', @.physname=''
> >
> > filling in the blanks but that refused to work.
> >
> > We still have the 65 gig MDF file but we get error 9004
> > when we try to attach using enterprise manager.
> >
> > We saw a knowledge base article saying to install service
> > pack 3a will this solve the problem, don't necessarily
> > want to mess about with these things unless absolutely
> > necessary
> >
> > I will be very grateful is someone tells me how to sort
> > this and doesn't say i'm up the creek without a paddle
> >
> > thanks in advance
>|||I wouldn't sack anyone for pissing of DBAs. Putting 65 GB of business data
at risk is a different matter though... not to mention the downtime and the
extra work involved.
--
Jacco Schalkwijk
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uWLfBT4jEHA.1404@.TK2MSFTNGP09.phx.gbl...
>> You also need to seriously suggest firing that IT guy...What he's done
>> really pissed off DBAs!
> Or fire the IT manager who allow for non-trained personnel have this kind
> or privileges on a database
> server... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Richard Ding" <rding@.acadian-asset.com> wrote in message
> news:eiYHCg2jEHA.4068@.TK2MSFTNGP10.phx.gbl...
>> You also need to seriously suggest firing that IT guy...What he's done
>> really pissed off DBAs!
>>
>> "Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
>> news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
>> > Ok this morning one of the IT guys deleted the LDF file
>> > from the server for a particular database. The file was
>> > 45 gig, he stopped the server then deleted the file,
>> > without detaching the database.
>> >
>> > We tried running sp_attach_db @.dbname='', @.physname=''
>> >
>> > filling in the blanks but that refused to work.
>> >
>> > We still have the 65 gig MDF file but we get error 9004
>> > when we try to attach using enterprise manager.
>> >
>> > We saw a knowledge base article saying to install service
>> > pack 3a will this solve the problem, don't necessarily
>> > want to mess about with these things unless absolutely
>> > necessary
>> >
>> > I will be very grateful is someone tells me how to sort
>> > this and doesn't say i'm up the creek without a paddle
>> >
>> > thanks in advance
>>
>|||Well they managed to get it up and running with only a 2 week loss of data,
so that was good but they didnt get any sleep doing it, got it running the
next morning, not sure how they did it, but they did, luckily
think the backups are been re-thinked, lol
A day researching was different i s'pose
thanks for the suggestions
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:ekAqO$2jEHA.596@.TK2MSFTNGP11.phx.gbl...
> Common error. Look at the suggestion by Jasper Smith here
> (http://tinyurl.com/5g2ol). Note that rebuilding the log this way is not
> supported by Microsoft, and you should make a copy of the mdf file just in
> case it does not work for you. Good luck.
> --
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backups? Use MiniSQLBackup Lite, free!
>
> "Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
> news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> > Ok this morning one of the IT guys deleted the LDF file
> > from the server for a particular database. The file was
> > 45 gig, he stopped the server then deleted the file,
> > without detaching the database.
> >
> > We tried running sp_attach_db @.dbname='', @.physname=''
> >
> > filling in the blanks but that refused to work.
> >
> > We still have the 65 gig MDF file but we get error 9004
> > when we try to attach using enterprise manager.
> >
> > We saw a knowledge base article saying to install service
> > pack 3a will this solve the problem, don't necessarily
> > want to mess about with these things unless absolutely
> > necessary
> >
> > I will be very grateful is someone tells me how to sort
> > this and doesn't say i'm up the creek without a paddle
> >
> > thanks in advance
>

Deleted .LDF File how can the database be brought back online

Ok this morning one of the IT guys deleted the LDF file
from the server for a particular database. The file was
45 gig, he stopped the server then deleted the file,
without detaching the database.
We tried running sp_attach_db @.dbname='', @.physname=''
filling in the blanks but that refused to work.
We still have the 65 gig MDF file but we get error 9004
when we try to attach using enterprise manager.
We saw a knowledge base article saying to install service
pack 3a will this solve the problem, don't necessarily
want to mess about with these things unless absolutely
necessary
I will be very grateful is someone tells me how to sort
this and doesn't say i'm up the creek without a paddle
thanks in advanceYou can try sp_attach_single_file_db instead of sp_attach_db. That is still
not guaranteed to work in this scenario though, it is only _guaranteed_ to
work if you explicitly detach the database, but you might be lucky.
Otherwise you will have to restore from the back up.
Jacco Schalkwijk
SQL Server MVP
"Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> Ok this morning one of the IT guys deleted the LDF file
> from the server for a particular database. The file was
> 45 gig, he stopped the server then deleted the file,
> without detaching the database.
> We tried running sp_attach_db @.dbname='', @.physname=''
> filling in the blanks but that refused to work.
> We still have the 65 gig MDF file but we get error 9004
> when we try to attach using enterprise manager.
> We saw a knowledge base article saying to install service
> pack 3a will this solve the problem, don't necessarily
> want to mess about with these things unless absolutely
> necessary
> I will be very grateful is someone tells me how to sort
> this and doesn't say i'm up the creek without a paddle
> thanks in advance|||You also need to seriously suggest firing that IT guy...What he's done
really pissed off DBAs!
"Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> Ok this morning one of the IT guys deleted the LDF file
> from the server for a particular database. The file was
> 45 gig, he stopped the server then deleted the file,
> without detaching the database.
> We tried running sp_attach_db @.dbname='', @.physname=''
> filling in the blanks but that refused to work.
> We still have the 65 gig MDF file but we get error 9004
> when we try to attach using enterprise manager.
> We saw a knowledge base article saying to install service
> pack 3a will this solve the problem, don't necessarily
> want to mess about with these things unless absolutely
> necessary
> I will be very grateful is someone tells me how to sort
> this and doesn't say i'm up the creek without a paddle
> thanks in advance|||Common error. Look at the suggestion by Jasper Smith here
(http://tinyurl.com/5g2ol). Note that rebuilding the log this way is not
supported by Microsoft, and you should make a copy of the mdf file just in
case it does not work for you. Good luck.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Use MiniSQLBackup Lite, free!
"Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> Ok this morning one of the IT guys deleted the LDF file
> from the server for a particular database. The file was
> 45 gig, he stopped the server then deleted the file,
> without detaching the database.
> We tried running sp_attach_db @.dbname='', @.physname=''
> filling in the blanks but that refused to work.
> We still have the 65 gig MDF file but we get error 9004
> when we try to attach using enterprise manager.
> We saw a knowledge base article saying to install service
> pack 3a will this solve the problem, don't necessarily
> want to mess about with these things unless absolutely
> necessary
> I will be very grateful is someone tells me how to sort
> this and doesn't say i'm up the creek without a paddle
> thanks in advance|||> You also need to seriously suggest firing that IT guy...What he's done
> really pissed off DBAs!
Or fire the IT manager who allow for non-trained personnel have this kind or
privileges on a database
server... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:eiYHCg2jEHA.4068@.TK2MSFTNGP10
.phx.gbl...
> You also need to seriously suggest firing that IT guy...What he's done
> really pissed off DBAs!
>
> "Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
> news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
>|||I wouldn't sack anyone for pissing of DBAs. Putting 65 GB of business data
at risk is a different matter though... not to mention the downtime and the
extra work involved.
Jacco Schalkwijk
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uWLfBT4jEHA.1404@.TK2MSFTNGP09.phx.gbl...
> Or fire the IT manager who allow for non-trained personnel have this kind
> or privileges on a database
> server... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Richard Ding" <rding@.acadian-asset.com> wrote in message
> news:eiYHCg2jEHA.4068@.TK2MSFTNGP10.phx.gbl...
>|||Well they managed to get it up and running with only a 2 week loss of data,
so that was good but they didnt get any sleep doing it, got it running the
next morning, not sure how they did it, but they did, luckily
think the backups are been re-thinked, lol
A day researching was different i s'pose
thanks for the suggestions
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:ekAqO$2jEHA.596@.TK2MSFTNGP11.phx.gbl...
> Common error. Look at the suggestion by Jasper Smith here
> (http://tinyurl.com/5g2ol). Note that rebuilding the log this way is not
> supported by Microsoft, and you should make a copy of the mdf file just in
> case it does not work for you. Good luck.
> --
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backups? Use MiniSQLBackup Lite, free!
>
> "Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
> news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
>

Deleted .LDF File how can the database be brought back online

Ok this morning one of the IT guys deleted the LDF file
from the server for a particular database. The file was
45 gig, he stopped the server then deleted the file,
without detaching the database.
We tried running sp_attach_db @.dbname='', @.physname=''
filling in the blanks but that refused to work.
We still have the 65 gig MDF file but we get error 9004
when we try to attach using enterprise manager.
We saw a knowledge base article saying to install service
pack 3a will this solve the problem, don't necessarily
want to mess about with these things unless absolutely
necessary
I will be very grateful is someone tells me how to sort
this and doesn't say i'm up the creek without a paddle
thanks in advance
You can try sp_attach_single_file_db instead of sp_attach_db. That is still
not guaranteed to work in this scenario though, it is only _guaranteed_ to
work if you explicitly detach the database, but you might be lucky.
Otherwise you will have to restore from the back up.
Jacco Schalkwijk
SQL Server MVP
"Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> Ok this morning one of the IT guys deleted the LDF file
> from the server for a particular database. The file was
> 45 gig, he stopped the server then deleted the file,
> without detaching the database.
> We tried running sp_attach_db @.dbname='', @.physname=''
> filling in the blanks but that refused to work.
> We still have the 65 gig MDF file but we get error 9004
> when we try to attach using enterprise manager.
> We saw a knowledge base article saying to install service
> pack 3a will this solve the problem, don't necessarily
> want to mess about with these things unless absolutely
> necessary
> I will be very grateful is someone tells me how to sort
> this and doesn't say i'm up the creek without a paddle
> thanks in advance
|||You also need to seriously suggest firing that IT guy...What he's done
really pissed off DBAs!
"Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> Ok this morning one of the IT guys deleted the LDF file
> from the server for a particular database. The file was
> 45 gig, he stopped the server then deleted the file,
> without detaching the database.
> We tried running sp_attach_db @.dbname='', @.physname=''
> filling in the blanks but that refused to work.
> We still have the 65 gig MDF file but we get error 9004
> when we try to attach using enterprise manager.
> We saw a knowledge base article saying to install service
> pack 3a will this solve the problem, don't necessarily
> want to mess about with these things unless absolutely
> necessary
> I will be very grateful is someone tells me how to sort
> this and doesn't say i'm up the creek without a paddle
> thanks in advance
|||Common error. Look at the suggestion by Jasper Smith here
(http://tinyurl.com/5g2ol). Note that rebuilding the log this way is not
supported by Microsoft, and you should make a copy of the mdf file just in
case it does not work for you. Good luck.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Use MiniSQLBackup Lite, free!
"Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
> Ok this morning one of the IT guys deleted the LDF file
> from the server for a particular database. The file was
> 45 gig, he stopped the server then deleted the file,
> without detaching the database.
> We tried running sp_attach_db @.dbname='', @.physname=''
> filling in the blanks but that refused to work.
> We still have the 65 gig MDF file but we get error 9004
> when we try to attach using enterprise manager.
> We saw a knowledge base article saying to install service
> pack 3a will this solve the problem, don't necessarily
> want to mess about with these things unless absolutely
> necessary
> I will be very grateful is someone tells me how to sort
> this and doesn't say i'm up the creek without a paddle
> thanks in advance
|||> You also need to seriously suggest firing that IT guy...What he's done
> really pissed off DBAs!
Or fire the IT manager who allow for non-trained personnel have this kind or privileges on a database
server... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:eiYHCg2jEHA.4068@.TK2MSFTNGP10.phx.gbl...
> You also need to seriously suggest firing that IT guy...What he's done
> really pissed off DBAs!
>
> "Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
> news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
>
|||I wouldn't sack anyone for pissing of DBAs. Putting 65 GB of business data
at risk is a different matter though... not to mention the downtime and the
extra work involved.
Jacco Schalkwijk
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uWLfBT4jEHA.1404@.TK2MSFTNGP09.phx.gbl...
> Or fire the IT manager who allow for non-trained personnel have this kind
> or privileges on a database
> server... :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Richard Ding" <rding@.acadian-asset.com> wrote in message
> news:eiYHCg2jEHA.4068@.TK2MSFTNGP10.phx.gbl...
>
|||Well they managed to get it up and running with only a 2 week loss of data,
so that was good but they didnt get any sleep doing it, got it running the
next morning, not sure how they did it, but they did, luckily
think the backups are been re-thinked, lol
A day researching was different i s'pose
thanks for the suggestions
"Peter Yeoh" <nospam@.nospam.com> wrote in message
news:ekAqO$2jEHA.596@.TK2MSFTNGP11.phx.gbl...
> Common error. Look at the suggestion by Jasper Smith here
> (http://tinyurl.com/5g2ol). Note that rebuilding the log this way is not
> supported by Microsoft, and you should make a copy of the mdf file just in
> case it does not work for you. Good luck.
> --
> Peter Yeoh
> http://www.yohz.com
> Need smaller SQL2K backups? Use MiniSQLBackup Lite, free!
>
> "Steven Scaife" <anonymous@.discussions.microsoft.com> wrote in message
> news:08b501c48f52$f1c64690$a401280a@.phx.gbl...
>