Log files don't belong to any filegroups. But if you mean original log file that was created when the db was created, according to my testing (SQL 2000) it's not possible...

What recovery model do you use?

If simple you can run

backup log db_name with truncate_only

this removes all inactive transactions from the log

if you use full or bulk_logged model perform...

As far as I know emergency mode opens database without transaction log which implies that you cannot make any changes to the data.

So you can run dbcc checkdb only without repair clauses....

Can you determine what the reason for suspect status is? Inspect Windows and SQL Server logs for error messages, also check there's enough free space on disks holding the database.

I'm sorry to say that you made a mistake. You should have rename db files and attach as FSPRD and everything would be ok. Now you have got sysfiles and...

You can't do that. Instead, place your log file on RAID 1 (mirrored) drive - thus you are protected against single media failure. To be able to recover as much data...

What I wanted to suggest was to put db into emergency mode and try to get out as much data as possible. You've already done that to no avail. I...

Have you got any good backup that you can go back to? From what you posted I assume that you don't. What is the status of the db? Can you...

see this article from MS:

http://support.microsoft.com/kb/253817/EN-US/

I agree with you that this topic is not very well covered. I found the following article quite helpful:

http://vyaskn.tripod.com/moving_sql_server.htm

sp3 and sp3a are equivalent in this case. Apply sp3a to test machine and restore will succeed. Be aware of some other things to consider. if you have a different disk/directory...

Just my experience from a couple of years ago. I had problem with CXPACKET waittype in my DWH processing (loading data to Analysis services from 100 million row table). It got...

First of all you need to determine the cause of suspect status. What are messages in SQL Server error log on server startup or during detach/attach? Are there any messages in Windows...

2195 is OS build

@@version output starts like this:

Microsoft SQL Server  2000 - 8.00.760 (Intel X86)

where 760 denotes SP3 in my case

or you can use

select serverproperty('productlevel')

If I remember correctly @@servername relies on master..sysservers table. Can you examine its contents? There should be at least one row holding info about local server (isremote column=0)