SQL SERVER – Fixing Annoying Network Binding Order Error – Notes from the Field #112
[Note from Pinal]: In this episode of the Notes from the Field series database expert Ryan Adams explains a very critical error user receive when binding network error. Ryan is one guy who spends more time with real world issues with SQL Server than anything else. He has mastered the art of resolving complex errors and document them so easily that one can’t find anywhere else. In this blog post Ryan addresses a very interesting error related to binding network error. Read the experience of Ryan in her own words.
SQL SERVER – Add failover cluster node fails with “number of cluster nodes supported for edition”
SQL SERVER – Timeout expired. The timeout period elapsed prior to completion of the operation
Today we are going to learn about how to fix the error: Timeout expired. The timeout period elapsed prior to the completion of the operation.
SQL SERVER – FIX: Msg 4335, Level 16, State 1 – The specified STOPAT time is too early
While trying to prepare for a demo, I ran into some interesting error. When I searched for error about STOPAT on the internet, there were not many clear answers so I thought of sharing on my blog. Actually, my demo was all about point in time restore feature of SQL Server. I was trying something similar given in my earlier blog.
SQL SERVER – System.IO.FileNotFoundException: Could not load file or assembly
SQL SERVER – FIX: Msg 7395, Level 16, State 2 – Unable to start a nested transaction for OLE DB provider
While playing with linked server from SQL Server to SQL Server, I faced few errors and fixed them as well. It has become a custom to get errors working with Linked Servers almost every time. I personally thought it is worth blogging because I didn’t find any single blog having the cause and solution explained in detail. Let us learn about the OLE DB provider error.


