Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't Install AdventureWorks

Status
Not open for further replies.

CodeJunkee

Technical User
Joined
Jan 8, 2003
Messages
5
Location
US
I have just installed SQL 2005 and it is up and running but I can't get the AdventureWorks DB to install. I have tried the Setup Install, uninstall, Re-install, uninstall, and install from downloaded .msi versions. All produce the same results. The DB does not appear in the list of DBs in the Management Studio, so I try to attach the DB. I get the following error:

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

Yet when I try to run this command, or a CHECKDB against 'AdventureWorks' I get:

"Could not locate entry in sysdatabases for database 'AdventureWorks'.
No entry found with that name. Make sure that the name is entered correctly. "

It does not seem to know the db is there or let me get to it. How do I get the sample db installed?

 
Try to query the sys.databases table and see what it says. It's the definitive souce as to what databases are on the system.

How are you attaching the database? Where did you get the mdf and ldf from?

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
I have queried sys.databases and it is not there. I have tried both the installs from the setup and the downloaded .msi files. Neither automatically attach the dbs. I ran attach from the Server Management Studio and it produces the errors I reported above. I later installed the older Pubs and Northwinds DBs with no problem, not something is failing in the AdventureWorks db.
 
Well, I think I found the solution. There was MSSQL Instance of the machine from and MSDE install for the Veritas Backup program. I uninstalled MSSQL 2005, turned off all the MSSQL services, and Veritas Backup Services, and reinstalled SQL 2005. I also, gave in a Custom Instance name instead of default (to distinguish it from the Backup Instance). Now the AdventureWorks Sample DB comes up and running, and I have no more remote access problems.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top