October 15, 2012 at 10:56 pm
Keeping the title as noise ; kool ...
stoplists; I wasn't sure of the nomenclature but I got that correct after reading an article ...
nice to learn something.
thanks for the question
~ demonfox
___________________________________________________________________
Wondering what I would do next , when I am done with this one :ermm:
October 15, 2012 at 11:20 pm
Thanks Steve. I was not aware of this. Got to learn something new today 🙂
~ Lokesh Vij
Link to my Blog Post --> www.SQLPathy.com[/url]
Follow me @Twitter
October 15, 2012 at 11:53 pm
As sql server version was not specified so I selected NoiseList but got wrong...
I think version should be mentioned in question..
learn new thing today.......
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
October 16, 2012 at 12:19 am
kapil190588 (10/15/2012)
As sql server version was not specified so I selected NoiseList but got wrong...I think version should be mentioned in question..
learn new thing today.......
If it were different in two supported editions of SQL Server, I agree. However, SQL Server 2005 is not supported anymore, so this question is correct for all supported editions of SQL Server.
October 16, 2012 at 12:27 am
kapil190588 (10/15/2012)
As sql server version was not specified so I selected NoiseList but got wrong...I think version should be mentioned in question..
learn new thing today.......
Although getting it right, I concur with kapil190588 that the version should somehow be mentioned. I had to google a little to find the answer, and did have to work my way through a couple of SQL server versions to end up with the Stop List.
But thanks for the question anyway.
🙂
October 16, 2012 at 1:21 am
This was removed by the editor as SPAM
October 16, 2012 at 1:37 am
I hadn't come across this before, so just glad to get the point.
Thanks Steve.
October 16, 2012 at 2:48 am
okbangas (10/16/2012)
kapil190588 (10/15/2012)
As sql server version was not specified so I selected NoiseList but got wrong...I think version should be mentioned in question..
learn new thing today.......
If it were different in two supported editions of SQL Server, I agree. However, SQL Server 2005 is not supported anymore, so this question is correct for all supported editions of SQL Server.
When I saw the question and the list of answers, I *knew* there would be debate over this.
However, I agree with Okbangas - the question is fine without mentioning the version. And not just because SQL Server 2005 is out of date. I might have at least somewhat concurred with Kapil if that were the only argument. However, the "correct" answer for SQL Server 2005 and before was not included.
In SQL Server 2005, the words to be ignored were called "noise words". But lists of those words were not ever called "noise lists" - they were called "noise word files". So even those who have only experience with SQL Server 2005 and prior should have been able to realize that a name change had happened, and that they needed to do more research.
I think this was a great question, Steve! 🙂
October 16, 2012 at 2:52 am
thanks Hugo for the explanation....
I am not much aware about this and only thing I knew that somewhat there is word like noise list in sql server 2005 that's why i select that option...
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
October 16, 2012 at 3:04 am
okbangas (10/16/2012)
If it were different in two supported editions of SQL Server, I agree. However, SQL Server 2005 is not supported anymore, so this question is correct for all supported editions of SQL Server.
I didn't realize SQLServerCentral had support dates too. Microsoft has SQL 2000 on Extended Support for another six months or so, and SQL 2005 is still in Extended Support too... ("Microsoft offers a minimum of 10 years of support for SQL Server products.") What are SQLServerCentral support dates?
I got today's question correct, but only because I'd recently been studying for the 2008 exams...
October 16, 2012 at 3:47 am
Rich Weissler (10/16/2012)
okbangas (10/16/2012)
If it were different in two supported editions of SQL Server, I agree. However, SQL Server 2005 is not supported anymore, so this question is correct for all supported editions of SQL Server.I didn't realize SQLServerCentral had support dates too. Microsoft has SQL 2000 on Extended Support for another six months or so, and SQL 2005 is still in Extended Support too... ("Microsoft offers a minimum of 10 years of support for SQL Server products.") What are SQLServerCentral support dates?
I got today's question correct, but only because I'd recently been studying for the 2008 exams...
We've had this debate before, and the concensus seemed to be that QotD refers to SQL Server versions currently under full support, not those under extended support, and that the version has to be specified if and only if there is a version currently in full support for which the answer is wrong.
Tom
October 16, 2012 at 4:09 am
Thanks for the question.
October 16, 2012 at 4:47 am
L' Eomot Inversé (10/16/2012)QotD refers to SQL Server versions currently under full support, not those under extended support
Excellent. Thank you.
And, of course, good question today.
October 16, 2012 at 6:00 am
I concur with kapil190588 that the version should somehow be mentioned.
Please see http://msdn.microsoft.com/en-us/library/ms142551(v=sql.90).aspx - noise-word list (LIST!)
Viewing 15 posts - 1 through 15 (of 30 total)
You must be logged in to reply to this topic. Login to reply