Thank you Gail. I am learning.

We had faced a similar problem with SSIS (64 bit system )and hence the link. Reducing the max server memory settings solved our issue

Thanks Gail, for clearing my misunderstanding.

Regards

SQL Server "max server memory" controls only th BufferPool memory. SSIS, LOB data,CLR process, SQL Agent process etc, do not use BufferPool memory of SQL Server. They use what is...

Accepted that his is not going to reenable the indexes.

But since krishnaroopa has mentioned that he has disabled two indexes by mistake. This implies that othe indexes might exist, and...

Have TABLOCK hint placed on the table.

This will be minimally logged.

http://msdn.microsoft.com/en-us/library/ms190422(v=SQL.90).aspx

DISTINCT performs a implicit SORT. You can check the query plan.

When SQL Server finds that there is not enough memory to perform SORT it spills it to tempdb.

Whenever data is...

Try Updating statistics of all tables with full scan

Enable TRACE FLAG 1222 . This will output the deadlock trace to SQL Server log file.

Try to understand why it occured.

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

Check for Process:Working set counter for each SQL server instance process. If this value is less than SQL Server's Memory Manager:Total Server memory counter , than you have an...

During backup was there any huge DML task going on.

during recovery,When the waittype is suspended, this indicates that, data is being spilled to tempdb during recovery. Hence resulting in a...

Linked servers per se are not bad when you want to pull small amounts of data.

Second point is when you are having a explicitly defined transaction in distributed transaction...