Comments on: SSIS – Task and Component Naming Conventions http://www.ssistalk.com/2010/02/08/ssis-task-and-component-naming-conventions/ Random thoughts and experiences with SSIS, by Phil Brammer Wed, 25 Jan 2012 10:27:44 -0600 http://wordpress.org/?v=2.9.2 hourly 1 By: Emil Glownia http://www.ssistalk.com/2010/02/08/ssis-task-and-component-naming-conventions/comment-page-1/#comment-46042 Emil Glownia Tue, 27 Dec 2011 11:17:43 +0000 http://www.ssistalk.com/?p=217#comment-46042 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". 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”.

]]> By: Hou BI Developer http://www.ssistalk.com/2010/02/08/ssis-task-and-component-naming-conventions/comment-page-1/#comment-35841 Hou BI Developer Thu, 06 Oct 2011 21:43:16 +0000 http://www.ssistalk.com/?p=217#comment-35841 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. 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.

]]> By: Pieter Olivier http://www.ssistalk.com/2010/02/08/ssis-task-and-component-naming-conventions/comment-page-1/#comment-27537 Pieter Olivier Sun, 03 Jul 2011 20:37:43 +0000 http://www.ssistalk.com/?p=217#comment-27537 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. 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.

]]>