"Andrea Montanari" <andrea.sqlDMO@virgilio.it> wrote in message
news:46jfktFb8v30U1@individual.net...
> hi,
> SAC wrote:
> > I'm using MSDE. Don't know much yet...just a beginner.
> >
> > What is my doc.mdf?
> >
> > I think I did find out why it doesn't like what I'm doing...when I
> > installed MSDE I changed the default data directory to D:\My Doc....
> >
> > It might have something to do with that..but I don't know what to do
> > about it.
> >
> > Any more ideas?
>
> as Jens already pointed out, database are not only a physical "thing" on
> your file systen, but they are logically registered in the SQL Server/MSDE
> instance too in the system databases... if you only delete the physical
> files, the database will still be "registered" and of course will be
marked
> as "suspect" as the engine will be no longer able to locate the relative
> physical files..
> run oSql.exe
> (
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q325003) and
> execute, at the command prompt
> 1>SELECT Name FROM dbo.sysdatabases WHERE DATABASEPROPERTYEX(Name,
'Status')
> = 'SUSPECT';
> 2>GO
> the name of the database you physically dropped should be listed..
> execute then
> 1>DROP DATABASE x;
> 2>GO
> where x is the name you should be prompted with..
> 1>QUIT
> leave oSql.exe..
> this way you cleaned the orphan database...
>
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
>
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org > DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> --------- remove DMO to reply
>
>
