VSS backups might cause SQL to generate Non-Yielding Scheduler dumps if Backup verification is turned on

Found an interesting Non-Yielding scheduler recently. Opened the dump, and found function calls related to backup verification (such as validating the file name, verifying that the drive is part of the cluster group, etc.) at the top of the stack: Child-SP          RetAddr           Call Site 00000000`29cda478 000007fe`fe21a776 ntdll!ZwAlpcSendWaitReceivePort 00000000`29cda480 000007fe`fe2bcc74 rpcrt4!LRPC_CCALL::SendReceive 00000000`29cda540 000007fe`fe2bcf25 rpcrt4!NdrpClientCall3 00000000`29cda800 000007fe`f8902196…

3

Windows Server 2003 – KB 2463332 for Windows Internal Database fails to install

This is an interesting issue that I ran into, and took some time to find out the steps for resolution. What was happening was the customer was receiving repeated prompts for installing KB 2463332 for Windows Internal Database. It could, of course, have been any other update for the windows internal DB as well. Now,…

2

SQL Server Patch installation fails with error 1603

Ran into this interesting issue recently. I was trying to install a patch on SQL, and it failed. I searched in the hotfix.log (since this was a SQL 2005 instance), and found these messages:- 02/03/2012 03:01:03.649 Installing file: sqlrun_sql.msp 02/03/2012 03:01:03.696 Copy Engine: Creating MSP install log file at: C:Program Files (x86)Microsoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB2494113_sqlrun_sql.msp.log…

1

SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"

When installing SQL Server 2008/2008 R2, you might come across a situation where the setup fails towards the end, when trying to start the SQL Server services. You find this message in the summary.txt:- Configuration error code: 0x4BDAF9BA@1306@24 Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log…

74

An interesting find about Temp tables in SQL Server

I ran into a very interesting issue with temp tables recently. The issue description goes something like this. We have an application preparing some SQL statements, and sending them to the SQL Database engine for execution. However, the “issue” is easily reproducible in SQL Server Management studio. The first batch of statements looks something like…

5

Implementing SSL encryption for SQL Server in a DNS forwarding environment

Let’s say you have an environment which implements DNS forwarding. In such a setup, the client uses a different name (or FQDN) while connecting to SQL Server than the actual SQL Server name (or FQDN). The connection request is forwarded to actual SQL Server through DNS forwarding implemented at the n/w layer. In such an…

3