About us

By

About me – I’m your friendly SQL DBA Siddharth Chauhan. I’m MCSA certified in SQL Server 2016 and have over 11 years of IT experience. In these years I’ve worked with several companies and domains in order to keep upgrading my skills and knowledge. I also have good hands-on experience in programming languages like T-SQL, PowerShell, .Net etc.

I’m firm believer of our old Hindi saying “Vidya aisa dhan hai jo batne se badhta hai” (Knowledge is such a wealth that increases as much as you distribute it) and hence came up with this blog so that I can share some distinctive content from my own professional experience with my readers.

I also know that knowledge is endless ocean and hence I like to dive into this ocean each day gaining knowledge on about anything I can lay my hands on. Enjoying the greatness and vastness of what’s all out there for us to know and get amazed every day.

You can also follow me on my YouTube channel - SiddTechnolog



Thanks

Popular posts from this blog

SQL Server: SQL Server services not starting. TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support.

By
Hi All, and welcome back. As the computing power and networking is increasing day by day so is the need of more safer and stronger encryption channel methods and algorithms. And we want our databases and database server to use the same as well. But sometimes implementing them may cause undesired results like SQL Server not coming online. In case you’re also facing the same issue or planning to adopt new TLS standards like TLS 1.2 and don’t want to such problems then you should go through this post. Problem: We may require to make changes like enabling higher level cipher suite TLS 1.2 and disable TLS 1.0 for better security of our servers. But in case you make this changes it can be possible that after restart the SQL Services refuse to come online and fails. If you check the SQL Server error logs you’ll get the below errors: Error: 17182, Severity: 16, State: 1. TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL sup
Read more

SQL Server 2014 SP\CU installation getting stuck at “MsiTimingAction”

By
Image
Hello folks, and welcome back to this new post on Sidd's SQL Solutions. Recently I was working on regular SQL Server patching stuff, which often we have to do and I faced this odd situation on one of the server, which troubled me a lot. Fortunately I was able to fix it after two days of struggle, which also gave me my new post. This blog post will cover this issue and its fix in details. The Issue: The odd situation or the issue I faced here was while installing S ervice P ack 2 for SQL Server 2014 on a server running with  Windows Server 2012 R2  OS. The setup starts up normally like others but gets stuck at “MsiTimingAction ” page and  simply refuses to progress any further . No matter how many times you restart the setup or your system\server it end up at the same stage. It seems to be a known issue, which was fixed in C umulative U pdate 2 of S ervice P ack 1 for SQL Server 2014. The system on which I was applying this patch was already running with CU8
Read more

SQL Server: Cluster Installation failed with error “Wait on the Database Engine recovery handle failed.”

By
Image
So, it is a nice fine day and you’re in office doing your BAU. You got this new task of installing SQL Cluster (which you’ve probably done several times before) and after making all necessary arrangements and planning you started it. All went fine and then when the setup is almost done you got this strange error “Wait on the Database Engine recovery handle failed.” which ruins the rest of your day. No worries we are here to sort this out quickly for you. Problem Now the problem here is that SQL Server setup is able to install all the components but is failing for DB engine (and its group). You get the error pop-up stating the below error: “Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.” It may also give some link, which unfortunately (may) not lead you to anywhere. And at the end your see crosses against DB engine and its dependent components. Let me first tell you that why you got this error. In every SQL
Read more