July 18, 2018 at 11:04 am
I have been using SQL Server 2008 SP2 for 2 years and didn't face that, today I upgraded to SP4 and noticed weird thing.
If I try to add a job and refresh the SSMS explorer , the green arrow will disappear but everything is working fine. Jobs are running and didn't notice any malfunctions.
I have to re-open new SSMS connection and green arrow is back
I have administrator privileges
July 18, 2018 at 11:07 am
bissagars - Wednesday, July 18, 2018 11:04 AMI have been using SQL Server 2008 SP2 for 2 years and didn't face that, today I upgraded to SP4 and noticed weird thing.
If I try to add a job and refresh the SSMS explorer , the green arrow will disappear but everything is working fine. Jobs are running and didn't notice any malfunctions.
I have to re-open new SSMS connection and green arrow is backI have administrator privileges
It's not a fault.... it's a "feature". It means that if want to do certain things, you'll need to "Run as Administrator" to do them. For example, attaching MDF and LDF files to attach a previous detached database. Same holds true for SQL Server Agent. Unless you "Run as Administrator" to get into SSMS, you might not be able to (for example) shut down the SQL Server Agent from SSMS.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2018 at 11:15 am
Jeff Moden - Wednesday, July 18, 2018 11:07 AMIt's not a fault.... it's a "feature". It means that if want to do certain things, you'll need to "Run as Administrator" to do them. For example, attaching MDF and LDF files to attach a previous detached database. Same holds true for SQL Server Agent. Unless you "Run as Administrator" to get into SSMS, you might not be able to (for example) shut down the SQL Server Agent from SSMS.
I am already running the server as Administrator
July 18, 2018 at 11:25 am
bissagars - Wednesday, July 18, 2018 11:15 AMJeff Moden - Wednesday, July 18, 2018 11:07 AMIt's not a fault.... it's a "feature". It means that if want to do certain things, you'll need to "Run as Administrator" to do them. For example, attaching MDF and LDF files to attach a previous detached database. Same holds true for SQL Server Agent. Unless you "Run as Administrator" to get into SSMS, you might not be able to (for example) shut down the SQL Server Agent from SSMS.
I am already running the server as Administrator
I don't mean as a sys_admin. I mean for how you start SSMS. If you right click on the SSMS icon to start it, you see an entry for "Run as Administrator". That's what I'm talking about.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2018 at 11:32 am
Jeff Moden - Wednesday, July 18, 2018 11:25 AMbissagars - Wednesday, July 18, 2018 11:15 AMJeff Moden - Wednesday, July 18, 2018 11:07 AMIt's not a fault.... it's a "feature". It means that if want to do certain things, you'll need to "Run as Administrator" to do them. For example, attaching MDF and LDF files to attach a previous detached database. Same holds true for SQL Server Agent. Unless you "Run as Administrator" to get into SSMS, you might not be able to (for example) shut down the SQL Server Agent from SSMS.
I am already running the server as Administrator
I don't mean as a sys_admin. I mean for how you start SSMS. If you right click on the SSMS icon to start it, you see an entry for "Run as Administrator". That's what I'm talking about.
I tried to run the SSMS as Administrator, it is the same. Please take a look on this video.
July 18, 2018 at 12:01 pm
Dunno then. I've not had nor have been able to duplicate that problem if running as administrator.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2018 at 12:07 pm
I just tried the new SSMS V17, and I can't duplicate the issue with the new SSMS.
So maybe a bug with the old SSMS supplied with the SP4 update, not sure but I can duplicate the issue on different servers if using the old SSMS.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply