SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Jobs


SQL Server Jobs

Author
Message
Ken Garrett
Ken Garrett
SSC-Addicted
SSC-Addicted (408 reputation)SSC-Addicted (408 reputation)SSC-Addicted (408 reputation)SSC-Addicted (408 reputation)SSC-Addicted (408 reputation)SSC-Addicted (408 reputation)SSC-Addicted (408 reputation)SSC-Addicted (408 reputation)

Group: General Forum Members
Points: 408 Visits: 171
Hopefully 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.
Noel McKinney
Noel McKinney
SSCrazy
SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)

Group: General Forum Members
Points: 2085 Visits: 798
I had to laugh at the LOLCats spelling of Enterprise as Enterprize! Too bad the question wasn't written in LOLCats as well... "I can haz SQL j0bz in which edishunz?":-D
david.wright-948385
david.wright-948385
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1268 Visits: 979
kevin.l.williams (11/27/2009)
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?


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...
david.wright-948385
david.wright-948385
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1268 Visits: 979
david.wright-948385 (11/30/2009)
kevin.l.williams (11/27/2009)
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?


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...


Could even add "catch-up" logic to run jobs missed while the instance was down :-)
Luke L
Luke L
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4160 Visits: 6128
I 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.aspx

To help us help you read this

For better help with performance problems please read this
Chad Crawford
 Chad Crawford
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2904 Visits: 18718
Crud, 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.

Chad
Trekman
Trekman
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 131
(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 issues
Tom Thomson
Tom Thomson
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14888 Visits: 12238
In 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.

Tom

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search