SSMS Auto Save – Recover Lost Files


Hi All,

I’m sure, many times you’ve all faced the frustration of losing your work due to an SSMS crash. The good news is that if you’re using SSMSBoost¬†your recent query windows will be saved.

If you go to the settings of SSMSBoost and check the Script Execution History tab, you’ll see there is a checkbox that will Enable Execution History, you can also choose where to store your files.


Extremely useful and this doesn’t require you to save every query window that you open!

Tableau -Unable to remove borders from worksheet


I tried everything to remove all the borders from my worksheet so that all that showed up was the number I was interested in. But I still ended up with this:


Even though all of my border settings looked like this:



Turns out that it’s just a workbook display bug as when I published my dashboard, I ended up with this:


SSIS -Registry setting specifying configuration file does not exist


I was having an issue getting an agent job from completing when running a package that relies upon an Indirect XML Configuration File. When executing the agent job I received a couple of warnings, one from the SSIS Package itself and another from the Event Viewer:

Event Viewer:


SSIS catalogue error:


The problem here was that I had my environment variable used to specify the location of my config file set up in my User Variables and not in System Variables. This was also a problem because I’d specified the [NETWORK\SQLAgent] user as the SQL Agent service logon account.


Once I switched my variable into System Variables my agent job ran through without error.

SSIS – Keyword not supported: ‘provider’


Today I’d set up an agent job for a project deployment model SSIS package. In my project I’m using connection managers to handle my database connections and had configured my SSIS package to use the variables I wanted, however when I kicked off my agent job, it failed with this error:

Error: System.ArgumentException: Keyword not supported: 'provider'


Eventually I figured out that during configuration of my SSIS project I’d pointed an ADO connection in my SSIS package to an OLEDB connection manager in my environment variable. Once I swapped the connection to point to an ADO connection the package ran as expected.