That was how exactly I have configured the datasource in the report manager.

Yes, U R correct in spotting out on the CD Setup. It was by defaultly set up...

/****** Object: LinkedServer [DataServerSeven] Script Date: 07/11/2012 10:02:40 ******/

EXEC master.dbo.sp_addlinkedserver @server = N'DataServerSeven', @srvproduct=N'MSSQL', @provider=N'SQLNCLI', @provstr=N'PROVIDER=SQLOLEDB;SERVER=tcp:XXXXXXXXXXX\xxxXXXXXXXXXX,58660'

/* For security reasons the linked server remote...

I have dropped and recreated the linked server. Still the same error no change.

As of now we have increased the primary file allocation from 5 GB to 6GB. have to follow up with the queries that users fire on this sql instance to...

We have all 4 system databases on a mount point in which only 43 GB is used and 956 GB is free. Please advice what to do here to avoid...

The services come online on all the nodes except node 7. I found the bottle neck. Its the corrupted NIC drives not allowing the services to communicate with the node....

No worries. I also learned everything online only. I'm not amused by your question. I agree it can be read online. Anyways here a nice link. hope you will have...

Thanks Evil for your input.

Yes we can use TablockX but this might increase the granularity level of the lock. The other query has to wait until the current query...

I did a little investigation back on my server. Please find the details below and suggestions are open.

Query1:

UPDATE [dbo].[WorkQueue]

SET WorkQueueStatus = 'DataLoaded'

, WorkQueueStatusDate...

Can anyone please update me on the above issue, Please.

I need to give a detailed update before the day close

I just wanted to figure out. which SPID is killing/Suspending the 100,77,70,71.

I see the query UPDATE [dbo].[WorkQueue]

SET WorkQueueStatus = 'DataLoaded'

WorkQueueStatusDate = GETDATE()

WorkQueueStatusUTCDate = GETUTCDATE()

WorkQueueEndWorkDate = GETDATE()

WorkQueueProcessingMSG = 'DataLoaded: '...

thanks a lot for input Gail:

So that was the suspended Job. Can I know who suspended it? Please find the Log below.

Date,Source,Severity,Message

04/04/2012 10:41:55,spid20s,Unknown,waiter id=process5863048 mode=IX requestType=wait

04/04/2012 10:41:55,spid20s,Unknown,waiter-list

04/04/2012 10:41:55,spid20s,Unknown,owner id=process184bc8508 mode=S

04/04/2012...

Thanks a lot for your input Evil:

I just encountered another deadlock. I saw the logs and it said that SPID 77 is suspended. Then I ran sp_who2 to find out...

Thanks a lot Evil: I will try to locate the that particular Update statement on Workqueue table.

But we have 17 jobs getting kicked of every 5 mins and all jobs...

Thanks a lot Gail.

Analysis:

So, SPID 76, 91 and 85 are involved in Deadlock occurrence and are supending each other.

Three jobs are potentially running at the same time.

Question: How would...