Windows Server 2000 - Database Server - start SQL jobs
-
Hey guys, If we restart the server in the night, there is nobody to login. Connect to the database is no problem. But we have to start several jobs on the server. is there a property to start SQL jobs from a server without login? :~
Have you tried the "Task Scheduler". You find it under Accessories/System Tools. If you prefer the CLI, you can try the AT command.
"When did ignorance become a point of view" - Dilbert
-
Have you tried the "Task Scheduler". You find it under Accessories/System Tools. If you prefer the CLI, you can try the AT command.
"When did ignorance become a point of view" - Dilbert
-
Yes sure, but they wouldn't start or rather, they wouldn't be used cause the jobs run on the SQL Server...
modified on Wednesday, March 24, 2010 6:10 AM
-
Yes sure, we already use this :-D If no user logged in the jobs wouldn't start... Think so... start your pc and you would not login, but updates run in the background. We have SQL jobs, which run at 7:00 AM but the server was restartet at 6:00 AM an nobody is there to login to the server with the adminuser. Connect to the servers database already works. :)
-
Yes sure, we already use this :-D If no user logged in the jobs wouldn't start... Think so... start your pc and you would not login, but updates run in the background. We have SQL jobs, which run at 7:00 AM but the server was restartet at 6:00 AM an nobody is there to login to the server with the adminuser. Connect to the servers database already works. :)
If the Scheduled Jobs are setup properly, using an account that the job knows about (username/password), noone has to login to the machine at all. The Agent service will run the job as the user that's supplied. No interactive login required on your part.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
If the Scheduled Jobs are setup properly, using an account that the job knows about (username/password), noone has to login to the machine at all. The Agent service will run the job as the user that's supplied. No interactive login required on your part.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
SQL Server has it's own scheduled tasks ability.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
SQL Server has it's own scheduled tasks ability.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009... -
X| yes I know... WE ALREADY USE IT!!! X| but where can we set the login property there? the >>SQL JOBS<< wouldn't run without a logged in user.
Go to "Administrative Tools / Services" Rightclick "SQL Server Agent" and select Properties. In the "General" tab, make sure the startup type is "Automatic". In the "Log On" tab you put in the correct credentials for a user with the correct permissions.
"When did ignorance become a point of view" - Dilbert
-
X| yes I know... WE ALREADY USE IT!!! X| but where can we set the login property there? the >>SQL JOBS<< wouldn't run without a logged in user.
Yeah, but you weren't too clear on that. SQL Server Management Studio -> SQL Server Agent -> Edit the job -> the Run As drop down. Also, under the General tab, you get to enter the creds of a user.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009...