SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Abi Chapagai / SQL Server Job Steps / Latest Posts

RE: SQL Server Job Steps

zymos — Fri, 09 Mar 2012 14:07:35 GMT

Great question that is easy and reviews the SQL Server Agent job topic.

RE: SQL Server Job Steps

jfgoude — Sun, 01 May 2011 23:07:54 GMT

my erro : you can run a report subscription job but not create it

RE: SQL Server Job Steps

Simon-413722 — Mon, 04 Apr 2011 18:12:51 GMT

ouch!! i'm one of the many who didnt read the end of the question (select 4) and answer based on sql 2005 functionalities :(

RE: SQL Server Job Steps

Dave62 — Fri, 25 Mar 2011 08:00:08 GMT

[quote][b]SanDroid (3/24/2011)[/b][hr] ...Rich, I have suggested this many times in the past with many differant accounts. The answer has always been that QOTD is not moderated. The question is posted as it was originaly submitted. Errors and all. :cool:[/quote]I know, first hand, that this is not true. I recently submitted a QoD and received a response from an editor with suggestions for corrections. I have made the corrections and resubmitted the question and am waiting for a further response or for it to be published.Based on this experience it seems there is in fact moderation.

RE: SQL Server Job Steps

Abi Chapagai — Thu, 24 Mar 2011 20:50:11 GMT

Thanks all for the comments and suggestions. You all are correct that i should have mentioned the version of SQL Server in the question. I agree with you all that PowerShell is not available in SQL Server 2005. I was working in SQL Server 2008, and i thought to ask this question since there are many new features and wanted to share and learn from you all. I will try to be more specific in future QotD. Once again thank you all.

RE: SQL Server Job Steps

SanDroid — Thu, 24 Mar 2011 15:28:35 GMT

[quote][b]kevin.l.williams (3/24/2011)[/b][hr][quote][b]SanDroid (3/24/2011)[/b][hr][quote][b]rmechaber (3/24/2011)[/b][hr]These kinds of versioning problems with QoD are common enough and easily prevented: couldn't SSC require all submitters to specify which versions they have [u]tested[/u] their question on?[/quote]Rich, I have suggested this many times in the past with many differant accounts. The answer has always been that QOTD is not moderated. The question is posted as it was originaly submitted. Errors and all. :cool:[/quote]It should not be that difficult to add a field on the question submission screen that prompts the user to answer "What language and version of SQL was this tested on?" They don't even have to go that far, it could be a message next to the question input field that says "Don't forget to include SQL version and language tested on".[/quote]I am sure Steve could use your assistance in adding this. Perhaps you should contact him and volunteer your skills.

RE: SQL Server Job Steps

kevin.l.williams — Thu, 24 Mar 2011 15:23:58 GMT

[quote][b]SanDroid (3/24/2011)[/b][hr][quote][b]rmechaber (3/24/2011)[/b][hr]These kinds of versioning problems with QoD are common enough and easily prevented: couldn't SSC require all submitters to specify which versions they have [u]tested[/u] their question on?[/quote]Rich, I have suggested this many times in the past with many differant accounts. The answer has always been that QOTD is not moderated. The question is posted as it was originaly submitted. Errors and all. :cool:[/quote]It should not be that difficult to add a field on the question submission screen that prompts the user to answer "What language and version of SQL was this tested on?" They don't even have to go that far, it could be a message next to the question input field that says "Don't forget to include SQL version and language tested on".

RE: SQL Server Job Steps

SanDroid — Thu, 24 Mar 2011 14:27:38 GMT

Several have said it already, but I am going to say it again.Why did you not list the version of SQL server when it is obvious you where taking about SQL 2008 R2? It is good to remember that there is more than one version of everything when writing questions and articles about software and development.Unless confusing people and making them frustrated is your goal. Then you are on a path to sucess! :w00t:

RE: SQL Server Job Steps

SanDroid — Thu, 24 Mar 2011 14:20:30 GMT

