Post reply

Unable to attach adventureworks db

  • March 31, 2010 at 2:47 am

    #231362

    hello all

    When i was trying to attach adventureworks db on SQL server 2005 developers edition, I got this error message:

    Could not find row in sysindexes for database ID 10, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.

    Could not open new database 'SSISLOGGING'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 602)

    with little searching, i found that there is an issue with the version of sql server.

    I had installed SQL server 2000 first, then on top of it installed SQL server 2005. Both of them developers editions. I realise that 2000 is the main db engine here, so even if I am trying to attach adventureworks through management studio it gives the above error.

    Please suggest any possible workaround so that i can keep both the versions of SQL server and yet attach the db.

    Thanks in advance.

  • March 31, 2010 at 3:09 am

    #1142911

    You can have few instances of SQL Server on the same machine. You can also have each instance with a different version of SQL Server (assuming that you don’t have any instance that is prior to SQL Server 2000), so this isn’t a problem. It seems to me that you are connected to the SQL Server 2000 and you are trying to attach to it a database that was created for SQL Server 2005. This is something that will not work. You have to attach the adventureworks database to the SQL Server 2005 or later.

    Adi

    --------------------------------------------------------------
    To know how to ask questions and increase the chances of getting asnwers:
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • March 31, 2010 at 3:54 am

    #1142934

    Thanks for immediate response.

    I am now able to fix the issue. The issue was certainly due to the version and my utter lack of foresightin not installing the 2005 version as a named instance, as with default instance there was conflict.

    I resolved it by re-installing the 2005 version without uninstalling the previous one, but this time naming the instance.

    My previous dbs were hence untouched and adventureworks db was attached successfully at last.

    Thanks again.

Viewing 3 posts - 1 through 2 (of 2 total)

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