DTS / job naming strategies

  • I have 7 production and 6 development SQL Servers that I manage.

    I have a lot of DTS packages and jobs.  It's becoming more and more difficult to find packages and jobs. 

    I was thinking of standardising on a naming convention of this:

    division - export/import/backup/sql script - source - destination - application name - what the job does

    Comments?

     

  • This was removed by the editor as SPAM

  • Personal preference, but I'd put the application name first. Quite often I'm faced with tracking down problems with XYZ application. If you run the same application in multiple divisions you can follow it with the Division id.

    The main thing is to set a standard, document it, publish it and stick to it.

     

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

Viewing 3 posts - 1 through 2 (of 2 total)

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