Recently I found out that Toad has nice option 'Automation'.
I tried to use it (just to test) and it works perfectly fine for me.
For my curiosity I wanted to Schedule the Task but failed.
What I did:
Login as domain\user
Connect to server
Create a simple Task and successfully executed it
Click on 'Schedule' button in 'Automation Script' dialog and took 'default' Schedule
It requested my credentials
When I click on 'Apply' it throws the error ( see attachment0
You haven't detailed the steps you are taking to create/schedule your "job", so rather then guess, I'll say that it's best to let Toad schedule the automation job for you. When you've tested your automation flow sufficiently, hit the "Schedule Automation" tool button above your workflow. Toad will ask you to name your job (*.TAS file type) and then ask for details on how the task scheduler should initiate your job, per screen snap below... note that it picks up your Windows credentials automatically.
Hi Gary,
You answers is always very valuable.
Here are my steps just to validate that Scheduling works for me.
login
in 'Database Activities' select 'Execute Script'
'Preview SQL' and populate statement:
select TABLE_NAME FROM INFORMATION_SCHEMA.TABLES
'Save Automation Script to file and add to Project'
It saved it at C:\Users<my-name>\AppData\Local\Quest Software\Toad for SQL Server 5.8\Toad Projects\test01.tas
Validated that it generates expected Result Set of 1092 rows
I click on 'Schedule' button but it didn't ask me to name the Job. It simply pop-up a dialog ( see attachment 1-3.png)
I click on OK button
In Job Manager I see the following ( attachment 4.png)
It has Status 'Not scheduled'
I do 'right-click' and 'Edit Task' and see the same as before i.e. attachments 1-3.png
At which point I'm doing wrong?
Thanks
P.S. I see that your screenshot looks like regular Windows Task Scheduler but mine is completely different. Likely this is the culprit .. When I click on 'Schedule ..' it opens
Actually I wasn't able to fix the issue ... but I found the workaround : I started to use Windows Scheduled Tasks utility.
Well .. likely it was not designed that way ... but at least I'm not blocked now.