But why would you need a backup? I mean, it's not as if a disk will fail, or someone drops a table (or the entire database) or the data file...

You need brackets around the parameter to the exec.

EXEC @sql -- SQL assumes that @sql contains he name of a stored procedure

EXEC (@sql) -- SQL will execute the contents of...

I don't think there is a comprehensive book, as much of the internal workings, the costing algorithms etc, as far as I know are not public knowledge.

There's a large...

Why on earth is there no backup?

Please run this and post the full and complete output.

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Without a database backup, the database cannot be recovered...

If you're happy with rebuilding and losing all your jobs, job history, backup history, etc, then go ahead. If not, I can help you rebuild the log.

Would you mind...

Open in management studio, change the database name (if necessary) and execute.

You are aware that this is just a script of the structure of the DB? There's no data included...

The error log is a text file. Just do a search for it in the OS, it'll be called ERRORLOG.

We can probably do an emergency mode repair and rebuild...

Developer edition is the full enterprise edition features with a non-production licence, so you lose nothing in the way of features by using it.

If you still have problems, some...

You need...

No. From what I heard, they found it not commercially viable, hence...

Enterprise edition is not supported on non-server operating systems. It's only supported when running on Server 2003/2008/2008 R2. Not Windows 7.

Why are you using Enterprise edition? If it's for development,...

Great. CheckDB will take a while, so don't run it when the server is in use.

There are three I know of.

Apex Sql Log Reader

Lumigent Log Explorer

Quest Log Reader

None of them are free. I don't know the price of the quest one, but when I check...

Please post table definitions, sample data and desired output. Read this to see the best way to post this to get quick responses.

http://www.sqlservercentral.com/articles/Best+Practices/61537/

Read everything you can find. Try things out until you understand them (not on the production server). Read more. Practice. Read. Repeat for a few years