Can’t connect from SSMS on your own machine to SQL Server in an Azure Virtual Machine? Here is the network-related error users see and what to check to fix it.
SQL SERVER – Script Level Upgrade for Database ‘master’ Failed Because Upgrade Step ‘sqlagent100_msdb_upgrade.sql’ – Error: 5041: MODIFY FILE Failed
One more cause of the script level upgrade failure for ‘sqlagent100_msdb_upgrade.sql’: Error 5041, MODIFY FILE failed. Here is how I fixed it.
SQL SERVER – Full-Text Search Not Working For PDF Documents
A client stored PDF files in a VARBINARY(MAX) column, and Full-Text search could not find text in them. Here are all the steps I used in my lab to make it work.
HRESULT 0x8007138E: The Cluster Resource Is Not Available
HRESULT 0x8007138E, the cluster resource is not available, stopped a SQL Server patch on a clustered instance. The Summary.txt and Detail.txt files led to one failed cluster disk. Removing it from the cluster fixed the install.
SQL SERVER – Fix – Error – Property MemoryAllocatedToMemory OptimizedObjectsInKB is not available for Database. This property may not exist for this object, or may not be retrievable due to insufficient access rights.
The MemoryAllocatedToMemory OptimizedObjectsInKB error popped up while I was teaching a workshop. It is a permissions issue, and one command fixes it.
SQL SERVER – Unable to Repair – SQL_Telemetry_Repair_Startup_Cpu64 gives error – The Service Cannot Be Started
SQL SERVER – Unable to Repair – SQL_Telemetry_Repair_Startup_Cpu64 gives error – The Service Cannot Be Started
SQL SERVER – Create Catalog Error 911: Database ‘SSISDB’ Does Not Exist. Make Sure That he name is entered correctly
Doing create catalog in SSMS failed with Error 911: database SSISDB does not exist. Here is how SQL Server Profiler showed me the real cause.