Problem Changing Job Names in Replication Script

• DBADave

  Newbie

  Points: 0

  More actions

  August 1, 2003 at 7:02 am

  #101600

  I implemented replication and scripted the entire process (including jobs). I modified the job names within the scripts to comply with our naming conventions. After I run the script SQL Server creates the Snapshot, Distribution and Log Reader Jobs with my job names, but also creates a second set of Snapshot and Distribution jobs using its own naming convention. The replication agents that are created only reference the SQL Server generated jobs, not the ones where I modified the names. Does anyone know why this is happening?

  Thanks, Dave

• sarmistead

  Newbie

  Points: 0

  More actions

  August 1, 2003 at 12:58 pm

  #468270

  In BOL look at the doc for each of the SPs used in replication (sp_addpublication, etc.) and you notice that the job names are marked as for internal use only. You can provide a job name on the step but SQL Server will not use it for it's own processing.

  Steve Armistead,

  Database Administration

  Panther Systems, Inc.

  Vancouver, WA

  Steve

• DBADave

  Newbie

  Points: 0

  More actions

  August 1, 2003 at 1:04 pm

  #468273

  I noticed the "For Internal Use Only", but wasn't sure what it meant. Since Job_Name was being offered as a parameter I thought it was valid for me to change the Job_Name. Now I'm wondering why it's even listed as a parm if you can't use it.

  Thanks, Dave