Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Trusting Systems


Trusting Systems

Author
Message
Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36143 Visits: 18747
Comments posted to this topic are about the item Trusting Systems

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Gary Varga
Gary Varga
SSCrazy Eights
SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)

Group: General Forum Members
Points: 8356 Visits: 6160
What I constantly find fascinating is the number of management teams who are told that they need to invest more to get the levels of nonfunctional requirements the demand (be it redundancy, scalability, maintainability, flexibility etc) who go on to deny the investment (usually time) then demand that the nonfunctional requirement must be met anyway.

It seems that every place where this then gets raised as a challenge then highlighted back that instructions were made to cut corners and sacrifice the nonfunctional requirements the following horrible expression gets rolled out: "We are where we are."

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
MKEDataGuy
MKEDataGuy
Old Hand
Old Hand (320 reputation)Old Hand (320 reputation)Old Hand (320 reputation)Old Hand (320 reputation)Old Hand (320 reputation)Old Hand (320 reputation)Old Hand (320 reputation)Old Hand (320 reputation)

Group: General Forum Members
Points: 320 Visits: 108
This reminds me of an article I came across earlier in my career... The gist of the piece was that every employee should know how to do their jobs without the use of an automated system. So, that when (not if, but when) the system goes down, the business can continue to function. Granted it won't be at the same productivity level, but business continues none the less. I know there are jobs now, where that's just not possible. However, I think, that too many workers don't know how to do their jobs without the aid of a computer. And, I think, there's real value in knowing how to actually do your job without a computer, as oppose to relying on one. If you can do it without a computer, that signals to me that you truly understand the process; instead of just knowing which buttons to push.

Thanks,
MKE Data Guy
jay-h
jay-h
SSC Eights!
SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)

Group: General Forum Members
Points: 925 Visits: 2222
Knowledge Draftsman (5/23/2013)
This reminds me of an article I came across earlier in my career... The gist of the piece was that every employee should know how to do their jobs without the use of an automated system. ...


Unfortunately many businesses like stores that SHOULD be able to function in a power outage, for example, cannot because they have become completely dependent on automation.

It's getting worse. With cloud dependency, it's not just enough to get some temporary power, without a network connection the business has no local redundancy to operate (Sandy showed how vulnerable these connections are). Obviously stores etc SHOULD be able to function for a while without communications, but they're no longer designed that way and even with willing employees, nothing can be accomplished. Plenty of other business operations (remote sales offices for example) have become completelyl cloud dependent in the effort to remove computation from the office to other centralized locations.

...

-- FORTRAN manual for Xerox Computers --
Jim P.
Jim P.
Say Hey Kid
Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)Say Hey Kid (681 reputation)

Group: General Forum Members
Points: 681 Visits: 2215
jay-h (5/23/2013)

Unfortunately many businesses like stores that SHOULD be able to function in a power outage, for example, cannot because they have become completely dependent on automation.


Barcode scanners basically started killing this in the early 90's and it has only gotten worse.



----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.
Megistal
Megistal
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1608 Visits: 2555
I know most will disagree with what I will say but that's what I found through out my experiences.

If there's no money tag associate with something (downtime, results, etc) then it's none existent for management.
Therefore each time we had plan something, we translated it into dollar cost or man hour (which is then translated into dollar cost by management). Still an approximate but it got the attention it deserved only because money is involved, they have something "tangible" to look at.

no money -> no worry (don't care)
some money -> some worry (will care to some extent)
Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36143 Visits: 18747
Knowledge Draftsman (5/23/2013)
This reminds me of an article I came across earlier in my career... The gist of the piece was that every employee should know how to do their jobs without the use of an automated system. So, that when (not if, but when) the system goes down, the business can continue to function. Granted it won't be at the same productivity level, but business continues none the less. I know there are jobs now, where that's just not possible. However, I think, that too many workers don't know how to do their jobs without the aid of a computer. And, I think, there's real value in knowing how to actually do your job without a computer, as oppose to relying on one. If you can do it without a computer, that signals to me that you truly understand the process; instead of just knowing which buttons to push.


I think this was fine advice 20, or even 10, years ago. Now we have so many people in the workplace that have never done the job without a computer. I'm not sure of the solution here, but at some point I expect that lots of what we do just won't work without a computer and we may need to delay/shut down parts of our business until the computers are fixed.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
jay-h
jay-h
SSC Eights!
SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)SSC Eights! (925 reputation)

Group: General Forum Members
Points: 925 Visits: 2222
Steve Jones - SSC Editor (5/23/2013)
Knowledge Draftsman (5/23/2013)
This reminds me of an article I came across earlier in my career... The gist of the piece was that every employee should know how to do their jobs without the use of an automated system. So, that when (not if, but when) the system goes down, the business can continue to function. Granted it won't be at the same productivity level, but business continues none the less. I know there are jobs now, where that's just not possible. However, I think, that too many workers don't know how to do their jobs without the aid of a computer. And, I think, there's real value in knowing how to actually do your job without a computer, as oppose to relying on one. If you can do it without a computer, that signals to me that you truly understand the process; instead of just knowing which buttons to push.


I think this was fine advice 20, or even 10, years ago. Now we have so many people in the workplace that have never done the job without a computer. I'm not sure of the solution here, but at some point I expect that lots of what we do just won't work without a computer and we may need to delay/shut down parts of our business until the computers are fixed.


At a minimum, at least, the operation should be workable for a length of time on emergency power, off the grid. Depending on full time cloud connection is a major weakness.

...

-- FORTRAN manual for Xerox Computers --
lptech
lptech
Old Hand
Old Hand (345 reputation)Old Hand (345 reputation)Old Hand (345 reputation)Old Hand (345 reputation)Old Hand (345 reputation)Old Hand (345 reputation)Old Hand (345 reputation)Old Hand (345 reputation)

Group: General Forum Members
Points: 345 Visits: 3275
American Airlines is not likely to suffer very much from said outage. They may be the best or only choice for certain destinations. People are not going to give up their frequent flyer miles either. And airlines don't really seem to care about customer satisfaction when it comes to fees for just about everything.

But this is still a good reminder of why we need to address problems and not hope that they just go away, because they usually don't. Just this week, we are looking into a SQL Agent job that didn't work, but successfully completed. This caused some billing for that time period not to get done, and was only discovered on the financial side months later. It is now taking a lot of work to recreate everything, as a lot of files involved are long past their retention period.

Of course maintaining this attitude also requires management that is willing to deal with things that are not already official objectives. In a past job, this was not the case, and any DBA who discovered a problem was blamed for not having fixed it. Needless to say, everything was buried well below the management level, resulting in many hours of work to fix them laterAngry
OCTom
OCTom
SSCrazy
SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)

Group: General Forum Members
Points: 2813 Visits: 4152
What we're really talking about here is disaster recovery. Disaster doesn't have to mean an earthquake, tornado, or something else on a massive scale. It could mean a temporary power outage on a local scale. We have to understand which systems are critical to the operations of the enterprise and which ones are not. I would guess that the ability for an airline to know their flight schedules is critical.

All employees like to think their work is high priority. The reality is that very few systems and employees are mission critical. If you have identified the mission critical systems and operations that must be working within a reasonable time period, you can address those first.

Catching systems that fail in some way that may not be visible or obvious is the job of those who created the system. Any program or script that runs needs to have error recovery in it. You need to have checks and balances within the systems and identify problems early. There may also be a need for the department who uses the systems and data to have checks and balances where they can discover problems early.

I don't know if American Airlines will have other problems, such as loss of customers, due to the downtime. If systems fail enough, though, trust will fade and the airline could be hurt down the road.

Tom
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search