Jeff Moden (6/4/2014)

---

Koen Verbeeck (6/4/2014)

---

SQLRNNR (6/4/2014)

---

Evil Kraig F (6/3/2014)

---

SSIS: Crappy naming methods for your data sources. You're connecting this thing to a database and you're going to push it through environments. It doesn't need to be named "Martha's stuff in a table". Name it after the database.

This made me think of another really bad pet peeve.

Naming the database as _Prod, _UAT, _QA, _Dev in order to match the different environments. Not only does it screw with code releases, it screws with SSIS packages (and yes configurations help a bit with that, but then do you leave the DS named after Dev where you built the package in the first place?).

It only makes sense if all those databases are on the same instances. (sounds like a lovely idea)

You could suffix the databases names if the databases are in source control and you need to branch.

...

As far as SSIS packages go, thanks... you've just given me yet another reason to avoid SSIS whenever possible. 😛