funny story...kinda. [modified]
-
yesterday, tuesday would be the day, I was just typing out a simple delete query to remove some fake test data i threw in the system. well, i wiped out all the production data on that table in the system because of a typo. aren't i awesome? well, not but 30 minutes later...im searching for a backup and realizing the backup is old my phone rings. it's a job offer for a job i had just interviewed for. what awesome timing. so i go in and tell my boss i lost all the data and dont worry i already found another job. ;) I have all the data off the backup, had to pull a snapshot of the server from Friday. It wasn't a big deal, it just couldn't have been better timing on any of it *im currently an intern so im pretty excited because it's the first job i wanted and interviewed for. :cool:
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
modified on Wednesday, February 06, 2008 2:04:25 PM
-
Yikes! Well you better fix the data you deleted before you leave, that kind of thing can follow you around for years.
When everyone is a hero no one is a hero.
Oh I have it all off the backup, had to pull a snapshot of the server from Friday. It wasn't a big deal, it just couldn't have been better timing on any of it :-D
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
-
That is what is nice about Toad you can turn off explicit commit just in case. Personally, I always operate that way and just commit when ready. (Of course that would be in Oracle) Developers shouldn't have the password to production anyway so it isn't your fault :)
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayA tech here did a maintenance job on the SDE system, and crashed it. When it came up, a layer was missing. ?? It took us an entire day to get the tapes, restore them, rebuild the database to point-in-time.
"Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." "There is no one who loves pain itself, who seeks after it and wants to have it, simply because it is pain..."
-
yesterday, tuesday would be the day, I was just typing out a simple delete query to remove some fake test data i threw in the system. well, i wiped out all the production data on that table in the system because of a typo. aren't i awesome? well, not but 30 minutes later...im searching for a backup and realizing the backup is old my phone rings. it's a job offer for a job i had just interviewed for. what awesome timing. so i go in and tell my boss i lost all the data and dont worry i already found another job. ;) I have all the data off the backup, had to pull a snapshot of the server from Friday. It wasn't a big deal, it just couldn't have been better timing on any of it *im currently an intern so im pretty excited because it's the first job i wanted and interviewed for. :cool:
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
modified on Wednesday, February 06, 2008 2:04:25 PM
I hope you don't ever plan to list that job on your resume. At least not for a decade or two. Try to recover what you can and show them that you may have made a mistake, but you are professional enough to do your best to rectify it. Oh, and learn from this mistake. ALWAYS test your script on a COPY of the database before applying it to production. Better yet, NEVER put test data in a production database. It's easy enough to create a deve version of the web.config or app.config that points your connection strings to the dev database, then if you screw it up, you can make a backup of production and restore it over top of dev. Of course, this is just my 20+ years of experience talking, YMMV.
-
I hope you don't ever plan to list that job on your resume. At least not for a decade or two. Try to recover what you can and show them that you may have made a mistake, but you are professional enough to do your best to rectify it. Oh, and learn from this mistake. ALWAYS test your script on a COPY of the database before applying it to production. Better yet, NEVER put test data in a production database. It's easy enough to create a deve version of the web.config or app.config that points your connection strings to the dev database, then if you screw it up, you can make a backup of production and restore it over top of dev. Of course, this is just my 20+ years of experience talking, YMMV.
Draugnar wrote:
Of course, this is just my 20+ years of experience talking, YMMV.
:|
Draugnar wrote:
web.config or app.config
what are these things? are they in frontpage? please advise.
Draugnar wrote:
COPY of the database
how do i make this? show me the way oh great developer!
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
-
I hope you don't ever plan to list that job on your resume. At least not for a decade or two. Try to recover what you can and show them that you may have made a mistake, but you are professional enough to do your best to rectify it. Oh, and learn from this mistake. ALWAYS test your script on a COPY of the database before applying it to production. Better yet, NEVER put test data in a production database. It's easy enough to create a deve version of the web.config or app.config that points your connection strings to the dev database, then if you screw it up, you can make a backup of production and restore it over top of dev. Of course, this is just my 20+ years of experience talking, YMMV.
I find that developers who made big mistakes early in the career are not the kind that would make the same mistakes later when they have the latitude to do real damage. I wouldn't cover it up nor would I advertise it to the world. But experience does not only come from success.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
I find that developers who made big mistakes early in the career are not the kind that would make the same mistakes later when they have the latitude to do real damage. I wouldn't cover it up nor would I advertise it to the world. But experience does not only come from success.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
Draugnar wrote:
Of course, this is just my 20+ years of experience talking, YMMV.
:|
Draugnar wrote:
web.config or app.config
what are these things? are they in frontpage? please advise.
Draugnar wrote:
COPY of the database
how do i make this? show me the way oh great developer!
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
jgasm wrote:
Draugnar wrote: web.config or app.config what are these things? are they in frontpage? please advise. Draugnar wrote: COPY of the database how do i make this? show me the way oh great developer!
I'm sorry, but these are programming questions and don't belong in this forum. Please read the rules of the forum :laugh: Actually, you make a good point. If I came across as condescending to the newbie, my apologies. I'm sure there are plenty here with even more experience than myself. Draugnar
-
jgasm wrote:
Draugnar wrote: web.config or app.config what are these things? are they in frontpage? please advise. Draugnar wrote: COPY of the database how do i make this? show me the way oh great developer!
I'm sorry, but these are programming questions and don't belong in this forum. Please read the rules of the forum :laugh: Actually, you make a good point. If I came across as condescending to the newbie, my apologies. I'm sure there are plenty here with even more experience than myself. Draugnar
Draugnar wrote:
I'm sorry, but these are programming questions and don't belong in this forum. Please read the rules of the forum
nice. i thought someone might catch that
Draugnar wrote:
If I came across as condescending to the newbie, my apologies. I'm sure there are plenty here with even more experience than myself.
No not really, my only defense for wiping out production data because im a nubcake is sarcasm :( it's sad, but it's all i have to hold on to. now whenever i contact IT they ask me which backup I need pulled :(
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
-
I find that developers who made big mistakes early in the career are not the kind that would make the same mistakes later when they have the latitude to do real damage. I wouldn't cover it up nor would I advertise it to the world. But experience does not only come from success.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayEnnis Ray Lynch, Jr. wrote:
the latitude to do real damage
no one is dumb enough to entrust me with that kind of power ;P
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
-
That is what is nice about Toad you can turn off explicit commit just in case. Personally, I always operate that way and just commit when ready. (Of course that would be in Oracle) Developers shouldn't have the password to production anyway so it isn't your fault :)
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayEnnis Ray Lynch, Jr. wrote:
Developers shouldn't have the password to production anyway
Just out of curiosity, why do you say this? You're not the first person I've known to say this, but the other person couldn't give me a good reason why not.
The hamsters ate my signature.
-
Ennis Ray Lynch, Jr. wrote:
Developers shouldn't have the password to production anyway
Just out of curiosity, why do you say this? You're not the first person I've known to say this, but the other person couldn't give me a good reason why not.
The hamsters ate my signature.
Developers do not produce production code. They develop code which testers test on Test which gets a trial implementation on Staging and then moved live into production. 1 of the reasons is to prevent the scenario that just occurred. The deletion of a DB by a dev on accident. The other is security. Developers have complete knowledge of the system. If they have the password they can also violate policies. I replaced a developer once who was illegally modifying the database to increase commissions of floor staff. This would not have been possible if he did not have the password.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
Developers do not produce production code. They develop code which testers test on Test which gets a trial implementation on Staging and then moved live into production. 1 of the reasons is to prevent the scenario that just occurred. The deletion of a DB by a dev on accident. The other is security. Developers have complete knowledge of the system. If they have the password they can also violate policies. I replaced a developer once who was illegally modifying the database to increase commissions of floor staff. This would not have been possible if he did not have the password.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayEnnis Ray Lynch, Jr. wrote:
I replaced a developer once who was illegally modifying the database to increase commissions of floor staff.
was he rounding down fractions of a cent from accrual of interest and transfer the leftovers into their own commissions over a period of years, leaving them with a cash windfall undetected by the corporation?
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
-
Ennis Ray Lynch, Jr. wrote:
I replaced a developer once who was illegally modifying the database to increase commissions of floor staff.
was he rounding down fractions of a cent from accrual of interest and transfer the leftovers into their own commissions over a period of years, leaving them with a cash windfall undetected by the corporation?
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
Nope, updating full dollar amounts. There were no audits and logging was not enabled. It was the pinnacle of how a financial system should not have been run. It lasted about 6 months before being caught. I think the total stolen was a few hundred k. It was wiped under to prevent bad press.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
Ennis Ray Lynch, Jr. wrote:
I replaced a developer once who was illegally modifying the database to increase commissions of floor staff.
was he rounding down fractions of a cent from accrual of interest and transfer the leftovers into their own commissions over a period of years, leaving them with a cash windfall undetected by the corporation?
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
Salami slicing! Like Superman III (and Office Space).
-
Developers do not produce production code. They develop code which testers test on Test which gets a trial implementation on Staging and then moved live into production. 1 of the reasons is to prevent the scenario that just occurred. The deletion of a DB by a dev on accident. The other is security. Developers have complete knowledge of the system. If they have the password they can also violate policies. I replaced a developer once who was illegally modifying the database to increase commissions of floor staff. This would not have been possible if he did not have the password.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayThe #1 reason why nuclear reactors have isolated systems from the rest of the facility. We had to develop on one machine, then take the tape reels off, move them to the live system, and load. After review.
"Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." "There is no one who loves pain itself, who seeks after it and wants to have it, simply because it is pain..."
-
yesterday, tuesday would be the day, I was just typing out a simple delete query to remove some fake test data i threw in the system. well, i wiped out all the production data on that table in the system because of a typo. aren't i awesome? well, not but 30 minutes later...im searching for a backup and realizing the backup is old my phone rings. it's a job offer for a job i had just interviewed for. what awesome timing. so i go in and tell my boss i lost all the data and dont worry i already found another job. ;) I have all the data off the backup, had to pull a snapshot of the server from Friday. It wasn't a big deal, it just couldn't have been better timing on any of it *im currently an intern so im pretty excited because it's the first job i wanted and interviewed for. :cool:
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
modified on Wednesday, February 06, 2008 2:04:25 PM
I'm an intern too (with a government-related organization nonetheless) and I'm proud to say I've never caused any irreperable harm :-D In fact, I've never had to walk down the hall to the network guys to have them pull data. I've screwed up many personal projects, so I'm a little gun-shy when it comes to things like mass data deletion. And trust me, I certainly could accidentally cause hell around here.
-
Developers do not produce production code. They develop code which testers test on Test which gets a trial implementation on Staging and then moved live into production. 1 of the reasons is to prevent the scenario that just occurred. The deletion of a DB by a dev on accident. The other is security. Developers have complete knowledge of the system. If they have the password they can also violate policies. I replaced a developer once who was illegally modifying the database to increase commissions of floor staff. This would not have been possible if he did not have the password.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayIn your world that may be true. In my world there are only 2 MS developers and no one else who knows what to do, you need access to Dev and Prod.
It's good to be alive
-
yesterday, tuesday would be the day, I was just typing out a simple delete query to remove some fake test data i threw in the system. well, i wiped out all the production data on that table in the system because of a typo. aren't i awesome? well, not but 30 minutes later...im searching for a backup and realizing the backup is old my phone rings. it's a job offer for a job i had just interviewed for. what awesome timing. so i go in and tell my boss i lost all the data and dont worry i already found another job. ;) I have all the data off the backup, had to pull a snapshot of the server from Friday. It wasn't a big deal, it just couldn't have been better timing on any of it *im currently an intern so im pretty excited because it's the first job i wanted and interviewed for. :cool:
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow
modified on Wednesday, February 06, 2008 2:04:25 PM
Congratulations on the new job!
jgasm wrote:
so i go in and tell my boss i lost all the data and dont worry i already found another job.
That's way cool.
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
-
Congratulations on the new job!
jgasm wrote:
so i go in and tell my boss i lost all the data and dont worry i already found another job.
That's way cool.
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
Thanks ! Thank god for backups.
----------------------------------------------------------- Completion Deadline: two days before the day after tomorrow