"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Replace the C:\Data\***.mdf and the C:\Data\***.ldf lines above to where your .mdf and .ldf is stored on your computer. If it complains about AdventureWorks2008 already existing, try the following first:

USE MASTER
GO
DROP DATABASE [AdventureWorks2008]

Good luck!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Q1: If you can query the database then its attatched. If you want to ensure that there is not any corruption run DBCC CHECKDB against it.

Q2: In the windows you have supplied it is giving the error "Operating System Error 2: The system cannot find the specified file.". This is the issue, the supplied path is incorrect. If you look at the path it ends in just Documents.

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Re:> awarren85 Q2 solution
Most likely this solution would work. But I will prefer a solution with a less chance of harming or corrupting the SQL Server installation where I have to re-install it again. At first, I will try a solution I can have my arms around it so to speak.

Re:> PatelAlpesh comment
Two out of three databases have been attached properly. So, the user permit is less likely the cause of the error.

Re:> EvilPostIt posts
On Q1, what is the step by step procedure to run DBCC CHECKDB to detect corruption?

On Q2, in folder "C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\Documents" I have:

Now, is it possible because it (Documents folder) wasn't there on the first try; therefore, something got corrupted? And, unless its effect is gone it will keep giving some error unless it is corrected. It is a wild shot but doesn't hurt considering it.

I like your approach because I am beginner so therefore more comfortable with it at this point.