Database coming up suspect.

Let me tell you the scenario. We are doing the following to ensure we have
the fastest recovery time possible if Windows updates applied to the box
crash it.
When we get ready to apply updates to a box we want to break the driver
mirror by pulling the second drive. That way if the updates we are about to
apply break something we can just put the other drive in. But when we do this
on our test boxes the SQL databases come up suspect. Can anyone help me?
These are the steps we take.
Shut SQL down > Turn off box > Pull drive > turn PC on > log onto windows >
â'Database is now Suspectâ'."Rhild" <Rhild@.discussions.microsoft.com> wrote in message
news:EFF4313C-521D-42F1-895C-5DA19E006470@.microsoft.com...
> Let me tell you the scenario. We are doing the following to ensure we have
> the fastest recovery time possible if Windows updates applied to the box
> crash it.
> When we get ready to apply updates to a box we want to break the driver
> mirror by pulling the second drive. That way if the updates we are about
> to
> apply break something we can just put the other drive in. But when we do
> this
> on our test boxes the SQL databases come up suspect. Can anyone help me?
> These are the steps we take.
> Shut SQL down > Turn off box > Pull drive > turn PC on > log onto windows
> >
> "Database is now Suspect".
>
In theory, if this is all you're doing, it should work. I've done similiar
things.
However, it sounds like you're either pulling the wrong drive, or Windows is
somehow changing the drive letter(s) when you do this.
Check the errorlog for more details.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com

Database coming up suspect.

Let me tell you the scenario. We are doing the following to ensure we have
the fastest recovery time possible if Windows updates applied to the box
crash it.
When we get ready to apply updates to a box we want to break the driver
mirror by pulling the second drive. That way if the updates we are about to
apply break something we can just put the other drive in. But when we do this
on our test boxes the SQL databases come up suspect. Can anyone help me?
These are the steps we take.
Shut SQL down > Turn off box > Pull drive > turn PC on > log onto windows >
“Database is now Suspect”.
"Rhild" <Rhild@.discussions.microsoft.com> wrote in message
news:EFF4313C-521D-42F1-895C-5DA19E006470@.microsoft.com...
> Let me tell you the scenario. We are doing the following to ensure we have
> the fastest recovery time possible if Windows updates applied to the box
> crash it.
> When we get ready to apply updates to a box we want to break the driver
> mirror by pulling the second drive. That way if the updates we are about
> to
> apply break something we can just put the other drive in. But when we do
> this
> on our test boxes the SQL databases come up suspect. Can anyone help me?
> These are the steps we take.
> Shut SQL down > Turn off box > Pull drive > turn PC on > log onto windows
> "Database is now Suspect".
>
In theory, if this is all you're doing, it should work. I've done similiar
things.
However, it sounds like you're either pulling the wrong drive, or Windows is
somehow changing the drive letter(s) when you do this.
Check the errorlog for more details.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com

Database coming up suspect.

Let me tell you the scenario. We are doing the following to ensure we have
the fastest recovery time possible if Windows updates applied to the box
crash it.
When we get ready to apply updates to a box we want to break the driver
mirror by pulling the second drive. That way if the updates we are about to
apply break something we can just put the other drive in. But when we do thi
s
on our test boxes the SQL databases come up suspect. Can anyone help me?
These are the steps we take.
Shut SQL down > Turn off box > Pull drive > turn PC on > log onto windows >
“Database is now Suspect”."Rhild" <Rhild@.discussions.microsoft.com> wrote in message
news:EFF4313C-521D-42F1-895C-5DA19E006470@.microsoft.com...
> Let me tell you the scenario. We are doing the following to ensure we have
> the fastest recovery time possible if Windows updates applied to the box
> crash it.
> When we get ready to apply updates to a box we want to break the driver
> mirror by pulling the second drive. That way if the updates we are about
> to
> apply break something we can just put the other drive in. But when we do
> this
> on our test boxes the SQL databases come up suspect. Can anyone help me?
> These are the steps we take.
> Shut SQL down > Turn off box > Pull drive > turn PC on > log onto windows
> "Database is now Suspect".
>
In theory, if this is all you're doing, it should work. I've done similiar
things.
However, it sounds like you're either pulling the wrong drive, or Windows is
somehow changing the drive letter(s) when you do this.
Check the errorlog for more details.
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com http://www.greenms.com

