2. Stop SQL Server. Move original MDF file from older server (or location) to new server (or location) by replacing just created MDF file. Delete the LDF file of new server just created.

3. Start SQL Server

Could not open FCB for invalid file ID 0 in database ‘Local1′.

Turns out that after running:

SELECT *
FROM sysdatabases
WHERE name = ‘yourdatabasename’

the database (MDF) file we thought was mounted was not, so we stopped the SQL services and renamed the file to match the one in the record produced by the query directly above this paragraph.

Also, we executed step number 10 before 9 because of a permission issue.

Thank you. Om Shanti Om.

ref:wavedrop

Connection Broken
We had tried checkdb with repair allow data loss but did not help. I don’t have good backup also.
Please suggest

Thank you

Connection Broken
We had tried checkdb with repair allo data loss but did not help. I don’t have good backup also.
Please suggest

Thank you

DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Msg 2526, Level 16, State 3, Line 2
Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options.

Do you have any solution???
Thank in advance

I am logged in as user sa still it gives me error while updating sysdatabases as “Ad hoc updates on system tables are not allowed”.

Due to this i cannot set my database in emergency mode, my production database’s log file is corrupted and it is not allowing me to attach mdf file to create .ldf file.

I tried the process mentioned by you but updating system table is not allowed, i tried in sql server management studio express 2005 and also in sql server management studio 2005 but same error is popped out. I also tried by creating a user with all privileges but still i didn’t work

Please can u help me to re-build ldf file since it is my production database and it needs to be sorted out fast.

Your response will be appreciated………..

Thanks in advance.

Due to this i cannot set my database in emergency mode, my production database’s log file is corrupted and it is not allowing me to attach mdf file to create .ldf file.

I tried the process mentioned by you but updating system table is not allowed, i tried in sql server management studio express 2005 and also in sql server edition 2005 but same error is popped out.

Please can u help me to re-build ldf file since it is my production database and it needs to be sorted out fast.

Your response will be appreciated………..

Thanks in advance.

Best Regards!
Jesus

By the way, it’s now 10:50PM at the office. LOL!

I’m sorry, please help me.

When I do step ‘—-Following statement will update only one row in database’

I found message “Msg 259, Level 16, State 1, Line 3
Ad hoc updates to system catalogs are not allowed.”

I don’t know what ‘s happen?

Best regards,
Surachai S

Followed steps above – However when I try and query data table I receive error below

Server: Msg 823, Level 24, State 2, Line 1
I/O error (torn page) detected during read at offset 0x0000005ec80000 in file ‘C:\Program Files\Microsoft SQL Server\MSSQL\data\Deal.MDF’.

Connection Broken

If I try and open tables through Enterprise Manager Receive message

Error 601 Could not continue scan with NOLOCK due to data movement

Would you have any ideas ?

Thanks

This is simply great!!
Your solution helped us to recover from a serious matter.
Really thx a lot.

Keep up the good work pal.

Regards,
Dinesh Hettiarachchi.

To fix this issue login with admin privilege and execute below statements:
SP_CONFIGURE ‘ALLOW UPDATES’, 1
GO
RECONFIGURE WITH OVERRIDE
GO

Regards,
Pinal Dave

Server: Msg 259, Level 16, State 2, Line 1
Ad hoc updates to system catalogs are not enabled. The system administrator must reconfigure SQL Server to allow this.

Please your advice.
Thanks

thank you very much for this solution !!! It was very useful for us … and perhaps it is possible for you to integrate the things which Jim Rickards responses!

Wish you success and all the best for 2010!

Bob

Thank you very much for this article.Thanks a lot…
The best by the test

I had also got the ‘Ad hoc updates to system catalogs are not allowed’ message with Pinal’s script

Thank you very much indeed for writing such a clear an concise article about a very technical matter. Well done :)

Thank you

Thank you very much for this article. I could save a lot of job details for a whole week in a technical company, who has not backed up their database for long time.

This worked me fine.

I appreciate you for writing these kind of stuff.

- Thanks -

I encounter the following error when execute the steps at

DBCC REBUILD_LOG(‘Local1′,’c:\Local1_Log.ldf’).

Error msg:
Server: Msg 5180, Level 22, State 1, Line 1
Could not open FCB for invalid file ID 0 in database ‘Local1′.

Connection Broken

I could not proceed, do you have any suggestion?
Thx a lot