[quote][b]rmechaber (3/24/2011)[/b][hr]These kinds of versioning problems with QoD are common enough and easily prevented: couldn't SSC require all submitters to specify which versions they have [u]tested[/u] their question on?[/quote]Rich, I have suggested this many times in the past with many differant accounts. The answer has always been that QOTD is not moderated. The question is posted as it was originaly submitted. Errors and all. :cool:

RE: SQL Server Job Steps

MyDoggieJessie — Thu, 24 Mar 2011 13:58:04 GMT

The question should have started with "In SQL Server 2005..." as Powershell is NOT an option in 2005.

RE: SQL Server Job Steps

rmechaber — Thu, 24 Mar 2011 13:45:01 GMT

[quote][b]RedJackal (3/24/2011)[/b][hr]If only you [i]could[/i] run a Reporting Services Report Subscription as a Job Task...[/quote]I haven't worked through this bookmarked site, but it looks tempting: [url=http://msdn.microsoft.com/en-us/library/ff793463.aspx]http://msdn.microsoft.com/en-us/library/ff793463.aspx[/url]Rich

RE: SQL Server Job Steps

RedJackal — Thu, 24 Mar 2011 12:26:26 GMT

If only you [i]could[/i] run a Reporting Services Report Subscription as a Job Task...

RE: SQL Server Job Steps

OCTom — Thu, 24 Mar 2011 11:40:37 GMT

Yup. I'm still stuck in 2005 mode. I didn't think Powershell was right for 2005 and I thought the report subscription was wrong, too. I flipped a coin and selected the report subscription option. :-D

RE: SQL Server Job Steps

SQLRNNR — Thu, 24 Mar 2011 10:41:47 GMT

Thanks for the question

RE: SQL Server Job Steps

Chris Harshman — Thu, 24 Mar 2011 10:36:57 GMT

I got it wrong... but for a different reason. The question said to pick 4, I probably would have picked all of them otherwise, since I know SSRS Report Subscriptions use SQL Agent jobs. I wasn't thinking of the question in terms of the Job Step Type dropdown. Oh well, not like my QOTD record here is all that great anyway ;-)

RE: SQL Server Job Steps

Sean Lange — Thu, 24 Mar 2011 10:34:03 GMT

[quote][b]kevin.l.williams (3/24/2011)[/b][hr][quote][b]rmechaber (3/24/2011)[/b][hr][quote][b]Sean Lange (3/24/2011)[/b][hr][quote][b]rmechaber (3/24/2011)[/b][hr]As others have pointed out, the "correct" answer is wrong. Powershell is NOT an option in 2005. I got it right for the wrong reason: I guessed that Powershell integration was more likely in in 2008 than an RS subscription.These kinds of versioning problems with QoD are common enough and easily prevented: couldn't SSC require all submitters to specify which versions they have [u]tested[/u] their question on?Rich[/quote]By that same logic it is also correct if the version is 2008. With no version specified it could be right OR wrong. You feel it is wrong because you are on 2005 and the author feels it is right because he is on 2008. I would definitely say that the QOTD lived up to its expectations in that it made you think and learn something. Version challenges will always be an issue with QOTD because we get cool new features with each new version and there are always going to be people that are not on the most current version.[/quote]Sean, I will respectfully disagree: if it's not always true, then it's false. There is no reason for these ambiguities to exist and persist in QoD, when it's easy enough for submitters to check the questions beforehand, either on their own systems or, if necessary to cover other versions, someone else's. At the very least, if the question were only marked as "Tested on SQL Server 2008 R2," we'd know that much.I don't care about getting points or the number of right answers I get. I care about misinformation propagated as truth. It is misleading and incorrect to identify a "correct" answer without qualifying the circumstances under which the answer is, in fact, correct.Rich[/quote]This type of issue has sparked some heated exchanges in recent QoDs. I second the request that all questions contain something like this "Tested on default install SQL Server XXXX, language: us_english". Kevin[/quote]I absolutely agree that version should be mentioned with every question. One of the biggest challenges is that we don't all have all the versions available to us. The version argument will continue until the end of time and as you suggested the best (and probably only) way to avoid it is to have the version number(s) as part of the question.

