Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««123»»

SQL Server Job Steps Expand / Collapse
Author
Message
Posted Thursday, March 24, 2011 9:08 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 2:49 PM
Points: 13,069, Visits: 11,908
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)
Post #1083389
Posted Thursday, March 24, 2011 9:43 AM


Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Thursday, July 17, 2014 2:01 PM
Points: 687, Visits: 3,002
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
Post #1083421
Posted Thursday, March 24, 2011 10:04 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Friday, July 18, 2014 3:37 PM
Points: 3,123, Visits: 1,256
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



Post #1083437
Posted Thursday, March 24, 2011 10:23 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, July 21, 2014 10:03 AM
Points: 2,490, Visits: 1,026
I respectfully agree with the previous requests to identify the version/settings specific to the question and answer.
Post #1083450
Posted Thursday, March 24, 2011 10:34 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 2:49 PM
Points: 13,069, Visits: 11,908
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)
Post #1083459
Posted Thursday, March 24, 2011 10:36 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 7:43 AM
Points: 1,849, Visits: 2,009
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
Post #1083461
Posted Thursday, March 24, 2011 10:41 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 7:44 PM
Points: 21,209, Visits: 14,899
Thanks for the question



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


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1083464
Posted Thursday, March 24, 2011 11:40 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 1:36 PM
Points: 2,514, Visits: 3,705
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.
Post #1083499
Posted Thursday, March 24, 2011 12:26 PM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Friday, December 7, 2012 8:08 AM
Points: 91, Visits: 39
If only you could run a Reporting Services Report Subscription as a Job Task...
Post #1083518
Posted Thursday, March 24, 2011 1:45 PM


Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Thursday, July 17, 2014 2:01 PM
Points: 687, Visits: 3,002
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
Post #1083579
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse