Model database marked as suspect now unable to attach

  • I have a sql server that had a model system database marked as suspect. The server was rebooted while the state was recovering. To troubleshoot I detached the model database and than tried to attach it. When I run sp_attach_db I get this error 'A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)' while sqlservr was started with the -f -t3608 startup parameters.

    The model database is not in sys.databases and I get this in the error logs:

    2010-02-16 15:55:40.10 spid8s Could not find database ID 3. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred.

    It seems to me that the model database is detached but there is some reference to the model database that had an id of 3.

    Any help would be greatly appreciated.

  • The model DB is essential for SQL's operation, it's used to recreate tempDB. SQL cannot start without the model DB.

    Check Books online, I'm sure there's something in there about restoring model from backup. Otherwise, consider rebuilding the master DB. I think it'll rebuild model at the same time. You will lose all login information (unless you have a backup of master) but it'll enable you to get SQL up and running.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Here's the link you need to rebuild them: http://msdn.microsoft.com/en-us/library/dd207003.aspx

    Never, never, never detach a suspect database.

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • Does the fun ever stop? while rebuilding the system databases I get this exception message

    Exception type: Microsoft.SqlServer.Setup.Chainer.Workflow.NoopWorkflowException

    Any thoughts?

  • No idea. At this point you should call Product Support to help you.

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply