A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated

An error occurred during the execution of xp_cmdshell. A call to ‘LogonUserW’ failed with error code : ‘1385’.

Procedure has no Parameters and Arguments were Supplied.

Sql Server Configuration Manager Remote Procedure Call Failed (0x800706be)

SQL Server Installation Add Features is not Showing All Instances

Today we get a request to install SQL server reporting services for 4 of 8 of the instances on a server.
As usual we pick our sql 2012 dump and start installing. When we reached to Add feature page of installation we were not able to see 4 of 8 instances in drop down as in screen shot

Windows update can't check for updates because the service is not running

Patching does have its own issues, hard to predict

 This time I was doing windows updates

Control panel --> System and security --> Windows update -->check for updates

The image file is valid , but is for a machine type other than the current machine

While patching SQL server 2005 SP1 to SP2, we face below error

Error: The image file is valid , but is for a machine type other than the current machine

This error clearly states that patch file is good, the issue  is with my machines

A file activation error occurred. The physical file name may be incorrect.

EXECUTE permission was denied on the object ‘xp_cmdshell’, database ‘mssqlsystemresource’, schema ‘sys’

Cannot create a row of size XXXX which is greater than the allowable maximum row size of 8060

'Cannot execute as the database principal because the principal "##MS_PolicyEventProcessingLogin##" does not exist

Cannot use special principal dbo

Error: Cannot use special principal dbo: Error 15405

Maximum Stored Procedure, Function, Trigger, or View Nesting Level Exceeded (limit 32)

Failed to run patch request for instance: (exit code: -2068709375) : Single Node Cluster Patching !!

Single Node Cluster Patching

Frequently used DMV's in SQL Server

The media family on device '' is incorrectly formed. SQL Server cannot process this media family

The SQL Server failover cluster instance 'instance name' was not correctly detected. The instance was discovered on the local node but it was not found to be active.

Could not clear 'DIFFERENTIAL' bitmap in database 'database name' because of error 9002

Suspect Pages in database

On Sunday evening we got an opportunity to run DBC checkdb on one of our suspected database (Of course UAT). And as usual we started checkdb from one of sessions on SQL box query analyzer. By the end of the day we realize it will take some more time to complete and we were expecting that by next day some one will kill our connection , while searching on internet we came to know about a table which gives us report of corruption “msdb..suspect_pages”

Cannot insert the value NULL into column ‘owner_sid’, table ‘msdb.dbo.sysjobs’