Saving the SSRS Encryption Key might not provide a helpful error message
Errors
Background Because one of the nodes in our AG was having Windows updates applied, it was necessary to suspend data movements for all databases involved in the AG, on that server. Upon my return (after the maintenance was completed) I was unable to connect to the server, with a message that didn’t really match the …
The full message will also contain “The version number cannot be greater than the current version number”. Behaviour I have an SSIS package installed in an SSISDB which is on a server that run SQL Server 2012 (server A) and it needed to be copied to another 2012 instance (server B). My workstation has SQL …
In a previous article I demonstrated how use of READUNCOMMITTED (or the NOLOCK hint) can result in erroneous data, due to page splits. Examples abound of the more common issue with this isolation level, which occur when reading a row that is being updated in another transaction and then rolled back. These so-called ‘dirty reads’ …
Generally, when somebody posts a query using the NOLOCK hint, there are a variety of warnings about dirty reads, phantom reads and double-reading (due to page splits). The dirty read example is common and tends to be the main example used to demonstrate what to watch out for with NOLOCK, but I’ve never seen an …
SSIS can produce an inordinate number of error messages and numbers. Some of these can even be helpful and informative. Generally accompanied by an Error Code, one of the most popular appears to be “0x80070057” and can have a number of causes. Recently I came across this particularly helpful code when creating a Slowly Changing …
Notes on SQL 