DTS Standards

Question

DTS Standards

Jonathan Stokes

SSCrazy Eights

Points: 9861
More actions
November 2, 2005 at 2:08 pm

#188246

Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/cherring/dtsstandards.asp
------------------------------
The Users are always right - when I'm not wrong!

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Edward W. Stanley SSCertifiable Points: 6512 More actions · Answer 1

I think thats great. But with the waning support for DTS as I found in the release of 2005 (which bothers me, btw), I wonder how we can migrate those over to 2005 with little effort. I have in some of my deployments dozens of complex DTS packages.

And maybe its job rentention but I"d rather be movign on to making newer better faster projects then maintenance.

Cheers.

Jonathan Stokes SSCrazy Eights Points: 9861 More actions · Answer 2

I agree with you. However, there are a lot of Organisation's out there who will still be using 2000 2 or more years from now.

At least that is the impression that I have got from talking to colleagues and friends. For some it's the money, for others the amount of work involved and for the cautious, the risk. Being in a datawarehouse environment currently moving to an etl tool scenario, there's not much to be immediately gained from moving to 2005.

------------------------------
The Users are always right - when I'm not wrong!

Alex-217289 Ten Centuries Points: 1085 More actions · Answer 3

I agree that the naming convention should certainly be used to clearly identify sources and destinations as well as transform steps. As for using descriptive text at the top of your DTS packages, perhaps consider hiring a DBA capable of making a couple of clicks to find out info instead. It'll keep your packages cleaner and many of the objects in DTS are self-describing anyway. With a good naming convention, you should be all set.

By the way, the Green Lantern rocks!

Cheers,

Alex

Rogue DBA

philcart SSC-Forever Points: 47796 More actions · Answer 4

Like the naming convention, just hate it when you look at the package and can't see the full name because of those annoying dots.

I avoid using text annotations and worrying too much about the package layout. Both of these are not part of the package object model so if you modify the package programmatically and save it you lose them.

Also, is the Execute Proces task just used to make a copy of the Excel file? The line "...import the source spreadsheet before we DTS it in..." sort of implies that we're importing the file twice.

--------------------
Colt 45 - the original point and click interface

Carlos Urbina SSCommitted Points: 1850 More actions · Answer 5

Thank you for your suggestions, Jonathan. In the long run, standards and conventions are not for the brilliant innovator, but for the stalwart person who can keep an enterprise going. For the innovator, I would remind them that genius has ALWAYS been about the 90% perspiration. In other words, we must take the time to help others understand what we do, no matter what the circumstances, because in the end it will be cost effective to the enterprise to which we owe our living.