What SSIS jobs are executing and how do I stop one?

Every now and then an SSIS job is still running and you want to kill it to start it over with a fix you made(…in test right, you’d never let this happen in production).

There is a view in the SSISDB that will tell you what is running, and a stored procedure that can stop the running SSIS packages.
select * from catalog.executions where end_time is null

Exec catalog.stop_operation @operation_id = 33

SQL Server File Expansion Performance

Moving some old notes over to blog posts and I ran across the problem of SQL Server needing to increase file sizes.

Make sure the user running SQL Server also has permission to: Perform Volume Maintenance Tasks

The reason for this is the following:

Data and log files are initialized to overwrite any existing data left on the disk from previously deleted files. Data and log files are first initialized by filling the files with zeros when you perform one of the following operations:

  • Create a database.
  • Add files, log or data, to an existing database.
  • Increase the size of an existing file (including autogrow operations).
  • Restore a database or filegroup.

In SQL Server, data files can be initialized instantaneously. This allows for fast execution of the previously mentioned file operations. Instant file initialization reclaims used disk space without filling that space with zeros. Instead, disk content is overwritten as new data is written to the files. Log files cannot be initialized instantaneously.

In order to make use of Instant File Initialization the SQL Server user must be a member of the Perform Volume Maintenance Tasks group.


Awesome Error Messages – 1

IIS Express – The specified port is in use


Somewhere between using webdeploy to send files to a dev server a few times yesterday I started getting this message locally.  Googling for it turns up lots of results of how to change your port etc.


The root cause of this message in my case was that Entity Framework was looking for a connection string that didn’t exist in my config files.  I’d renamed it to match another that we use for the same database in a different application that is deployed in the machine.config file on our servers. Creating a DB Context in the constructor for the default controller caused IIS Express to toss this message and fail to load pages.