Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Job Steps


SQL Server Job Steps

Author
Message
Sean Lange
Sean Lange
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16624 Visits: 17024
rmechaber (3/24/2011)
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 tested their question on?

Rich



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.

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Moden's splitter.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Understanding and Using APPLY (Part 1)
Understanding and Using APPLY (Part 2)
Rich Mechaber
Rich Mechaber
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1087 Visits: 3661
Sean Lange (3/24/2011)
rmechaber (3/24/2011)
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 tested their question on?

Rich



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.


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
kevin.l.williams
kevin.l.williams
Hall of Fame
Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)

Group: General Forum Members
Points: 3379 Visits: 1323
rmechaber (3/24/2011)
Sean Lange (3/24/2011)
rmechaber (3/24/2011)
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 tested their question on?

Rich



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.


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


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



BarbW
BarbW
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3087 Visits: 1130
I respectfully agree with the previous requests to identify the version/settings specific to the question and answer. :-)
Sean Lange
Sean Lange
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16624 Visits: 17024
kevin.l.williams (3/24/2011)
rmechaber (3/24/2011)
Sean Lange (3/24/2011)
rmechaber (3/24/2011)
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 tested their question on?

Rich



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.


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


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


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.

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Moden's splitter.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Understanding and Using APPLY (Part 1)
Understanding and Using APPLY (Part 2)
Chris Harshman
Chris Harshman
SSCrazy
SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)

Group: General Forum Members
Points: 2689 Visits: 3289
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 ;-)
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21099 Visits: 18259
Thanks for the question



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

OCTom
OCTom
SSCrazy
SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)

Group: General Forum Members
Points: 2815 Visits: 4152
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
RedJackal
RedJackal
SSC Journeyman
SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)

Group: General Forum Members
Points: 91 Visits: 41
If only you could run a Reporting Services Report Subscription as a Job Task...
Rich Mechaber
Rich Mechaber
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1087 Visits: 3661
RedJackal (3/24/2011)
If only you could run a Reporting Services Report Subscription as a Job Task...

I haven't worked through this bookmarked site, but it looks tempting: http://msdn.microsoft.com/en-us/library/ff793463.aspx

Rich
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