|
Does anyone have recommendations for SSIS object naming conventions? I've been using a seat-of-my-pants methodology, with few standards. I'm curious what other shops are doing. Thanks! Tim
(comments are locked)
|
|
Back in 2006, Jamie Thomson (a SQL Server MVP for SSIS) published a set of best practices and naming conventions for tasks and components Object Naming Conventions: These have become fairly popular and may be the source of some of the "Hungarian"-like names for SSIS objects. In the SSIS graphical environment, the icons typically indicate what the object is, and the naming conventions don't seem to serve much value. However, there is value in when the full name is reported in error logs. This makes it possible to easily identify the type of task/component that is reporting the error. Beyond this, the most important criteria for a good naming convention is consistent use throughout all your packages.
(comments are locked)
|
|
I know a few places that insist on using "DFT ..." for Data Flow Tasks, and so on. Personally, I'm not as much of a fan of having a particular naming convention as I am having sensible names, and appropriate descriptions. And useful annotations where possible. I agree. I am particular with my naming conventions for database objects and columns, but my SSIS task names look more like descriptive labels than anything else.
Oct 22 '09 at 03:23 AM
Tom Staab
As SSIS is a drag-and-drop interface, I think there's a little less reason to have a particular naming convention. You look at it graphically. If you hook into the XML itself, you have the types available in other ways.
Oct 22 '09 at 04:11 AM
Rob Farley
(comments are locked)
|
|
In the MCTS for BI they were all DFT this and SMTP that and so on. I tend to go against this now I am doing my own thing which is generally just a really good descriptive label.
(comments are locked)
|
