From: Henrik Staun Poulsen on
Hi ML,

We have tested a solution:

DROP DATABASE hespo

It works.
So we do not have to resort to the traditional solution: FORMAT C:

I still think that SQL Server is flawed in this respect.
That
alter database hespo modify file (name='hespofg1', OFFLINE);
Requires you to do a DROP Database, if you have no readable backup.

As you can see, I do not quite understand what vt suggests.
But I hope that it works.
Thank you very much for your help.
I'm sure we'll move files the correct way in the future. ;-)

From: B D Jensen on
Hi!
Having a filegroup with only one (big) table or some few tables,
you only disturb users/jobs who are interested in this part of the
database...
Greetings
Bjorn


From: Henrik Staun Poulsen on
Hi ML,

> I guess next time you'll also keep a backup handy somewhere.
Sure, better safe that sorry...
Well, maybe not test servers.
They are just test servers, and can be created from scratch.
Except if management forgets that it's just a test server, and release
it to production...

Thank you for your help.
Henrik

From: Henrik Staun Poulsen on
ML: Yes, I agree.

BTW; Microsoft came back with the same suggestion; Drop Database
when no file backup exists.

And a suggestion about some unsupported features, that we're trying
out on a test-test PC.

Best regards,
Henrik

From: Tibor Karaszi on
I guess emergency mode can be an option, in order to copy over the accessible data to a new
database... Perhaps not practical if you have loads of data...

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Henrik Staun Poulsen" <hsp(a)stovi.com> wrote in message
news:1180442222.307309.314550(a)g4g2000hsf.googlegroups.com...
> ML: Yes, I agree.
>
> BTW; Microsoft came back with the same suggestion; Drop Database
> when no file backup exists.
>
> And a suggestion about some unsupported features, that we're trying
> out on a test-test PC.
>
> Best regards,
> Henrik
>