• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ugh...database at work is fubar'd...

A

Accipiter22

Banned
I do a lot of database integrity/comparative testing where I work...they have 2 versions of it basically. Someone f'd up one of them last friday apparently so there'd be nothing for me or anyone on my team to do so now we all get 4 days off until it's fixed on wednesday. I get paid hourly. so this blows
 
I thought you meant you get to work all weekend and then some... not sure which sucks more...
 
Originally posted by: torpid
Originally posted by: Homerboy
your database is down for FOUR DAYS resulting in little/no work being done?? Thats some crappy IT.
Click to expand...
Click to expand...

Actually let me add to that.... where are you located and who are the decision makers? I think I have some consulting to do there.

If our database went down for even a day, resulting in work stoppage, #1 I'd be lynched by the hourly employees. #2 I'd be fired for not doing my job.
 
Originally posted by: Homerboy
Originally posted by: torpid
Originally posted by: Homerboy
your database is down for FOUR DAYS resulting in little/no work being done?? Thats some crappy IT.
Click to expand...
Click to expand...

Actually let me add to that.... where are you located and who are the decision makers? I think I have some consulting to do there.

If our database went down for even a day, resulting in work stoppage, #1 I'd be lynched by the hourly employees. #2 I'd be fired for not doing my job.
Click to expand...

First, it matters if the DB is even an important thing. Obviously this thing isnt mission critical.

Also, we don't know what the db is for. He said his job is testing, etc. Maybe he can't TEST, but the other users of the db can still do their job?

Too little information to make a judgement, especially since 2 weekend days are counted in the 4 days.

 
Ummm he and his "entire team" (I'd assume more than 2 people as he chose "enitre") can't work... I would judge "important" off that.
 
Originally posted by: Homerboy
Ummm he and his "entire team" (I'd assume more than 2 people as he chose "enitre") can't work... I would judge "important" off that.
Click to expand...

So what, a handful of hourly employees have nothing to do (and don't get paid) for 2 days?

The fact that there is no rush on this problem makes me judge "not important".
 
Originally posted by: KMDupont64
Originally posted by: Homerboy
Ummm he and his "entire team" (I'd assume more than 2 people as he chose "enitre") can't work... I would judge "important" off that.
Click to expand...

So what, a handful of hourly employees have nothing to do (and don't get paid) for 2 days?

The fact that there is no rush on this problem makes me judge "not important".
Click to expand...

There doesn't need to be a rush. There just needs to be competent IT staff. It should be a matter of hours at most, a couple button clicks and then a lot of tape whirring, then possibly some brief testing and reloading. Several days? Ridiculous.
 
Originally posted by: KMDupont64
Originally posted by: Homerboy
Ummm he and his "entire team" (I'd assume more than 2 people as he chose "enitre") can't work... I would judge "important" off that.
Click to expand...

So what, a handful of hourly employees have nothing to do (and don't get paid) for 2 days?

The fact that there is no rush on this problem makes me judge "not important".
Click to expand...

I'm not going to sit and argue over this (well apparently I am)
ANYYTHING that results in an "entire team" being out of work for 2+ days seems to me that the IT department slipped up.

Hourly employees are often more important than many salaried, so I wouldn't be so quick to cast them aside.
 
Originally posted by: Homerboy
Originally posted by: KMDupont64
Originally posted by: Homerboy
Ummm he and his "entire team" (I'd assume more than 2 people as he chose "enitre") can't work... I would judge "important" off that.
Click to expand...

So what, a handful of hourly employees have nothing to do (and don't get paid) for 2 days?

The fact that there is no rush on this problem makes me judge "not important".
Click to expand...

I'm not going to sit and argue over this (well apparently I am)
ANYYTHING that results in an "entire team" being out of work for 2+ days seems to me that the IT department slipped up.

Hourly employees are often more important than many salaried, so I wouldn't be so quick to cast them aside.
Click to expand...

There are many factors at play that we know nothing about. What his job is, what the app is, what the db is, who admisters the db, etc.

The only facts we know are that the DB is not important enough for people to come in and work the weekend to get it up, he is an hourly employee which they have no use for if this db is down.

Obviously, wth proper planning a db integrity/crash problem can be fixed in no time. All I am saying is the facts that we know about lead me to believe that this system/db is NOT IMPORTANT.

It may turn out that the dbas or infrastructure are a bunch of idiots with A+ certs but for now, we can't go on that.

Not to mention who f-ed up the DB to begin with?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top