I get an error when I try to attach the sample database.

IceThatJaw · December 22nd, 2011, 12:35 AM

This the error I get:

TITLE: Microsoft SQL Server Management Studio
------------------------------

Attach database failed for Server 'TEST-SERVER'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdN...r&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Directory lookup for the file "E:\Data\SqlServer\2008Express\MSSQL10.SQL2008EXPR ESS\MSSQL\DATA\PlanetWrox_log.ldf" failed with the operating system error 3(The system cannot find the path specified.). (Microsoft SQL Server, Error: 5133)

For help, click: http://go.microsoft.com/fwlink?ProdN...3&LinkId=20476

I tried attaching both MDF files to my local connection in SQL Server 2008.

P.S.- Is LINQ really the way to go? Should I focus on learning and using that for my database communication or is it just as good to use SQLSourceAdpaters and plain old SQL?

EDIT - Nevermind, I just had to delete the log file to get it to load. My second questions still stands though, and I am really getting into this book. It's so useful!

Imar · December 23rd, 2011, 04:15 AM

Quote:

P.S.- Is LINQ really the way to go? Should I focus on learning and using that for my database communication or is it just as good to use SQLSourceAdpaters and plain old SQL?

IMO, it is. Especially with the new Code First option, EF gives you a clean yet accessible approach to data access. However, it may not fit in every application. If you need more control over generated SQL for example, you may still want to use direct ADO.NET such as SqlConnection and SqlDataReader objects. I use EF for the majority of the projects I am involved in.

Cheers,

Imar