I'll tell you what we have here... - One .cmd per instance; - The .cmd file is located on the drive associated with the instance. Same thing with the .opt;
Hope it helps, On Wed, Mar 19, 2008 at 8:36 PM, Gill, Geoffrey L. <[EMAIL PROTECTED]> wrote: > Perhaps others have already dealt with this. > > > > Is there a way to create a single .cmd file that can be used for one > schedule with multiple sqlservers in a cluster environment so it will > run properly no matter what instance is on any one node or may have > failed to a node it normally does not live on and not report a failure? > Or do I have to make separate schedules for every node each with its own > .cmd file and make sure the .cmd files are on all cluster nodes? > > > > > > Geoff Gill > TSM Administrator > PeopleSoft Sr. Systems Administrator > SAIC M/S-G1b > (858)826-4062 > Email: [EMAIL PROTECTED] > -- __________________________________ Leandro Mazur
