Sidd's SQL Solution

Hi all, today in this post I’ll discuss one of the scenario, which I face (quite commonly now), while installing clustered SQL instance or setting up Always-on availability groups on machines running with Windows Server 2012/R2. Issue While installing Clustered SQL instance on a Windows Server 2012/R2 cluster, you may also see below error before installation is about to complete. In case you also seeing this error then you should visit Window’s “ Event Viewer ” before quitting the setup to have more details on the same. Cause In this post we are discussion one of the possible case, which is causing this issue and i.e. “Failure to create SQL Cluster Object in AD”. If this is the case then you’ll see an error similar to the one below in Window’s “Event Viewer” .  While installing a Clustered SQL Instance, SQL Server setup is also required to create a “ computer object ” in AD with same name as “ SQL Cluster Name ” provided during the setup. This is required so that Virt

Hello all. In this post I’m picking up an interesting problem related to SSRS, which was a result of a small miss in SSRS configuration and can keep novice DBAs wondering for long, what has went wrong (Hey does it rhymed!!). As we know .Net Framework provides easy and extensive integration of technologies and SSRS is no exception to it. There are multiple ways in .Net through which SSRS reports can be directly used within the application like using “Report Viewer” component, which is simpler to implement and use. Other ways is using more complex (means needs more coding) is “Report Execution Service”. In both the cases the SSRS report server URL should be accessible to application. Problem Our DEV team was working on one such integration using the “Report Execution Service” method, so one of our DBAs installed and configured SSRS components and provided the respective URLs to the team to use after providing appropriate rights to folders. Team was successfully able to depl

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

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

Hope this New Year had brought good time to all my blog readers. After a small break, I’m back with a very interesting blog post, which I’ve prepared on an interesting problem I faced recently. If you’re planning to use database mirroring as a solution to create secondary backup\failover site for your database, which is serving as backend database to your .Net Application hosted on the IIS Server then this is one of the things you need to consider apart from other pre-requisites. Scenario We had two databases running on different versions of SQL Server. One hosted on SQL Server 2008 R2 SP3 instance and another database was on SQL Server 2012 SP1 instance (both were stand-alone). We had two different applications connecting to these databases respectively, one application hosted locally and other one on remote IIS server. Problem The applications were running fine and without any problems in production and were able to access and work with test databases created on the r