Run it and gets its execution characteristics via Profiler (or server-side trace)

http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/

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/

What you've said there is in violation of the exam NDA agreement that you accepted when you wrote...

Just an addendum, now that the crisis has passed...

From what I saw in the list of indexes, you may have a few too many indexes on that table (though too...

Good to hear. Just to be sure that there's no lingering damage, please run this

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

That's a lot more complex than just adding a second instance and moving the 3 DBs there, as has been earlier recommended.

Errr, no.

What allows for log space reuse in Simple recovery...

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/

Password change?

You need a trigger or a trace. It's not something that SQL keeps track of itself.

If you can give more detail on what you want, I can give you better...

Is google down today?

http://msdn.microsoft.com/en-us/library/ms190273.aspx

There are several examples at the bottom

I would recommend just restoring from your backups. While this may complete (or may not) it may cause data loss, transactional inconsistencies, structural inconsistencies or other similar problems.

Emergency mode repair...

I'm going to call that complete garbage and dangerous information.

While service...

mahesh.vsp (1/23/2010)

---

I thought, whenever i say SIMPLE recovery model, when log file reaches 70-80% , then automatically overwrittes the LOG file but it is not happended and result in

LOG FULL...

The resource database, especially in SQL 2008, should be treated as if it were a binary file, a .dll file or the like. It should not be moved, messed with,...