Running SQL JOB for SQL Express >>>>>

I need to run a SQL script as a job for SQL Express. How can I do this ? Are there any programs that will allow me to do this ?

The solution for running schedule tasks in SQL Express is to use a Task in the Windows Task Scheduler to call SQLCmd and run the script you want to run. You can set schedules, etc. using Windows Tasks.

SQL Express does not include the SQL Agent, which is the tool higher level Editions of SQL use to schedule jobs.

Regards,

Mike Wachal
SQL Express team

-
Please mark your thread as Answered when you get your solution.

|||

Hi Mike,

Thanks for the information. I will try that. I also did a search and there is a program created by a company called Vale Software. They have a program named Express Agent that looks like it may work too. Thanks !!!

|||

I do not understand why Microsoft went through the trouble of removing the Sql Agent scheduler from SQL 2005 Express. This is wrong for any product path/roadmap. There are many small applications, both in-house IT as well as distributed, that depend on the reliable SQL Server Agent Job scheduler.

I stopped using the Windows Task Scheduler years ago because you cannot count on it. It is not reliable. While it has improved since the NT4 and early Win2000 days, it is only marginally better due to a UI instead of the AT command line.

We need the service, SQLSERVERAGENT, to be included with SQL 2005 Express in order to migrate applications to 2005.

If you have a system that is configured for Client - Server - Notebook/offline and you utilize SQL2005 on the servers, you need SQL2005 Express on the Client and notebooks for replication. For the same reasons we distribute MSDE now, we would distribute SQL2005 Express in the future for the Notebook/offline engine. Out installations, updates, and backups, depend on the server and notebook being the same, (i.e. the same service names, the same scheduler, etc.). If the notbooks cannot have Express with the SQLSERVERAGENT service, then that complicates everything and increases the cost to everyone involved.

|||

Yes, I definitely agree. I'm working on a product that uses a database, and that uses a free database for small business customers. We used to rely on MSDE. Now, we may rely on other non-MS databases, knowing that OLE DB allows us to access any database we need.

I don't think this is such a good commercial decision from MS.

Moreover, you can find in SQL Express all tools (stored procedures, tables) in msdb for creating and setting up jobs. The only thing you can't do regarding jobs is...starting them!!! This either does not give a good image of MS...