Rotating Header Image

Just Keep Googling, Just Keep Googling…. SQL Agent Job Scheduling (Past and Future)

So I needed a script where I could provide a start and end date that could go into the past and into the future to determine all the job schedule executions that should have or will happen between the given dates.

I found bupkis

My Google-Fu was weak and couldn’t find anything so I pinged the OOBER smart folks on Twitter as I couldn’t be the ONLY person who ever wanted to do this.

This one was a tricky one to find… so tricky in fact that I started writing my own version and had moderate success but was still SO BUGGY.

I started to work through some of my bugs and low and behold I found the holy grail!!

Twitter: Peter Larsson

Moral of the story: Don’t stop Googling cause there is a 99.9% chance that you’re not the first person to want to solve a particular problem.

Mr. Peter Larsson I thank you! ๐Ÿ™‚


Enjoy!! (Follow me on Twitter: @ColinStasiuk)

Post to Twitter Post to Delicious Post to Digg Post to StumbleUpon

Colin’s Oilers Ticket Contest!!!

So this is one of those personal non-geek type of posts so I apologize if this ends up on your feed and you were expecting something SQL-riffic ๐Ÿ™‚

Today is my birthday…

and I thought a good win/win scenario to try and get me out of my birthday funk is to do something that I like to do every now and again and give away some Oilers tickets!!!

…. but here’s the catch (sorry… this time there is a catch ๐Ÿ™‚ hehehe)

My son Rob is playing in the Stollery Family Day classic hockey tournament to raise money for the Stollery Children’s Hospital.

For those if you that don’t know… I spent a good chunk of my childhood in that hospital back when it was named the Northern Alberta Children’s Health Foundation.

So here’s the deal….

For every person that donates to my son Rob’s Stollery Hockey Tournament page you will be assigned a number.

At 8 PM tonight a random number will be drawn and that person will receive two tickets to the Oilers vs. the Flyers on Feb 16th!!!

$10 gets you 1 number
$25 gets you 3 numbers
$50 gets you 7 numbers
$100 gets you 20 numbers

Click the image below to donate and enter the contest!!!


Enjoy!! (Follow me on Twitter: @ColinStasiuk)

Post to Twitter Post to Delicious Post to Digg Post to StumbleUpon

Hey #SQLFamily Where Do You Go?

OK so this video came out like 7 years ago which is pretty well how long it’s been since I’ve blogged.

I miss blogging and the #SQLCommunity #SQLFamily #SQLHelp #SQLPASS…. basically all the hashtags that have anything/everything to do with SQL.

I turned on Tweetdeck for the first time in a LONG time and said a quick “Hello, from the other side”


(I’ll spare you the Adele meme) ๐Ÿ™‚


Low and behold a couple of #SQLBeauties (New Hashtag ALERT) @grrl_geek and @SQLBek remembered me and said hello.ย  <3

So why am I here?

Deep right?

I’m trying to find where my #SQLPeeps (New Hashtag ALERT) are hanging out these days…. twitter seems quiet with the usual suspects of #SQLPASS and #SQLHelp getting the odd post here or there…. have people just stopped tweeting?

Anyways I made a New Years Resolution to get my name back out there and start getting my presenting chops back because I really miss it (and all of you!!!).

If you’re out there…..

Hit me back, just to chat, truly yours, your biggest fan…. this is Colin



Enjoy!! (Follow me on Twitter: @ColinStasiuk)

Post to Twitter Post to Delicious Post to Digg Post to StumbleUpon

Do You Even Blog Bro? (Stats, Execution Plans, Indexes, and crazyness)

Have you ever worked with a piece of software for like 15-20 years and ended up doing something with that product that you haven’t or can’t remember doing ever before?



This happened to me quite recently and although I wont have a bunch of sexy scripts for you to reproduce the problem I will go through what I learned/remembered you can do with statistics.


  • Production database at a customer site is choosing an absolutely shitty execution plan (not using an index as expected).
  • Can’t get a backup
  • Don’t want to “cowboy” it up on a live 24/7 $$$$$$ production system
  • Can’t reproduce in development with an old backup that we have on site.


