[AusNOG] Vlan Add - Was Re: Work experience in networking/telecoms/DCs? Getting my foot in the door?
Joseph Goldman
joe at apcs.com.au
Wed Dec 24 13:39:48 EST 2014
On a small table of about 200 records on an old system that I was asked
to assist with, I did the select * first, then did an UPDATE forgetting
the where clause and updated all rows for a single field - since it was
the older system and one im not in charge of, no one could point me to
backups of any sort - so luckily I had the console output from my
SELECT, copypasta'd out to a text file and meticulously put back to the
right state (not quite row by row, but groups of rows).
Now days I always write DELETE and UPDATE statements WHERE clause first
so even if i do accidentally hit go it will error out
e.g.
DELETE FROM WHERE ID=540;
OR
UPDATE tbl SET WHERE ID=430;
Then go back add the tbl for the DELETE and the fields for the UPDATE.
On 24/12/14 13:27, PRK wrote:
>
> Is there anyone here who either:
>
> a) Hasn't done the vlan xxx instead of vlan add xxx?
>
> or
>
> b) Hasn't directly seen the vlan xxx instead of vlan add xxx done?
>
> Or, if you're more of a systems person, haven't locked yourself out of
> a server due to a firewall change, or directly seen someone else do so?
>
> Or, if you're a DBA, done an update to a database table and missed the
> where clause, overwriting every single record?
>
> I'd consider these fairly common errors that almost everyone makes,
> once, and a fantastic way to evaluate someone's response under
> pressure. They're also fantastic teachable moments (once resolved) as
> to why certain company processes and procedures exist.
>
> I'd probably be concerned if the same person made the same mistake
> more than once, though.
>
> prk.
>
> On 2014-12-23 20:48, Andy S. wrote:
>
>> I just remember one of my mate told a story about one particular CCIE
>> doing "switchport trunk allowed vlan xxx" instead of "switchport
>> trunk allowed vlan add xxx" and caused an outage. Companies losing
>> money (according to him. It's a stock trading company). Though it's
>> weird they needed more time to address where the issue was.
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20141224/258549b7/attachment.html>
More information about the AusNOG
mailing list