The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HD
D
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
ChrisYou might be able to attach the database files to the new installation. Read
about sp_attach_db.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup
in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old
HDD
> is now visible and accessible. I can now comfortably recover all their dat
a
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:
> You might be able to attach the database files to the new installation. Re
ad about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>|||> Tibor Im curious about your response. You say he "might" be able to attach,">
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously deta
ched from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work".
Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appre
ciate if MS would
provide a technical elaboration about specifically when attach work and when
it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we
see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me.
Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to attach
,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment