It’s been a while since I’ve created production-level SSIS packages. I’ve been fortunate enough to hand that responsibility over to our development team…
So, when someone mentioned today that SQL 2008 “broke” the SSIS logging feature, I got typically defensive and immediately set out to prove that the SQL team would never be that short-sighted.
So I created a simple “Move Data From A to B” package and enabled the trusty SSIS SQL logging; logging the OnError, OnPreExecute and OnPostExecute events as I always do. I ran the package, and promptly moved across to SQL Management Studio to open my trusty sysdtslog90 table, and prove my friend wrong.
I did a quick refresh on the table list, and lo-and-behold, the trusty sysdtslog90 table was nowhere to be found.
(So much for my faith in the basic goodness of developers.)
After a few minutes of checking package properties, the penny dropped; the trusty logging table hasn’t been ignored, it’s simply been moved and renamed.
It can now be found in your target database under System Tables, and it’s called sysssislog.
Two main benefits to this:
1. Name is no longer version specific, so hopefully it’ll keep the same name going forward.
2. System tables can’t be renamed, so it should be more robust.
(Faith in humanity restored, if only it had been on the new feature list somewhere…)