June 8, 2016 at 5:43 am
djj (6/8/2016)
Ed Wagner (6/8/2016)
Jeff Moden (6/7/2016)
Lynn Pettis (6/7/2016)
Hugo Kornelis (6/7/2016)
GilaMonster (6/7/2016)
What I've advised for years is to notify on lack of success (eg: have a monitoring server check that the backup ran, and if it didn't, send mail)And then have another server monitor the monitoring server, and mail you when it has problems.
And then another, and another , ... when does the monitoring end? :w00t:
When the users call with a problem that you forgot to monitor for. 😉
There will always be one. The best one would be when one of the monitors sends an email saying that the email server is down. 😛
Reminds me of our internet provider that went down. They wanted us to post a message to their site. :crazy:
Yep - exactly the point. Or when there's a power outage and they report restoration estimates on the local TV news.
June 8, 2016 at 6:19 am
Ed Wagner (6/8/2016)
djj (6/8/2016)
Ed Wagner (6/8/2016)
Jeff Moden (6/7/2016)
Lynn Pettis (6/7/2016)
Hugo Kornelis (6/7/2016)
GilaMonster (6/7/2016)
What I've advised for years is to notify on lack of success (eg: have a monitoring server check that the backup ran, and if it didn't, send mail)And then have another server monitor the monitoring server, and mail you when it has problems.
And then another, and another , ... when does the monitoring end? :w00t:
When the users call with a problem that you forgot to monitor for. 😉
There will always be one. The best one would be when one of the monitors sends an email saying that the email server is down. 😛
Reminds me of our internet provider that went down. They wanted us to post a message to their site. :crazy:
Yep - exactly the point. Or when there's a power outage and they report restoration estimates on the local TV news.
Many years ago I worked for a company that created a training course for deaf people. And yes, they advertised it on the radio.
June 8, 2016 at 7:14 am
BrainDonor (6/8/2016)
Ed Wagner (6/8/2016)
djj (6/8/2016)
Ed Wagner (6/8/2016)
Jeff Moden (6/7/2016)
Lynn Pettis (6/7/2016)
Hugo Kornelis (6/7/2016)
GilaMonster (6/7/2016)
What I've advised for years is to notify on lack of success (eg: have a monitoring server check that the backup ran, and if it didn't, send mail)And then have another server monitor the monitoring server, and mail you when it has problems.
And then another, and another , ... when does the monitoring end? :w00t:
When the users call with a problem that you forgot to monitor for. 😉
There will always be one. The best one would be when one of the monitors sends an email saying that the email server is down. 😛
Reminds me of our internet provider that went down. They wanted us to post a message to their site. :crazy:
Yep - exactly the point. Or when there's a power outage and they report restoration estimates on the local TV news.
Many years ago I worked for a company that created a training course for deaf people. And yes, they advertised it on the radio.
In my current workplace, I need to log in to the site to enter a helpdesk ticket to reset my password if it expires. By the way, there's no notification of the password expiring, except you can't log in any more.
June 8, 2016 at 7:49 am
BrainDonor (6/8/2016)
Many years ago I worked for a company that created a training course for deaf people. And yes, they advertised it on the radio.
Kinda like wondering why drive-up ATMs have Braille keypads...
+--------------------------------------------------------------------------------------+
Check out my blog at https://pianorayk.wordpress.com/
June 8, 2016 at 7:59 am
What's your impression on this campaign? https://youtu.be/vXeF6Uot8pk
I feel that the main message is correct, but it's not handled correctly which ends up on the message being lost.
June 8, 2016 at 8:13 am
Ray K (6/8/2016)
BrainDonor (6/8/2016)
Many years ago I worked for a company that created a training course for deaf people. And yes, they advertised it on the radio.Kinda like wondering why drive-up ATMs have Braille keypads...
I'm pretty sure that some drivers need them. :hehe:
June 8, 2016 at 8:22 am
HAPPY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
VS 2012 Update 5 fixed my crash problem.
HAPPY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
:hehe:
June 8, 2016 at 8:37 am
Jeff Moden (6/7/2016)
Lynn Pettis (6/7/2016)
Hugo Kornelis (6/7/2016)
GilaMonster (6/7/2016)
What I've advised for years is to notify on lack of success (eg: have a monitoring server check that the backup ran, and if it didn't, send mail)And then have another server monitor the monitoring server, and mail you when it has problems.
And then another, and another , ... when does the monitoring end? :w00t:
When the users call with a problem that you forgot to monitor for. 😉
Actually, I was talking about how many monitoring systems to use to monitor the monitoring systems? Or put it another way, how many watchers are watching watchers?
June 8, 2016 at 9:33 am
Lynn Pettis (6/8/2016)
Actually, I was talking about how many monitoring systems to use to monitor the monitoring systems? Or put it another way, how many watchers are watching watchers?
Reminds me of a bad Sci-Fi movie.:-D
June 8, 2016 at 10:10 am
Ed Wagner (6/8/2016)
Jeff Moden (6/7/2016)
Lynn Pettis (6/7/2016)
Hugo Kornelis (6/7/2016)
GilaMonster (6/7/2016)
What I've advised for years is to notify on lack of success (eg: have a monitoring server check that the backup ran, and if it didn't, send mail)And then have another server monitor the monitoring server, and mail you when it has problems.
And then another, and another , ... when does the monitoring end? :w00t:
When the users call with a problem that you forgot to monitor for. 😉
There will always be one. The best one would be when one of the monitors sends an email saying that the email server is down. 😛
No joke. A client had an email alert just for that. Email if the email server is down. Then they wondered why they didn't get any email when the email server was down.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 8, 2016 at 10:36 am
SQLRNNR (6/8/2016)
Ed Wagner (6/8/2016)
Jeff Moden (6/7/2016)
Lynn Pettis (6/7/2016)
Hugo Kornelis (6/7/2016)
GilaMonster (6/7/2016)
What I've advised for years is to notify on lack of success (eg: have a monitoring server check that the backup ran, and if it didn't, send mail)And then have another server monitor the monitoring server, and mail you when it has problems.
And then another, and another , ... when does the monitoring end? :w00t:
When the users call with a problem that you forgot to monitor for. 😉
There will always be one. The best one would be when one of the monitors sends an email saying that the email server is down. 😛
No joke. A client had an email alert just for that. Email if the email server is down. Then they wondered why they didn't get any email when the email server was down.
I've also heard of that exact same logic being proposed before. I must have had to most confused look on my face, almost like there was some part of it I missed. When I pointed out the error in their logic, it took them a minute to process it before they saw the light. It was so funny to see their expressions change when they realized the truth.
Naturally, this led me to a number of funny followups later. Because they believe that email is the "true documentation" for everything, does that mean the problem didn't exist because it wasn't in an email? Even better, because there was no email that the email server was down, did it really go down? 😛
June 8, 2016 at 10:40 am
Ed Wagner (6/8/2016)
SQLRNNR (6/8/2016)
Ed Wagner (6/8/2016)
Jeff Moden (6/7/2016)
Lynn Pettis (6/7/2016)
Hugo Kornelis (6/7/2016)
GilaMonster (6/7/2016)
What I've advised for years is to notify on lack of success (eg: have a monitoring server check that the backup ran, and if it didn't, send mail)And then have another server monitor the monitoring server, and mail you when it has problems.
And then another, and another , ... when does the monitoring end? :w00t:
When the users call with a problem that you forgot to monitor for. 😉
There will always be one. The best one would be when one of the monitors sends an email saying that the email server is down. 😛
No joke. A client had an email alert just for that. Email if the email server is down. Then they wondered why they didn't get any email when the email server was down.
I've also heard of that exact same logic being proposed before. I must have had to most confused look on my face, almost like there was some part of it I missed. When I pointed out the error in their logic, it took them a minute to process it before they saw the light. It was so funny to see their expressions change when they realized the truth.
Naturally, this led me to a number of funny followups later. Because they believe that email is the "true documentation" for everything, does that mean the problem didn't exist because it wasn't in an email? Even better, because there was no email that the email server was down, did it really go down? 😛
So where is the backup email server that should take over when the primary email server goes down so the email still goes through?
June 8, 2016 at 11:05 am
Ed Wagner (6/8/2016)
djj (6/8/2016)
Reminds me of our internet provider that went down. They wanted us to post a message to their site. :crazy:Yep - exactly the point. Or when there's a power outage and they report restoration estimates on the local TV news.
We lost power the other night for 4 hours. Fortunately we have a generator, and it kept the Internet connection up.
June 8, 2016 at 11:15 am
Luis Cazares (6/8/2016)
What's your impression on this campaign? https://youtu.be/vXeF6Uot8pkI feel that the main message is correct, but it's not handled correctly which ends up on the message being lost.
It's handled so incorrectly that it doesn't actually express the main message at all. It is utterly useless. Putting up a bunch of nonsensical strawmen and debunking them is nothing but a waste of time and effort.
We want more girls working in software development. I used to see a higher proportion of girls in those jobs when I was young than I do now that I'm old, and we were better off for it. The reason we don't get them hass nothing to do with the nonsensical strawmen this video debunks (even those who cause the real problem would agree that these strawmen are nonsense).
The real reason is that girls are discouraged from pursuing education in engineering or computer science by the general attitude in society that it isn't an appropriate thing for girls - an view that has been instilled in too many girls adopted before they are 10 or 11 years old. It's not (usually) the employers, or high school teachers, or universities that do the damage, it's teachers of younger children, and parents, and the vast horde of ignoramuses who believe that "everybody knows that's not a suitable career for girls" but haven't a clue why they believe that. Of course they believe it because it was inculcated in them when they were very young.
Tom
June 8, 2016 at 11:37 am
Lynn Pettis (6/8/2016)
Ed Wagner (6/8/2016)
SQLRNNR (6/8/2016)
Ed Wagner (6/8/2016)
Jeff Moden (6/7/2016)
Lynn Pettis (6/7/2016)
Hugo Kornelis (6/7/2016)
GilaMonster (6/7/2016)
What I've advised for years is to notify on lack of success (eg: have a monitoring server check that the backup ran, and if it didn't, send mail)And then have another server monitor the monitoring server, and mail you when it has problems.
And then another, and another , ... when does the monitoring end? :w00t:
When the users call with a problem that you forgot to monitor for. 😉
There will always be one. The best one would be when one of the monitors sends an email saying that the email server is down. 😛
No joke. A client had an email alert just for that. Email if the email server is down. Then they wondered why they didn't get any email when the email server was down.
I've also heard of that exact same logic being proposed before. I must have had to most confused look on my face, almost like there was some part of it I missed. When I pointed out the error in their logic, it took them a minute to process it before they saw the light. It was so funny to see their expressions change when they realized the truth.
Naturally, this led me to a number of funny followups later. Because they believe that email is the "true documentation" for everything, does that mean the problem didn't exist because it wasn't in an email? Even better, because there was no email that the email server was down, did it really go down? 😛
So where is the backup email server that should take over when the primary email server goes down so the email still goes through?
Yeah, you would think that there would be one, but there's no budget for one. :w00t:
Viewing 15 posts - 54,496 through 54,510 (of 66,815 total)
You must be logged in to reply to this topic. Login to reply