Can't delete orphaned Mirror because the principal server is decommissioned

Hoping someone can help me with this. I have a SQL 2005 box which was
formerly in a '2005 mirror.' The SQL server containing the
'principal' is now dead (ceased to exist). That is not the problem.
The problem is that I now want to delete the mirror as it is no longer
needed. The status of the mirror is 'Disconnected / In Recovery.'
Problem is that when I try to delete it, I get the message "Database x
is enabled for Database Mirroring, Database Mirroring must be removed
before dropping the database. (Microsoft SQL Server, Error: 3743).
O.K., this is another fine mess you've gotten me into Olly.... Ho do I
delete the 'mirroring relationship' if the server containing the
Principal has 'gone to a better life?' Until I work out how, I will
have to just ignore it and continue to put he server into production.
Not a great option. Thanks in advance.On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> Hoping someone can help me with this. I have a SQL 2005 box which was
> formerly in a '2005mirror.' The SQL server containing the
> 'principal' is now dead (ceased to exist). That is not the problem.
> The problem is that I now want todeletethemirroras it is no longer
> needed. The status of themirroris 'Disconnected / In Recovery.'
> Problem is that when I try todeleteit, I get the message "Database x
> is enabled for Database Mirroring, Database Mirroring must be removed
> before dropping the database. (Microsoft SQL Server, Error: 3743).
> O.K., this is another fine mess you've gotten me into Olly.... Ho do Idel
etethe 'mirroring relationship' if the server containing the
> Principal has 'gone to a better life?' Until I work out how, I will
> have to just ignore it and continue to put he server into production.
> Not a great option. Thanks in advance.
Here is what I have done with this. I know it is not nice but it has
partially worked. I simply stopped SQL server, renamed the mdf file
and restarted the server. This has worked. I actually thought I
would have to still delete the artifact of the database in a 'suspect
state.' But I didn't even have to do this. It was just gone. One
problem - though - the event log still contains an error "FCB::Open
failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
for file number 1. OS error: 2(error not found)." Anybody have any
ideas of how I can get rid of this?