If you run a SQL job, you need to create a profile. You don't have to stop/start the Agent to do that. You care the requiered profile using the agents GUI (if you don't run it as a NT service). You can also create such profile remotely either by using the 24x7 Remote Control or by executing one time job using RemoteCopySettings statement. If you run a JAL job you can use DatabaseConnectEx statement instead of DatabaseConnect statement. The first one doesn't need a profile. : I want to run a job on a remote agent but it has no database profiles set up : - I have only set up Database Profiles on the Master Scheduler - how do I : get the remote agent to run a job on a database instance ? Do I have to : set up Database Profiles on the Reote Agent as well ? This means stopping : the Remote Agent first and then creating the profiles and running the : agent again ? : Thanks for any help.
|