Recently, I was looking for a lightweight database for a small, independent application. One requirement was an easy deployment without installation of additional software on the server. The first thing that came to my mind was SQL Server Compact Edition. Technically it fulfilled all requirements perfectly but than I stumbled across this Connect Article.
“SQL Server compact edition is in deprecation mode with no new releases planned near future”
Sadly this disqualifies SQL Server Compact Edition for the use in a productive application and the recommended SQL Server Express or LocalDB do not really replace it.
Now the big question is, what to use instead of SQL Server Compact Edition for the use case of a lightweight, easy to deploy database on a Windows Server?
I did observe a confusing behaviour after patching a SQL Server 2012 to Service Pack 2. Some of the SSIS jobs running on that server started to fail with the message Unexpected Termination while most of the other jobs just worked as before.
Unexpected Termination can have multiple causes and if you search for that error in the internet you can find a bunch of different reasons and solutions. But non of them worked and to make the situation worse the jobs running on other servers without the Service Pack still worked. So I started looking into the known issues of the Service Pack and luckily I found this link: http://support.microsoft.com/kb/2991528
The error did not exactly match the entry I could find in the Event Viewer but all failing jobs used DT_TEXT or DT_NTEXT. I decided to risk installing the Cumulative Update (http://support.microsoft.com/kb/2983175) containing the fix. After this, the jobs started to work just fine. So in the end the solution was extremely simple.
This is just one possible solution for the Unexpected Termination error but if you experience this error after installing Service Pack 2 you should definitely check if this is also your problem.
Recently, I was installing a SQL Server Availability Group on two VMs to verify some open questions I had. And I am surprised that the installation went pretty smoothly. But when I tried to create the availability group I got the following error message.
Failed to bring availability group ‘<availability group name>’ online. The operation timed out. Verify that the local Windows Server Failover Clustering (WSFC) node is online. Then verify that the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again.
The message seemed to be pretty precise and I started verifying my WSFC configuration but unfortunately I couldn’t find any mistakes there. After searching for a while I found the following support post: http://support.microsoft.com/kb/2847723 It describes exactly my problem and the only thing I had to do was executing the following script:
CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS WITH DEFAULT_DATABASE=[master]
GRANT ALTER ANY AVAILABILITY GROUP TO [NT AUTHORITY\SYSTEM]
GRANT CONNECT SQL TO [NT AUTHORITY\SYSTEM]
GRANT VIEW SERVER STATE TO [NT AUTHORITY\SYSTEM]
It fixed the problem and I was able to create my availability group without any problems.