Data vanishing from SQL Server

Hi,
Please help me to solve the following scenario. We are
working on SQL Server 7.0 on Windows NT Server with Raid
5 . We are using a front end application through which all
the things are done. For the last few days we are finding
that certain sets of transactions are disappearing from
the database totally e.g.
1. Certain books are sold to the customers.
2. Stock is reduced.
3. Delivery instructions are generated from the system.
Say Point 1 & 2 are within same transaction whereas Point
3 is a separate transaction based on the committed transactions of
Point 1 & 2. Now the next day or on
the same day after 3-4 hours we find that all the
transactions are reverted. It is creating a big problem.
Is it problem with SQL Server / Windows NT / Virus / Hardware ?
Please give suggestion.
Thanks in advance.You can tell quite quickly if it is SQL Server by
performing a trace.
NB if it is SQL Server then the cause of this will be
something that your team has put in.
J
>--Original Message--
>Hi,
>Please help me to solve the following scenario. We are
>working on SQL Server 7.0 on Windows NT Server with Raid
>5 . We are using a front end application through which
all
>the things are done. For the last few days we are finding
>that certain sets of transactions are disappearing from
>the database totally e.g.
>1. Certain books are sold to the customers.
>2. Stock is reduced.
>3. Delivery instructions are generated from the system.
>Say Point 1 & 2 are within same transaction whereas Point
>3 is a separate transaction based on the committed
transactions of
>Point 1 & 2. Now the next day or on
>the same day after 3-4 hours we find that all the
>transactions are reverted. It is creating a big problem.
>Is it problem with SQL Server / Windows NT / Virus /
Hardware ?
>Please give suggestion.
>Thanks in advance.
>.
>|||Thanks for the suggestion. But if we run the trace then it will take up
certain CPU time. Apart from that this situation is not happening
everyday. It happens all of a sudden and that is why we cannot simulate
the scenario. Please suggest something more.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||Ok then.
Try setting up some triggers.
These triggers are only activated when data is deleted.
You can then store who or what deleted the data, or even
if it was ever there.
Incidently a trace does not take up much CPU time, try it
out for yourself, on your server set it up so it shows CPU
time, put on a trace, and then see if it has any noticable
difference, I think you will be surprised ;)
J
>--Original Message--
>Thanks for the suggestion. But if we run the trace then
it will take up
>certain CPU time. Apart from that this situation is not
happening
>everyday. It happens all of a sudden and that is why we
cannot simulate
>the scenario. Please suggest something more.
>
>*** Sent via Developersdex http://www.developersdex.com
***
>Don't just participate in USENET...get rewarded for it!
>.
>|||Dipankar,
Could your application possibly be using transactions which never get
committed?
Regards,
Mark
"Dipankar Ganguly" <dipankarganguly@.hotmail.com> wrote in message
news:be8835c2.0312170647.a4e7224@.posting.google.com...
> Hi,
> Please help me to solve the following scenario. We are
> working on SQL Server 7.0 on Windows NT Server with Raid
> 5 . We are using a front end application through which all
> the things are done. For the last few days we are finding
> that certain sets of transactions are disappearing from
> the database totally e.g.
> 1. Certain books are sold to the customers.
> 2. Stock is reduced.
> 3. Delivery instructions are generated from the system.
> Say Point 1 & 2 are within same transaction whereas Point
> 3 is a separate transaction based on the committed transactions of
> Point 1 & 2. Now the next day or on
> the same day after 3-4 hours we find that all the
> transactions are reverted. It is creating a big problem.
> Is it problem with SQL Server / Windows NT / Virus / Hardware ?
> Please give suggestion.
> Thanks in advance.