In my lab setup, I already have a 2 node windows 2012 R2 cluster. I already had one SQL server 2012 instance is working fine without issues. However, when I was trying to install a new additional SQL 2012 instance, the installation reached till the last phase and getting failed with errors related to a cluster resource.
SQL SERVER – AlwaysOn Availability Group Listener – This TCP Port is Already in Use
While doing a preparation of a demo, I encountered below error while creating the listener of the AlwaysOn availability group. I was trying this from Management Studio.
SQL SERVER – How to Reach Out to Cloud – Cloud Computing with PartitionDB
Cloud Computing is not new anymore; everyone is talking about the cloud. Has everyone already touched the sky?
SQL SERVER – Unable to Get Listener Properties Using PowerShell – An Error Occurred Opening Resource
I was engaged with a client for an AlwaysOn project and they had some follow-up questions. I took some time to find the answers and encountered an interesting error. I am sharing them here so that others can get benefited. They informed me that they are not able to see and modify listener properties. Let us learn about this error related to opening resource.
SQL SERVER – Error: 8509 – Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: 0x8004d00e(XACT_E_NOTRANSACTION)
Have you ever seen an issue related to MS DTC, SQL Server and JDBC XA distributed transactions? A client contacted me for help and he wanted my opinion within one hour. They signed up for my On Demand consulting services and we started looking at the server and application.
SQL Server Management Studio (SSMS) – Unable to Connect to SSIS – The Specified Service Does Not Exist as an Installed Service
After installing the latest version of SSMS (17.2), I was not able to connect to SQL Server Integration Services SSIS on my local machine.
SCOM – Alert: SQL Server Cannot Authenticate Using Kerberos Because the Service Principal Name (SPN) is Missing, Misplaced, or Duplicated
This blog explains what needs to be done when there are tools which can monitor and report issue about SPNs. Once a client informed that SCOM (System Center Operations Manager) is connected to the databases on SQL Server and raising below warning regarding the SQL Server (Service Principal Name) SPNs: