May 29, 2010 at 11:08 pm
Bug got reported to Microsoft back in December 2008, although Microsoft did not post a response until April 2009.
It states the INNER JOIN is the issue, as Peter and Paul (:w00t:and Mary, now how many times do you see this come up:-)). MS goes on to state it will be fixed in SQL 11. So would that not be SQL Server 2008 R2 :-D. Anyone have SSMS 2008 R2 loaded that could test this, or have tested it?
:hehe:, just need one more to make it even.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
May 29, 2010 at 11:39 pm
MeltonDBA (5/29/2010)
Bug got reported to Microsoft back in December 2008, although Microsoft did not post a response until April 2009.
Excellent find! I voted it up. There's a partial workaround there too which is good.
It states the INNER JOIN is the issue, as Peter and Paul (:w00t:and Mary, now how many times do you see this come up:-)).
Hmmm...we could do with a Mary on the forums, it's true :laugh:
Showing your age a bit there Melton? 😛
MS goes on to state it will be fixed in SQL 11. So would that not be SQL Server 2008 R2 :-D.
Nope, R2 is not a major release - it's version 10.5 (Kilimanjaro)
SQL11 is code named Denali - and that's where I would expect this to be fixed.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
June 7, 2010 at 10:18 am
Good day all,
I know I'm late to this party, but I just want to thank every one who contributed to this thread. I've been battling this behavior for weeks, convinced I was missing something simple...
Henry Lee
February 15, 2011 at 1:27 pm
We have been dealing with this very issue.
I find it quite interesting that SSMS 2005 and 2008 version are not checking for the SQL Server version that is being connected to. I have also confirmed that SSMS is sending different SQL code to the database server at connection time. We do use GRANT VIEW DEFINITION for our DEV, TEST and (yes) some Production databases. We STILL have the problem of the SSMS v 2008 not showing what a person can view, when SSMS 2005 can. STUPID!!!
So, my 2 questions are:
We have encountered this with SSMS 2008 Express editions. Is this unique to the version of SSMS 2008?
Have we been able to differentiate the SSMS 2008 (a.k.a full client install as provided with SQL Server 2008) vs SSMS 2008 Express Edition?
If this issue the query being run by SSMS 2008 that it is sending to SQL Server 2005. WE, the SQL Server community, have a serious issue with the use of SSMS 2008 in an enterprise where SQL Server 2005 is still in use and in my opinion, I believe this is a backward-compatibility issue and MS needs to address this asap!
Eddy White, DBA
Viewing 4 posts - 31 through 33 (of 33 total)
You must be logged in to reply to this topic. Login to reply