InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 22:03:11 GMT20http://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxIn SQL Server 2008, SSMSE does not support scheduling administrative tasks by using SQL Server Agent (http://msdn.microsoft.com/en-us/library/ms365247.aspx). So in effect there is no support for jobs - they can't be scheduled to run, although obviously you can create jobs using the MSDB stored procs. In SQL Server 2005 Express Edition, jobs can be created using the MSDB stored procs just as in SQL Server 2008 Express Edition, and they can't be scheduled to run. The support for jobs is exactly as extensive or restrictive in 2008 express as it is in 2005 express, so why does the answer claim you can create them in one but not in the other? The URL given as explanation is completely useless, it doesn't refer to jobs at all. Also, it doesn't say anything at all about SQL Server 2008, althoough the question (and the answer) both explicitly refer to 2008 as well as to 2005 and the answer makes a claim about them being different in respect to jobs in express edition.The question and answer are thoroughly misleading, and the reference given for the explanation is completely irrelevant. This doesn't help anyone learn anything, and may even mislead someone into using the wrong edition of SQL Server 2008.As an earlier commenter said, this sort of thing brings QOTD into disrepute.Sat, 30 Jan 2010 12:03:41 GMTL' Eomot Inverséhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspx(deleted post about "Enterprize" haha-how-funny-but-made-me-answer-wrong and going back to work instead of playing guessing games :-P)However I want to mention that I prefer to use *.SQL scripts with sqlcmd.exe in Windows Scheduled Tasks to do regular maintenance work and Backups instead of SQL Agent Jobs...They are independent of SQL Editions and can be maintained without the sluggish Management Studio...And last but not least they are much easier to deploy on multiple servers without the hassle of dealing with "Maintenance Plan" SSIS Packages and the related issuesWed, 09 Dec 2009 10:25:53 GMTTrekmanhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxCrud, I missed it. This is good to know if you have automated maintenance or admin scripts though. I guess if your scripts set up jobs on new servers, the scripts will run successfully on express, but the jobs will never start... and you'll never know that the instance isn't configured like you thought.ChadTue, 01 Dec 2009 09:10:14 GMT Chad Crawfordhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxI would imagine you could even conceive of creating these jobs and then kicking them off on a schedule based on Reporting Services Scheduled Reports, or using the windows task scheduler and an OSQL command or a variety of other resources. There are a variety of frameworks and applications on codeplex and CodeProject amoung others to get around these same issues...This is just the first one from Google...http://www.codeproject.com/KB/database/SQLAgent.aspxMon, 30 Nov 2009 08:03:16 GMTLuke Lhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspx[quote][b]david.wright-948385 (11/30/2009)[/b][hr][quote][b]kevin.l.williams (11/27/2009)[/b][hr]I don't think I learned anything useful by getting this question wrong. Who cares if you can create a job in express if it can't be used?[/quote]It wouldn't be difficult to write a stored proc to run at startup and thereafter every minute, which kicks the jobs off when scheduled...[/quote]Could even add "catch-up" logic to run jobs missed while the instance was down :-)Mon, 30 Nov 2009 03:00:38 GMTdavid.wright-948385http://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspx[quote][b]kevin.l.williams (11/27/2009)[/b][hr]I don't think I learned anything useful by getting this question wrong. Who cares if you can create a job in express if it can't be used?[/quote]It wouldn't be difficult to write a stored proc to run at startup and thereafter every minute, which kicks the jobs off when scheduled...Mon, 30 Nov 2009 02:57:55 GMTdavid.wright-948385http://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxI had to laugh at the LOLCats spelling of Enterprise as Enterpri[b]z[/b]e! Too bad the question wasn't written in LOLCats as well... "I can haz SQL j0bz in which edishunz?":-DSun, 29 Nov 2009 10:47:32 GMTNoel McKinneyhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxHopefully no one is "running" their database maintenance with these jobs on SQL 2005 and 2008 Express :-). This question smelled tricky from inception, and I am a little disappointed in myself for falling in the trap.Not much learned here, but at least I refreshed my knowledge of SQL Server 2000 - SQL Server Agent.Fri, 27 Nov 2009 17:48:58 GMTKen Garretthttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxI don't think I learned anything useful by getting this question wrong. Who cares if you can create a job in express if it can't be used?Fri, 27 Nov 2009 09:43:31 GMTkevin.l.williamshttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxWell, I can't defend this one. I have to agree, what good is it to create the job if you can't run it?Fri, 27 Nov 2009 09:07:13 GMTLynn Pettishttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspx[quote][b]dawryn (11/26/2009)[/b][hr]Another QoD turned sourAnd it will be covered with educational purposes :Whistling:[/quote]Hey, but at least we learned something, right? Oh, wait...Fri, 27 Nov 2009 07:00:13 GMTRob Goddardhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxI think this is one for Steve (Jones): There have been a number of QoDs lately that appear to be designed deliberately to mislead, on the pretext that everyone will get it wrong and [b]"learn from the experience"[/b]. Trouble is, it just makes people cynical about QoD in general and stop them even trying to answer, because answering correctly isn't based on skill or knowledge, rather it is a simple but annoying game of chance.Fri, 27 Nov 2009 05:54:45 GMTdavid.wright-948385http://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspx[quote][b]MarkusB (11/26/2009)[/b][hr]Strictly speaking you can create a job in SQL 2005 Express as well. All the necessary stored procedures in the msdb are there and you can execute them succesfully. You cannot execute them on a schedule because there's no SQL Agent, but a job exists.Just try this:[code="vb"]USE msdb ;GOEXEC dbo.sp_add_job @job_name = N'Daily Backup' ;GOselect * from sysjobsGO Exec dbo.sp_delete_job @job_name = N'Daily Backup' ;[/code]I think the question should be in which version can you execute jobs on a schedule.[/quote]I would have to agree with this. The question in this scenario just does not quite seem to match properly. The question asks what editions can you create a job in SQL Server, far different from being able to schedule a job.Thu, 26 Nov 2009 18:35:57 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxso technically you CAN create the jobs but it is meaningless because they will never be run. tis a bit misleading if someone just reads the answer and not the forum, then runs off to install expressThu, 26 Nov 2009 15:21:34 GMTsqljohn (twitter)http://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxpoor question, poor explanationand I do not agree with the "supposed" answer - but then why should we expect the "author" to know what he/she is talking about when they can't even spell "enterprise"?Thu, 26 Nov 2009 14:56:33 GMTtimflehttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxSo, it seems i'm not alone being trapped by create/schedule a job for the 2008 Express Edition :DThu, 26 Nov 2009 08:04:07 GMTDude76http://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxWhat to say...?SQL Agent is installed with SQL Server 2008 Express but cannot be started. So the creation of job is meaning less if you cannot execute it.Lost my point....Thu, 26 Nov 2009 05:19:46 GMTAtif-ullah Sheikhhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxAnother QoD turned sourAnd it will be covered with educational purposes :Whistling:Thu, 26 Nov 2009 04:54:56 GMTdawrynhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxStrictly speaking you can create a job in SQL 2005 Express as well. All the necessary stored procedures in the msdb are there and you can execute them succesfully. You cannot execute them on a schedule because there's no SQL Agent, but a job exists.Just try this:[code="vb"]USE msdb ;GOEXEC dbo.sp_add_job @job_name = N'Daily Backup' ;GOselect * from sysjobsGO Exec dbo.sp_delete_job @job_name = N'Daily Backup' ;[/code]I think the question should be in which version can you execute jobs on a schedule.Thu, 26 Nov 2009 04:15:26 GMTMarkusBhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspx[quote][b]vk-kirov[/b]... That link contains nothing about jobs and SQL Server Agents and should be corrected.[/quote]Done (it was under first result)Thu, 26 Nov 2009 04:13:44 GMTdawrynhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspx[quote][b]dawryn (11/26/2009)[/b][hr][quote]I can't see anything about jobs there. The link seems to be not relevant to the question.[/quote]What is the use of a job if there is no service to be executed (scheduled) with? Any new features in 2008 Express?[/quote]This was not a reply to your post, I know about the relation between jobs and SQL Server Agent :cool:I quoted the link from the explanation of the question. That link contains nothing about jobs and SQL Server Agents and should be corrected.Thu, 26 Nov 2009 03:10:50 GMTvk-kirovhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxYou can get SQL Agent on SQL 2008 Express Edition to start. You need to set up account rights and enable the agent XPs. But as soon as it starts it gives a message that Agent is not supported on Express edition and then stops. IMHO this is a case where you win the battle but loose the war.Thu, 26 Nov 2009 03:04:39 GMTEdVassiehttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxWe have had a number of questions which included a deliberate spelling error that had an answer xxx is wrong because it does not exist. As far as I know 'Enterprize' edition does not exist, but I have heard of 'Enterprise' edition and would have selected that if it was given in the question.Thu, 26 Nov 2009 03:01:29 GMTEdVassiehttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspx[quote]I can't see anything about jobs there. The link seems to be not relevant to the question.[/quote]What is the use of a job if there is no service to be executed (scheduled) with? Any new features in 2008 Express?See [url]http://msdn.microsoft.com/en-us/library/ms190268.aspx[/url]:exclamation:[quote]2. Expand SQL Server Agent.[/quote]Thu, 26 Nov 2009 02:35:51 GMTdawrynhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspx[quote]Ref: Editions and Components of SQL Server 2005 - [url]http://msdn.microsoft.com/en-us/library/ms144275%28SQL.90%29.aspx[/url][/quote]I can't see anything about jobs there. The link seems to be not relevant to the question.Thu, 26 Nov 2009 02:22:36 GMTvk-kirovhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxAccording to [url=http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx]http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx (SQL Server 2008 - Compare Edition Features)[/url] under Enterprise Manageability there is no SQL Server Agent in Express Edition:exclamationmark:How does anyone create and execute a job without this service?Thu, 26 Nov 2009 02:18:55 GMTdawrynhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxAre you able to start SQL Server Agent in SQL Server 2008 Express Edition?I can't find any proof of this.According to http://msdn.microsoft.com/en-us/library/cc645993.aspx it is not supported.Please explain.thanks,RobbertThu, 26 Nov 2009 01:55:21 GMTRobbert Hofhttp://www.sqlservercentral.com/Forums/Topic825065-1698-1.aspxComments posted to this topic are about the item [B]<A HREF="/questions/SQL+Agent/68153/">SQL Server Jobs</A>[/B]Wed, 25 Nov 2009 23:43:43 GMTlankenr