Sorry!

May be I misread your info...

Yes it is not supported for Windows 2000 Server edition...

Either you upgrade your OS to Advanced Edt.. or don't use it...

First you kill all the users from that db before you start your restore...

Overwirte option will not kill the users from the db...

Run the sp_who and check if any users...

Thanks Anders Pedersen for sharing your exprience..

SQL server EE (64 bit)

Data and Log file serperation (Raid 10)... but some SANs may give the same performance even the data and log files on the same drive based...

Interesting...

Did you check system log for any disk errors?

If there is no HW issue, may be option will be calling PSS...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=179518

You can create the index on system tables but can't be drop index and you can't run DBCC DBREINDEX against system tables too..

What table is system table index got corrupted?

You can...

Microsoft forbid using the /3Gb switch with Windows 2000 Server.

You can use /3gb switch in Windows 2000 too...

http://www.microsoft.com/technet/prodtechnol/exchange/Guides/E2k3Perf_ScalGuide/e834e9c7-708c-43bf-b877-e14ae443ecbf.mspx?mfr=true

I don't know Express edition has this feature or not but it has very few features compared to other editions..

Check the following article...

http://www.sqlservercentral.com/columnists/bknight/comparisonofsqlserver2005editions.asp

Yes..

sp_rename is not using any DDL statements so that it is not covered.. May be Next Version may cover it..

Yes..

sp_rename is not using any DDL statements so that it is not covered.. May be Next Version may cover it..

Did you try import and export wizard from SSMS?

Is your issue resolved?

Run the profiler to check exactly what is happening...

There might be no rows in the text file or your db connection might be configured to different server?

You can find the meaning of the trace events in the profiler itself when you click on the event at the bottom it will tell what it is...