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

DataAdapter.Update Method Question.

Hi,

I am trying to use DataAdapter.Update to save a file stream into SQl Express.

I have a dialog box that lets user select the file:

openFileDialog1.ShowDialog();

I want to put

openFileDialog1.OpenFile();

Into

this.documentTableAdapter.Update(this.docControllerAlphaDBDataSet.Document.DocumentColumn);

I am thinking that it might just be some syntax issue, but I looked online, and didn't find much answers.

Thanks,
Ke

Take a look on the links I posted here:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=622943&SiteID=1

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Data Types

I'm creating a windows .net form that has SQL as the back-end. One of the
controls is a group box with three radio buttons options. What data type
should this column have, so whatever option the user chooses will be saved o
n
the SQL table?
Another one, a YES/NO field, what data type should this column have?
--
TSHi TS,
You can use a numeric field and store 1 or 0.
please let me know if u have any questions.
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
---
"TS" wrote:

> I'm creating a windows .net form that has SQL as the back-end. One of the
> controls is a group box with three radio buttons options. What data type
> should this column have, so whatever option the user chooses will be saved
on
> the SQL table?
> Another one, a YES/NO field, what data type should this column have?
> --
> TS|||With three radio buttons you either have three or four options - if you allo
w
none of the options to be selected (maybe as an initial state).
E.g.
null - none selected
0 - first selected
1 - second selected
2 - third selected
etc.
I believe TINYINT could cover that. Look it up in Books Online if you
haven't already.
However, a more humanly-readable aproach would be to use more descriptive
values - make use of enumerations in .Net and map them to a table in your
database if appropriate. After all - this is the 21st century. ;)
ML|||On Thu, 27 Oct 2005 08:26:13 -0700, TS wrote:

>I'm creating a windows .net form that has SQL as the back-end. One of the
>controls is a group box with three radio buttons options. What data type
>should this column have, so whatever option the user chooses will be saved
on
>the SQL table?
>Another one, a YES/NO field, what data type should this column have?
Hi TS,
You're approaching this from the wrong side.
You should first investigate what data is needed for the application
that you are creating. Identify the dependencies and the business rules,
then normalize the data to at least third normal form and create your
tables.
Once that is done, the next step is to create a GUI that makes it as
easy as possible for the user to enter the required data into the
system. For a column where only a few specific options are legal, a
group box with radio buttons might be fine (but so might a textbox with
dropdown). For a column with only two legal values, a yes/no button
might be appropriate (but a checkbox, a dropdown, or a set of two radio
buttons might do as well).
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)