<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Navnath
»
SQL Server Jobs
28 posts, Page 3 of 3
««
«
1
2
3
SQL Server Jobs
Rate Topic
Display Mode
Topic Options
Author
Message
Ken Garrett
Ken Garrett
Posted Friday, November 27, 2009 5:48 PM
Old Hand
Group: General Forum Members
Last Login: Thursday, July 19, 2012 12:50 PM
Points: 385,
Visits: 170
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.
Post #825782
Noel McKinney
Noel McKinney
Posted Sunday, November 29, 2009 10:47 AM
SSCrazy
Group: General Forum Members
Last Login: Thursday, April 05, 2012 2:35 PM
Points: 2,007,
Visits: 767
I had to laugh at the LOLCats spelling of Enterprise as Enterpri
z
e! Too bad the question wasn't written in LOLCats as well... "I can haz SQL j0bz in which edishunz?"
Post #825893
david.wright-948385
david.wright-948385
Posted Monday, November 30, 2009 2:57 AM
SSC Eights!
Group: General Forum Members
Last Login: 2 days ago @ 4:41 AM
Points: 909,
Visits: 596
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...
Post #826076
david.wright-948385
david.wright-948385
Posted Monday, November 30, 2009 3:00 AM
SSC Eights!
Group: General Forum Members
Last Login: 2 days ago @ 4:41 AM
Points: 909,
Visits: 596
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
Post #826078
Luke L
Luke L
Posted Monday, November 30, 2009 8:03 AM
SSCrazy
Group: General Forum Members
Last Login: 2 days ago @ 9:42 AM
Points: 2,891,
Visits: 5,858
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
Post #826224
Chad Crawford
Chad Crawford
Posted Tuesday, December 01, 2009 9:10 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 3:52 PM
Points: 2,549,
Visits: 17,363
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
Post #826776
Trekman
Trekman
Posted Wednesday, December 09, 2009 10:25 AM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, January 23, 2013 10:10 AM
Points: 2,
Visits: 101
(deleted post about "Enterprize" haha-how-funny-but-made-me-answer-wrong and going back to work instead of playing guessing games
)
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
Post #831605
L' Eomot Inversé
L' Eomot Inversé
Posted Saturday, January 30, 2010 12:03 PM
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 3:07 PM
Points: 7,096,
Visits: 7,156
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
Que conclure à la fin de tous mes longs propos? C'est que les préjugés sont la raison des sots. (Voltaire, 1756)
Post #856696
« Prev Topic
|
Next Topic »
28 posts, Page 3 of 3
««
«
1
2
3
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