Trying to determine “why” this is happening was proving to be a rat-hole until I came across this:

specifically the part that said showed that you can run this:


What this UNDOCUMENTED/UNSUPPORTED/BE VERY CAREFUL USING/GREAT POWER BLAH BLAH BLAHย is doing is this is actually scripting out your statistics and the histogram



Now that you have the statistics from (in my case) the production database that I cannot get a backup of, or actively troubleshoot against, etc I can then run the following statement on my development server (which has an older backup of the database in question restored)

UPDATE STATISTICS [dbo].[TableName]([StatisticName]) WITH STATS_STREAM = 0x01000000010000000000000000000000B242E5900000000000038......etc., ROWCOUNT = 159543018, PAGECOUNT = 2904894

And BOOM… we were able to reproduce and establish the root-cause of the issue.

After googling around for blog posts about STATS_STREAM I did find the following as well:

Anyways this was just one of those moments where I got all excited and had that awesome feeling about trying something new and having it work.

Now that SQL Server 2016 is available to download for everyone I imagine I’ll have more “a-ha” moments


(If you don’t get the reference you’re young and I hate you and get off my lawn!!!)


Enjoy!! (Follow me on Twitter: @ColinStasiuk)

Post to Twitter Post to Delicious Post to Digg Post to StumbleUpon

Microsoft…. Y U NO FIX??



I would like…. if I may… it take you on a strange journey….

Consider this:

  • A SQL Server database with ALLOW_SNAPSHOT_ISOLATION set to true
  • A stored procedure that creates a #temp table in tempdb and subsequently drops it
  • Multiple calls of this stored procedure (running in Snapshot Isolation mode) happening at the same time

Please tell me how/why I would get this error:

Msg 3961, Level 16, State 1, Procedure CREATETABLE, Line 8
Snapshot isolation transaction failed in database ‘tempdb’ because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction.ย  It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.


Riddle me that!!!! (and yes I saved you the horror of seeing me in skintight green spandex)

SETUP (credit: Loris Chiocca):

USE [master]
CREATE DATABASE [SnapshotIsolationDB]
( NAME = N'SnapshotIsolationDB', FILENAME = N'C:\TEMP\SnapshotIsolationDB.mdf' , SIZE = 102400KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB )
( NAME = N'SnapshotIsolationDB_log', FILENAME = N'C:\TEMP\SnapshotIsolationDB_log.ldf' , SIZE = 10240KB , MAXSIZE = 2048GB , FILEGROWTH = 10%)
USE SnapshotIsolationDB
      ID int NOT NULL primary key
     waitfor delay '00:00:01'
        exec ACCESSTABLE


set transaction isolation level snapshot
begin tran
commit tran

Keep in mind you’ll probably have to rush-click-execute a few times before being able to produce the error…

So this isn’t my code or my find in the first place.

Why am I talking about it then?

3 Reasons…

  1. To hopefully bring more light to this bug
  2. To hopefully help others who run into this problem and their google-fu wasn’t able to point them to the Microsoft Connect Item.
  3. Cause it’s a thorn in my ass right now

Check this out…

And the comment of particular concern:

“Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing this bug is because the scenario reported in the bug are not common enough and due to the risk of implementing a fix it unfortunately does not meet the bar for the current version of the product.



If anyone is curious as to how I “fixed” my problem…. I stopped explicitly dropping the #temp tables in my stored procedure and allowed SQL Server to “clean up after itself” as the Snapshot Isolation errors always seemed to have an issue with the:



The question outstanding though is if #temp tables are created with the same name by different SPIDs and they exist in tempdb with the unique name that looks like : #temp_____00000090019545666 how can ANOTHER SPID be affected by the creation and dropping of said #temp table???



Enjoy!! (Follow me on Twitter: @ColinStasiuk)

Post to Twitter Post to Delicious Post to Digg Post to StumbleUpon

Twitter links powered by Tweet This v1.6.1, a WordPress plugin for Twitter.