data base in suspend mode

Hi,
In my sql7 the msdb and one user database are both in suspect mode. This is
the state for several hours so I can assume it will not change.
I suspect the user database is causing msdb to get in suspect mode.
However, I am looking for the information regarding the option to force the
bit causing the suspect mode which will then change the mode.
Thanks,
YancoYaniv,shalom
If you have backup of these databases I'd recommend you to restore it.
Also you can reset the status of suspect database by
UPDATE master..sysdatabases SET status = status ^ 256
WHERE name = 'Database_Name'
Note: It's strongly not recommended to update system tables.
"yaniv" <yanive@.nice.com> wrote in message
news:e7DOr#fnDHA.1708@.TK2MSFTNGP12.phx.gbl...
> Hi,
> In my sql7 the msdb and one user database are both in suspect mode. This
is
> the state for several hours so I can assume it will not change.
> I suspect the user database is causing msdb to get in suspect mode.
> However, I am looking for the information regarding the option to force
the
> bit causing the suspect mode which will then change the mode.
>
> Thanks,
> Yanco
>|||Thanks,
I did not have a recent backup of the user database.
I used sp_configure to allow update to system tbls and then sp_resetstatus
and it did the job for both databases, the next time sql srv started the
status was normal.
I will latter look into the log files try understanding the cause to the
problem.
--
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uUQKyCgnDHA.708@.TK2MSFTNGP10.phx.gbl...
> Yaniv,shalom
> If you have backup of these databases I'd recommend you to restore it.
> Also you can reset the status of suspect database by
> UPDATE master..sysdatabases SET status = status ^ 256
> WHERE name = 'Database_Name'
> Note: It's strongly not recommended to update system tables.
>
> "yaniv" <yanive@.nice.com> wrote in message
> news:e7DOr#fnDHA.1708@.TK2MSFTNGP12.phx.gbl...
> > Hi,
> >
> > In my sql7 the msdb and one user database are both in suspect mode. This
> is
> > the state for several hours so I can assume it will not change.
> >
> > I suspect the user database is causing msdb to get in suspect mode.
> >
> > However, I am looking for the information regarding the option to force
> the
> > bit causing the suspect mode which will then change the mode.
> >
> >
> >
> > Thanks,
> > Yanco
> >
> >
>

Data & Log File Location on RAID 5

Hi! I searched for an answer on this, but did not find exactly the info I am looking for . . .

With SQL 2005 I assume it is still appropriate to put data and logs on separate physical drives for best performance. However, I have only one RAID 5 for data and logs. Does it help to put these on separate partitions on the same array for data and logs or should I not even bother since it won't be separate physical disks? Thanks!

Matt, I'm moving your thread to the Database Engine forum where I think you'll get a faster answer.

-Jeffrey