November 26, 2019 at 9:34 am
Thanks Steve Jones for the article. After uninstalling native client the 2019 worked
November 26, 2019 at 12:01 pm
Seems like the spam is ramping up again.
November 26, 2019 at 2:36 pm
Don't you just love it when you get a "urgent" work request that needs to be done "NOW", because it's impacting staff productivity, so you get the work done in dev and test it (all works), up scale it to UAT and advise it's ready for testing within a day; because it's "urgent".
Then, one month later, as you're working through out standing commits, you stumble across this "urgent" work that's still not in Live and think "Ooops, maybe i missed the feedback." So you send an email across, double checking that testing was completed and successful, and apologise that it hadn't been deployed yet, to get the response "Oh, we weren't planning to look at that until January".
Was it really that urgent you had to escalate the issue to the directors that you wanted it fixed "NOW" if you aren't going to even look at the build for 3 months?! Argh. >_<
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 26, 2019 at 2:51 pm
Don't you just love it when you get a "urgent" work request that needs to be done "NOW", because it's impacting staff productivity, so you get the work done in dev and test it (all works), up scale it to UAT and advise it's ready for testing within a day; because it's "urgent".
Then, one month later, as you're working through out standing commits, you stumble across this "urgent" work that's still not in Live and think "Ooops, maybe i missed the feedback." So you send an email across, double checking that testing was completed and successful, and apologise that it hadn't been deployed yet, to get the response "Oh, we weren't planning to look at that until January".
Was it really that urgent you had to escalate the issue to the directors that you wanted it fixed "NOW" if you aren't going to even look at the build for 3 months?! Argh. >_<
One good thing about this is the amount of ammo now in your possession when the next 'urgent' request comes up!
November 26, 2019 at 3:03 pm
Thom A wrote:Don't you just love it when you get a "urgent" work request that needs to be done "NOW", because it's impacting staff productivity, so you get the work done in dev and test it (all works), up scale it to UAT and advise it's ready for testing within a day; because it's "urgent".
Then, one month later, as you're working through out standing commits, you stumble across this "urgent" work that's still not in Live and think "Ooops, maybe i missed the feedback." So you send an email across, double checking that testing was completed and successful, and apologise that it hadn't been deployed yet, to get the response "Oh, we weren't planning to look at that until January".
Was it really that urgent you had to escalate the issue to the directors that you wanted it fixed "NOW" if you aren't going to even look at the build for 3 months?! Argh. >_<
One good thing about this is the amount of ammo now in your possession when the next 'urgent' request comes up!
Nah... always do "urgent" requests quickly. They're almost never urgent and will frequently end up like the one did for Thom but you can really gain the upper hand on these types of things. First, if they really are urgent, you are a hero. If they end up like Thom's, then it's already done, there's no chance of you failing to hit the deadline, and you know what to expect for deadlines in the future when it comes to people wanting to make changes because they didn't actually know what the hell it is they actually need but knew something had to be done even if it was wrong and you still end up the hero but, sometimes, with apologies from the idiots that were urgent. 😀
Remember... it doesn't matter if something is urgent or not... we get paid the same no matter what. If we can look good doing it and solve people's urgencies quickly, that might help us on our next annual review and help us get a pay raise. If nothing else, keep a list of such urgencies because, on a pick'n'choose basis, they can look damned good on a resume. 😀
I do STRONGLY agree that urgencies should not turn your job into regular 60-80 hour work weeks.
And remember, practice NVO... No Verbal Orders, especially for urgencies. If you have a ticketing system, make damned sure it's used for such things. If you don't, make sure there's an email chain that you save. People with urgencies are also the first to look for scape-goats when THEY fail to urgently perform on their own urgency. It's a shame that things turn out that way but they almost always do.
I've also found that if you get people to write their "gotta have it NOWs" in the form of a ticket or an "official email", a lot of urgencies simply vanish or the real truth about them being needed in several months suddenly appears.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 2:47 pm
What I hate is when you get the 'Urgent' email on a request for some data. Then you spend the rest of the day working on it. Then the next day when you are ready to send the data you get that the person is out of the office for the next couple days. Was it really that urgent? Nope, then you follow up a few days after they get back in the office and they say "I haven't had time to look at it." Boy that really pisses me off.
-------------------------------------------------------------
we travel not to escape life but for life not to escape us
Don't fear failure, fear regret.
December 4, 2019 at 3:12 pm
What I hate is when you get the 'Urgent' email on a request for some data. Then you spend the rest of the day working on it. Then the next day when you are ready to send the data you get that the person is out of the office for the next couple days. Was it really that urgent? Nope, then you follow up a few days after they get back in the office and they say "I haven't had time to look at it." Boy that really pisses me off.
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. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 3:15 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.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 3:51 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 don't get the verbal ones either anymore, at least at this job. My old job it seemed like a constant flood of them. We didn't really have a good ticket request system, not after we dropped Lotus Notes and that killed the one I had created. Now everything has a Jira ticket, we got to keep track of how we spend our hours each day. <eye roll>
-------------------------------------------------------------
we travel not to escape life but for life not to escape us
Don't fear failure, fear regret.
December 4, 2019 at 3:52 pm
Often times around here we get the "urgent" request which will be followed up with a response asking for clarity about the details of what they actually want. And so many times it will go several months before they finally get around to providing the details of what was so urgent. Other times no response ever comes. Very few things are truly urgent in the real world. They are just the current most important thing because that is what they are thinking about right now.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
December 4, 2019 at 4:14 pm
ARGH!
So, I'm selling a house and I'm going to have a bloody ulcer before it's sold at this rate.
First, weird issues with the title and a mortgage that was paid off but still listed on a lookup site.
NOW the BUYER is having some issues and our closing has been pushed back from last week, to this week maybe by Friday, to now sometime maybe early next week...
But, at least some good news for this week, we've got the systems hooked up to begin prepping for our migration to a "cloud" which is basically using backups of our data to do it (we're standing up new VMs in the cloud.) So I now have TOTAL CONTROL (/insert maniacal cackle) of my database backups! It also helps that the migration devices do the backups in WAY less time than the backup system our NEC uses (looks like it does a "snapshot" then backs up the snapshots, as well as the transaction log backups)
If anyone has heard of "Rubrik" backup systems, that's what we're using. The truth of how good it is will be when I do a local test restore, of course.
December 4, 2019 at 5:32 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.
-------------------------------------------------------------
we travel not to escape life but for life not to escape us
Don't fear failure, fear regret.
December 4, 2019 at 5:43 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.
Yes, I landed on the earlier page when responding to your post, slightly odd to say the least.
😎
BTW: do you have any insight information on Jason, has he gone a 180 circle or was Jasona just a misspelling?
December 4, 2019 at 5:46 pm
BTW: do you have any insight information on Jason, has he gone a 180 circle or was Jasona just a misspelling?
Heh. First name, last initial run together.
Edited to add: Also, I get the preceding page as well, both when hitting the link from the forum to go to the last post, and when I submitted this post
Viewing 15 posts - 64,171 through 64,185 (of 66,816 total)
You must be logged in to reply to this topic. Login to reply