Mon 8 Feb 2010
I’m reposting a list of task/component prefix naming conventions that Jamie Thomson posted some years back for SSIS. Using a standard set of prefixes allows for easy log reading, better multi-developer support, and ease of readability.
Get the Excel document here: SSIS_Prefix_Naming.xlsx (11 KB)
Note that I have not updated this document for 2008 task/component changes, and some of the abbreviations may have been changed from Jamie’s original list of suggestions to suit the needs of my organization at the time.
July 3rd, 2011 at 2:37 pm
I am not a fan of prefixing tasks that you already know what it is. It’s like labling a circle on a diagram for example when you can clearly see it is a circle. It also doesn’t make sense that it should be known in logging as a circle.
Tasks aren’t the same as datatypes as per programming languages that needed to be prefixed all over the show.
When it comes to logging and finding your tasks in the sysdtslog90 table, it makes so much more sense to see the task for it is rather than navigating through all the noise of prefixes.
October 6th, 2011 at 3:43 pm
It’s quite the opposite for me. The prefix helps me a lot to easily identify the component/task I am looking for in the all the noise of sysdtslog90.
December 27th, 2011 at 5:17 am
Thanks I was looking for that. Prefixes for me is a must… I might know what the package does but names are ambiguous and with prefixes I straight away narrow it down to specific task type which saves me time + saves a lot of time for those who haven’t developed the package.
Regarding the comparison to diagram and circle I think it is missed comparison. Logging is a table (something you don’t visualize) and not a diagram therefore you will never see a circle unless you put prefix that will indicate it relates to “mathematical circles” and not “cultural circles”.