Comments on: SQL SERVER – Fix : Error Msg 1813, Level 16, State 2, Line 1 Could not open new database ‘yourdatabasename’. CREATE DATABASE is aborted.

By: subin

subin — Sun, 23 Aug 2009 17:13:40 +0000

Hi Pinal Sir,

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

By: Mark Plumpton

Mark Plumpton — Fri, 07 Aug 2009 01:45:40 +0000

The solution posted by Howard (1-apr-2008) worked for me on SQL 2008.

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

By: Bruwer

Bruwer — Wed, 05 Aug 2009 07:06:39 +0000

Hi Pinal

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

Thank you

By: Isuru

Isuru — Tue, 30 Jun 2009 08:45:33 +0000

Dear Pinal,

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 -

By: Christine

Christine — Mon, 08 Jun 2009 07:10:00 +0000

hi,

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

By: SANTHOSH

SANTHOSH — Wed, 20 May 2009 15:07:40 +0000

thanks for this guidance , its really superb and very easily one.
thank u very much

By: Babu

Babu — Sat, 21 Mar 2009 06:31:20 +0000

I have problem with MSSQL, i can’t attaching the DB… the error massege
Error 1813: Could not open new database ‘name of database’. CREATEDATABASE is aborted. Device activiation error. The physical file name ‘c:\program files\Microsoft SQL Server\MSSQL\data\name of database_log.LDF’ may be incorrect.
please help me………

By: Babu

Babu — Sat, 21 Mar 2009 06:30:09 +0000

By: husain

husain — Fri, 27 Feb 2009 11:05:27 +0000

Thank you very much. This exactly a perfect solution. You safe me today.

Regards
ucin

By: JR

JR — Tue, 24 Feb 2009 03:17:46 +0000

THANK YOU!!!!!!!!!!!!! I LOVE YOU MAN!!!!!!!!!!!!! You saved my life. You are AWESOME AND DESERVE A GOLD STAR!!! If I knew your address I would send you cookies and wine and some other goodies.

By: Tommy

Tommy — Thu, 19 Feb 2009 22:27:25 +0000

At:

DBCC TRACEON (3604)
DBCC REBUILD_LOG(yourdatabasename,‘c:\yourdatabasename_log.ldf’)
GO

I get an error:

The database could not be exclusively locked to perform the operation.

I’ve tried forcing the db into Single User mode and still nothing. The log does not get created.

Any ideas?

By: Arthas

Arthas — Tue, 13 Jan 2009 03:43:44 +0000

Many thanks for your great tutorial :) !

By: rodoss

rodoss — Fri, 26 Dec 2008 06:16:26 +0000

5. change below code and work perfectly! Thank you!

BEGIN

BEGIN TRAN

By: john

john — Thu, 11 Dec 2008 21:59:56 +0000

I got this error when attaching a db that has multiple log files, can I do the same process? Should I add the additional log file when I create the new db?

By: Todd

Todd — Fri, 07 Nov 2008 21:50:16 +0000

Hi,

Thanks for the post. It worked great.

By: Patrick

Patrick — Tue, 30 Sep 2008 15:07:30 +0000

Hi,

Thank you very much for this procedure – I have successfully implemented on a damaged DB.

Just for the records, this procedure also works on MSSQL 2000.

Thanks
Patrick

By: Luca

Luca — Thu, 25 Sep 2008 07:37:28 +0000

Hi,
THANKS! You saved my life!!!!

Just one thing:
Instead of point 10, I run

sp_DBOPTION ‘yourdatabasename’, ‘dbo use’, ‘false’

and

sp_DBOPTION ‘yourdatabasename’, ’single user’, ‘false’

Ciao!

By: chris

chris — Mon, 01 Sep 2008 06:04:46 +0000

Hi, I experience the same problem as described and I able to recover the database using the step recommended by Howard above. The database is working for a while.

However, when i try to connect the database from my program, i encountered the following error:

Msg 211, Level 23, State 51, Line 1
Possible schema corruption. Run DBCC CHECKCATALOG.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

Trying to run the DBCC CHECKCATALOG return no error.
Any idea?

Thx.

By: notquiteanewbie

notquiteanewbie — Tue, 26 Aug 2008 15:42:06 +0000

I had this same error. Turns out the mdf file was READ ONLY. After unchecking READ ONLY, I was able to attach my database on SQL 2005 SP2.

By: zlatan24

zlatan24 — Fri, 11 Jul 2008 09:30:11 +0000

There is fine tool-sql mdf recovery,repair data from corrupted databases in the MS SQL Server format (files with the *.mdf extension), can process huge databases, their file size can reach 16 TB, supports data extraction via the local area network, you can save recovered data as SQL scripts, it is also possible to split data into files of any size, can save extracted information directly to the SQL server. It allow to recovery SQL Server faster.