One of my clients contacted me for On-Demand support with an interesting situation. Their goal was to move ALL databases from C drive to the E drive. They told me that they have done ALTER for all databases (user and system) but it is not working in the master database.
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 – Wait Stats Collection Scripts for 2016 and Later Versions
Yesterday I posted a blog about a new DMV, which is introduced in SQL Server 2016. You can read the blog post here:Â Get Wait Stats Related to Specific Session ID With sys.dm_exec_session_wait_stats. After reading the blog post, I have received quite a few emails about SQL Server Wait Stats Collection Scripts. One of the question was is my earlier script still valid to collect the SQL Wait Stats for SQL Server 2016 and Later Versions.
SQL SERVER – Get Wait Stats Related to Specific Session ID With sys.dm_exec_session_wait_stats
First thing first, this feature of getting wait stats related to Specific Session ID with sys.dm_exec_session_wait_stats will only work with SQL Server 2016 or later version of SQL Server. If you attempt to run this on earlier versions of SQL Server, you will for sure get an error.Â
What is the Biggest Limitation of ISDATE() Function? – Interview Question of the Week #137
Question: What is the Biggest Limitation of ISDATE() Function?
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: