March 2, 2016 at 4:54 pm
Hi,
When I right click and tried to select top 1000 from msdb. This option is not highlighted.
Any idea?
SQL 2014 Standard edition in cluster environment
March 2, 2016 at 7:23 pm
The option to do this via SSMS 2014 is disabled on system tables in system databases on any SQL Server (2005+ has been tested). User tables in system databases are okay. SSMS 2012 still allows you to select top 1000 on system tables.
March 2, 2016 at 7:46 pm
sickb00000y (3/2/2016)
The option to do this via SSMS 2014 is disabled on system tables in system databases on any SQL Server (2005+ has been tested). User tables in system databases are okay. SSMS 2012 still allows you to select top 1000 on system tables.
Jeez... another "great improvement". Microsoft has time to do that silly kind of thing but no time to build in a decent splitter or even a machine language level Tally function. Shoot, they won't even spend time on the 44X+ performance problem introduced with FORMAT, but they have the time to do silly stuff to make life just a little bit more complicated for the DBA. <headdesk>.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2016 at 6:31 am
Jeff Moden (3/2/2016)
sickb00000y (3/2/2016)
The option to do this via SSMS 2014 is disabled on system tables in system databases on any SQL Server (2005+ has been tested). User tables in system databases are okay. SSMS 2012 still allows you to select top 1000 on system tables.Jeez... another "great improvement". Microsoft has time to do that silly kind of thing but no time to build in a decent splitter or even a machine language level Tally function. Shoot, they won't even spend time on the 44X+ performance problem introduced with FORMAT, but they have the time to do silly stuff to make life just a little bit more complicated for the DBA. <headdesk>.
And?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 3, 2016 at 7:12 am
Grant Fritchey (3/3/2016)
Jeff Moden (3/2/2016)
sickb00000y (3/2/2016)
The option to do this via SSMS 2014 is disabled on system tables in system databases on any SQL Server (2005+ has been tested). User tables in system databases are okay. SSMS 2012 still allows you to select top 1000 on system tables.Jeez... another "great improvement". Microsoft has time to do that silly kind of thing but no time to build in a decent splitter or even a machine language level Tally function. Shoot, they won't even spend time on the 44X+ performance problem introduced with FORMAT, but they have the time to do silly stuff to make life just a little bit more complicated for the DBA. <headdesk>.
And?
Not sure what you're looking for with your "And?" question. If I had to answer that, it would be "And I don't know why Microsoft continues to spend time and effort on such silly things that remove useful functionality instead of fixing or adding functionality that could be useful. Heh... I should borrow your shirt and pay them a visit. You know the one... It says "I may look calm but, in my mind, I've killed you 3 times". 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2016 at 7:23 am
Jeff Moden (3/3/2016)
Grant Fritchey (3/3/2016)
Jeff Moden (3/2/2016)
sickb00000y (3/2/2016)
The option to do this via SSMS 2014 is disabled on system tables in system databases on any SQL Server (2005+ has been tested). User tables in system databases are okay. SSMS 2012 still allows you to select top 1000 on system tables.Jeez... another "great improvement". Microsoft has time to do that silly kind of thing but no time to build in a decent splitter or even a machine language level Tally function. Shoot, they won't even spend time on the 44X+ performance problem introduced with FORMAT, but they have the time to do silly stuff to make life just a little bit more complicated for the DBA. <headdesk>.
And?
Not sure what you're looking for with your "And?" question. If I had to answer that, it would be "And I don't know why Microsoft continues to spend time and effort on such silly things that remove useful functionality instead of fixing or adding functionality that could be useful. Heh... I should borrow your shirt and pay them a visit. You know the one... It says "I may look calm but, in my mind, I've killed you 3 times". 😛
Ha! I was just having fun.
yeah, they spend time on silly stuff instead of on the core product. They're updating the SSMS type-ahead. It's still not going to be anywhere near as good as SQL Prompt, but they're spending time & resources on it when they should just let us get it done. Convincing them to spend time and effort on the core product, the one thing that third party people can't touch, just seems impossible.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 4, 2016 at 1:47 pm
Hi,
Here is what I am seeing.
I have SQL Non-Cluster 12.0.2254, which I can able to select top 1000 from msdb using GUI.
And I have SQL Server Cluster 12.0.4213, which I can't able to select top 1000 or edit top 200 from msdb using GUI
March 4, 2016 at 2:24 pm
But, what version is the SSMS tool that you're using on both?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 4, 2016 at 4:21 pm
Both of them are MicrosoftSqlServer 2014.
I selected the management studio from the Microsoft SQL Server 2014 folder in both machines.
March 4, 2016 at 4:34 pm
It's got to be due to the version.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 4, 2016 at 7:04 pm
This has nothing to do with the question that's already been answered.
You know, Grant, you could sell those shirts that Jeff mentioned. I've seen the picture of you in in while holding the bat. I could use one of those - the shirt, not the bat. Some days... 😉
March 5, 2016 at 6:39 am
Ed Wagner (3/4/2016)
This has nothing to do with the question that's already been answered.
Actually, I wonder if the question has been answered. 🙂
I wonder if it's a "security" feature kind of like, depending on how the system is setup, you can't restart the SQL Server Service from SSMS unless you opened SSMS by invoking "Run As Administrator". I wonder if this feature has been extended to when you try to view system tables.
I don't have 2014 installed to test that idea.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2016 at 4:07 pm
Jeff Moden (3/5/2016)
Ed Wagner (3/4/2016)
This has nothing to do with the question that's already been answered.Actually, I wonder if the question has been answered. 🙂
I wonder if it's a "security" feature kind of like, depending on how the system is setup, you can't restart the SQL Server Service from SSMS unless you opened SSMS by invoking "Run As Administrator". I wonder if this feature has been extended to when you try to view system tables.
I don't have 2014 installed to test that idea.
Touche, sir. It sounded like it had been answered, but I can't test it either. I have to admit that it does sound like something Microsoft would do. Then again, I don't use it anyway. Call me old-fashioned, but I just type the select statement.
However, Grant could still market those shirts. 😉
March 28, 2016 at 11:30 pm
I've been on holidays, but here's connecting to a SQL Server 2014 RTM instance from SSMS 2014: http://imgur.com/V7IHi1Z (embedding didn't work)
I haven't been able to test the "Run As Administrator" option because I don't have SSMS installed on any of our servers with 2014 running. Running under the sa account doesn't change it either.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply