December 4, 2019 at 6:23 pm
It pisses me off, as well. It does help my scheduling of "urgencies" though. 😀 I keep solid records of such abuses of the word "Urgent". I'm also not afraid of confronting the manager of such individuals and educating them on why such "Cry Wolf" urgencies can actually hurt the business. Such things don't actually happen to me often anymore because they know that if it turns out to be another abuse of the word "Urgent", I'll cut off their head, crap in their neck, and use their head for an ashtray. 😀
Ditto for me, though not the head cutting part. I document, and let them know I'm not jumping for anything again if they abuse the urgent word. I'll happily defend my slower pace to management.
December 4, 2019 at 6:27 pm
Is anyone one else still getting directed to the wrong page of responses? I was on the 'Active Threads' view and clicked on the link for Josana.work response on this thread and it took me to the prior page(4,279). This is very annoying, thought it would've been fixed by now.
Even posting this response takes me back to the prior page.
It was fixed, then regressed somewhere. It's an open bug again
December 4, 2019 at 7:00 pm
If anyone is interested in a rather interesting problem has a look at this: https://www.sqlservercentral.com/forums/topic/table-function-returns-varying-number-of-records-for-an-update-statement
I gave up.
-- Itzik Ben-Gan 2001
December 4, 2019 at 7:18 pm
p.s. I've also adopted the policy of NVO (No Verbal Orders), especially for "urgencies". It there's not a well documented ticket to support the urgency, it doesn't get done. While that sounds like I'm being nothing more than an Ahole, I'm not. It supports audits and a whole bunch of other things and I've gotten management support on that. It's actually written into our SOPs on the company WIKI.
I've kind of adopted the policy of, does it require changing production data? that's a ticket. Will it take me 30 minutes or less to get the data you want/help you and i like you? no ticket. Otherwise ticket.
December 4, 2019 at 8:22 pm
Jeff Moden wrote:p.s. I've also adopted the policy of NVO (No Verbal Orders), especially for "urgencies". It there's not a well documented ticket to support the urgency, it doesn't get done. While that sounds like I'm being nothing more than an Ahole, I'm not. It supports audits and a whole bunch of other things and I've gotten management support on that. It's actually written into our SOPs on the company WIKI.
I've kind of adopted the policy of, does it require changing production data? that's a ticket. Will it take me 30 minutes or less to get the data you want/help you and i like you? no ticket. Otherwise ticket.
Even if I like them I request a ticket. Too many times that less than 30 minute original request balloons to a half a day when they keep asking for multiple revisions because they didn't know what they really wanted.
Sorry Jasona.work I misspelled your name in my last post. Thanks Eirikur for pointing out my mistake. 🙂
-------------------------------------------------------------
we travel not to escape life but for life not to escape us
Don't fear failure, fear regret.
December 4, 2019 at 9:02 pm
I wonder whether I will be cast out from The Thread as a maverick grammar nutjob for suggesting that NSO would be a better abbreviation, given that 'verbal' means pertaining to words (be they written or spoken).
December 4, 2019 at 9:29 pm
I wonder whether I will be cast out from The Thread as a maverick grammar nutjob for suggesting that NSO would be a better abbreviation, given that 'verbal' means pertaining to words (be they written or spoken).
I'll see your grammatical nutjob and raise you two. 😀 According to definition "1.c" at the following link, verbal means not including any action. So NVO still works for tickets because it requires them to take action and write the ticket. Further, definition 3 specifically quantifies the difference as being "spoken rather than written".
https://www.merriam-webster.com/dictionary/verbal
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 9:33 pm
Phil Parkin wrote:I wonder whether I will be cast out from The Thread as a maverick grammar nutjob for suggesting that NSO would be a better abbreviation, given that 'verbal' means pertaining to words (be they written or spoken).
Did I miss something some where?
About getting orders for urgencies. He's suggesting to use NSO (No Spoken Orders) instead of NVO (No Verbal Orders) as mentioned by Jeff.
December 5, 2019 at 12:59 am
ZZartin wrote:Jeff Moden wrote:p.s. I've also adopted the policy of NVO (No Verbal Orders), especially for "urgencies". It there's not a well documented ticket to support the urgency, it doesn't get done. While that sounds like I'm being nothing more than an Ahole, I'm not. It supports audits and a whole bunch of other things and I've gotten management support on that. It's actually written into our SOPs on the company WIKI.
I've kind of adopted the policy of, does it require changing production data? that's a ticket. Will it take me 30 minutes or less to get the data you want/help you and i like you? no ticket. Otherwise ticket.
Even if I like them I request a ticket. Too many times that less than 30 minute original request balloons to a half a day when they keep asking for multiple revisions because they didn't know what they really wanted.
Sorry Jasona.work I misspelled your name in my last post. Thanks Eirikur for pointing out my mistake. 🙂
Yeah that's why it's a privilege reserved for people i like 😛 one of those criteria being I know they won't waste my time.
December 5, 2019 at 9:20 am
p.s. I've also adopted the policy of NVO (No Verbal Orders), especially for "urgencies". It there's not a well documented ticket to support the urgency, it doesn't get done. While that sounds like I'm being nothing more than an Ahole, I'm not. It supports audits and a whole bunch of other things and I've gotten management support on that. It's actually written into our SOPs on the company WIKI.
This is something we have for everything now, even the really simple stuff; as we got fed up of people abusing "urgents" at times. People will call us, and make a "urgent" work request, to which we remind them of the correct channels to raise a work ticket. Sometimes We've been chased a week later for that work, which they needed 2 days earlier, but then respond with "I didn't have to raise the ticket" when we say we can't find it. They literally take 2 minutes; if it was that urgent you would find those 2 minutes of time.
It does work really well though, as I'm sure many have found as well. People get a little "annoyed" by it, but those are many people that can't be bothered to make the request; but then why should we be bothered to do the work for them then? 😉
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
December 5, 2019 at 3:33 pm
That feeling when you want to point out that someone isn't correct about what they said, but you don't want to derail a topic and / or annoy said person...
🙂
December 5, 2019 at 3:36 pm
That feeling when you want to point out that someone isn't correct about what they said, but you don't want to derail a topic and / or annoy said person...
🙂
What did I get wrong this time?
"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
Viewing 15 posts - 64,186 through 64,200 (of 66,816 total)
You must be logged in to reply to this topic. Login to reply