RE: SQL Server Job Steps

BarbW — Thu, 24 Mar 2011 10:23:05 GMT

I respectfully agree with the previous requests to identify the version/settings specific to the question and answer. :-)

RE: SQL Server Job Steps

kevin.l.williams — Thu, 24 Mar 2011 10:04:03 GMT

[quote][b]rmechaber (3/24/2011)[/b][hr][quote][b]Sean Lange (3/24/2011)[/b][hr][quote][b]rmechaber (3/24/2011)[/b][hr]As others have pointed out, the "correct" answer is wrong. Powershell is NOT an option in 2005. I got it right for the wrong reason: I guessed that Powershell integration was more likely in in 2008 than an RS subscription.These kinds of versioning problems with QoD are common enough and easily prevented: couldn't SSC require all submitters to specify which versions they have [u]tested[/u] their question on?Rich[/quote]By that same logic it is also correct if the version is 2008. With no version specified it could be right OR wrong. You feel it is wrong because you are on 2005 and the author feels it is right because he is on 2008. I would definitely say that the QOTD lived up to its expectations in that it made you think and learn something. Version challenges will always be an issue with QOTD because we get cool new features with each new version and there are always going to be people that are not on the most current version.[/quote]Sean, I will respectfully disagree: if it's not always true, then it's false. There is no reason for these ambiguities to exist and persist in QoD, when it's easy enough for submitters to check the questions beforehand, either on their own systems or, if necessary to cover other versions, someone else's. At the very least, if the question were only marked as "Tested on SQL Server 2008 R2," we'd know that much.I don't care about getting points or the number of right answers I get. I care about misinformation propagated as truth. It is misleading and incorrect to identify a "correct" answer without qualifying the circumstances under which the answer is, in fact, correct.Rich[/quote]This type of issue has sparked some heated exchanges in recent QoDs. I second the request that all questions contain something like this "Tested on default install SQL Server XXXX, language: us_english". Kevin

RE: SQL Server Job Steps

rmechaber — Thu, 24 Mar 2011 09:43:40 GMT

[quote][b]Sean Lange (3/24/2011)[/b][hr][quote][b]rmechaber (3/24/2011)[/b][hr]As others have pointed out, the "correct" answer is wrong. Powershell is NOT an option in 2005. I got it right for the wrong reason: I guessed that Powershell integration was more likely in in 2008 than an RS subscription.These kinds of versioning problems with QoD are common enough and easily prevented: couldn't SSC require all submitters to specify which versions they have [u]tested[/u] their question on?Rich[/quote]By that same logic it is also correct if the version is 2008. With no version specified it could be right OR wrong. You feel it is wrong because you are on 2005 and the author feels it is right because he is on 2008. I would definitely say that the QOTD lived up to its expectations in that it made you think and learn something. Version challenges will always be an issue with QOTD because we get cool new features with each new version and there are always going to be people that are not on the most current version.[/quote]Sean, I will respectfully disagree: if it's not always true, then it's false. There is no reason for these ambiguities to exist and persist in QoD, when it's easy enough for submitters to check the questions beforehand, either on their own systems or, if necessary to cover other versions, someone else's. At the very least, if the question were only marked as "Tested on SQL Server 2008 R2," we'd know that much.I don't care about getting points or the number of right answers I get. I care about misinformation propagated as truth. It is misleading and incorrect to identify a "correct" answer without qualifying the circumstances under which the answer is, in fact, correct.Rich

RE: SQL Server Job Steps

Sean Lange — Thu, 24 Mar 2011 09:08:51 GMT

[quote][b]rmechaber (3/24/2011)[/b][hr]As others have pointed out, the "correct" answer is wrong. Powershell is NOT an option in 2005. I got it right for the wrong reason: I guessed that Powershell integration was more likely in in 2008 than an RS subscription.These kinds of versioning problems with QoD are common enough and easily prevented: couldn't SSC require all submitters to specify which versions they have [u]tested[/u] their question on?Rich[/quote]By that same logic it is also correct if the version is 2008. With no version specified it could be right OR wrong. You feel it is wrong because you are on 2005 and the author feels it is right because he is on 2008. I would definitely say that the QOTD lived up to its expectations in that it made you think and learn something. Version challenges will always be an issue with QOTD because we get cool new features with each new version and there are always going to be people that are not on the most current version.

RE: SQL Server Job Steps

rmechaber — Thu, 24 Mar 2011 06:27:07 GMT

As others have pointed out, the "correct" answer is wrong. Powershell is NOT an option in 2005. I got it right for the wrong reason: I guessed that Powershell integration was more likely in in 2008 than an RS subscription.These kinds of versioning problems with QoD are common enough and easily prevented: couldn't SSC require all submitters to specify which versions they have [u]tested[/u] their question on?Rich

RE: SQL Server Job Steps

Surii — Thu, 24 Mar 2011 05:36:08 GMT

Nice and easy one..Thanks for the question.

RE: SQL Server Job Steps

cengland0 — Thu, 24 Mar 2011 03:30:58 GMT

[quote][b]Hugo Kornelis (3/24/2011)[/b][hr]A good question. It would have been a great question if the author had not forgotten to specify the version - Powershell is not supported in SQL Server 2005, so that might cause some incorrect replies.It was a nice touch to indicate the number of answers that has to be checked. Though this makes it easier as well - since there were only five options, I knew I had the correct answer as soon as I identified the one incorrect option. Would it not have been simpler to ask us to check the option that is [b]NOT[/b] a job step and require only a single answer?I hope to see more questions from this contributor.[/quote]Ah, that explains it. If it didn't say "Select Four," I would have gotten the question wrong because I frequently create Steps in Jobs have never seen "Powershell" or "Reporting Services Report Subscriptions" options so I would have only selected 3. I use 2005 and had to look this one up before answering to find the proper 4th option.

RE: SQL Server Job Steps

Chris Houghton — Thu, 24 Mar 2011 02:57:31 GMT

Good question and not too difficult. I did my certs in 2008 and so my natural inclination was to answer the question with that version in mind :-D

RE: SQL Server Job Steps

Hugo Kornelis — Thu, 24 Mar 2011 02:41:49 GMT

A good question. It would have been a great question if the author had not forgotten to specify the version - Powershell is not supported in SQL Server 2005, so that might cause some incorrect replies.It was a nice touch to indicate the number of answers that has to be checked. Though this makes it easier as well - since there were only five options, I knew I had the correct answer as soon as I identified the one incorrect option. Would it not have been simpler to ask us to check the option that is [b]NOT[/b] a job step and require only a single answer?I hope to see more questions from this contributor.

RE: SQL Server Job Steps

Balance — Thu, 24 Mar 2011 02:28:50 GMT

They got it wrong because they are using 2005 & the question doesn't specify the version and I suspect most businesses are still using 2005 for production systems.

RE: SQL Server Job Steps

mohammed moinudheen — Thu, 24 Mar 2011 02:05:09 GMT

Thanks for the question. Easy one. :-)

RE: SQL Server Job Steps

Koen Verbeeck — Thu, 24 Mar 2011 01:32:00 GMT

A bit easy, but still 40% (at the moment) got it wrong :blink:

RE: SQL Server Job Steps

UMG Developer — Wed, 23 Mar 2011 22:33:48 GMT

Thanks for the question!

SQL Server Job Steps

Abi Chapagai — Wed, 23 Mar 2011 22:33:25 GMT

Comments posted to this topic are about the item [B]SQL Server Job Steps[/B]