April 18, 2012 at 12:13 pm
How about a slight change of subject. Still "worst questions" but of the humorous sort.
We've all heard about the admin assistant who switched from typewriters to computers and started whiting out the monitor to correct misspelled words. Or the priest who pulled the round film out of a 3.5 floppy to stick it in the disk drive where it got stuck.
What was (to you) the funniest, most gut-busting question you ever had to answer in your capacity as an IT / SQL Server person?
April 18, 2012 at 12:27 pm
hbtkp (4/13/2012)
hbtkp (4/13/2012)
he just told me i cant help u with code,so i need help from you,
hbtkp (4/13/2012)
i m fresher in sql
hbtkp (4/15/2012)
i know basic,
If nothing else, it's been entertaining to watch.
hbtkp (4/17/2012)
i m closing this thread
I wonder if he/she had to ask someone how to do it...
April 18, 2012 at 12:32 pm
ACinKC (4/18/2012)
hbtkp (4/13/2012)
i think i will lost my job , i am on dead linequote]hbtkp (4/13/2012)
he just told me i cant help u with code,so i need help from you,hbtkp (4/13/2012)
i m fresher in sqlhbtkp (4/15/2012)
i know basic,If nothing else, it's been entertaining to watch.
hbtkp (4/17/2012)
i m closing this threadI wonder if he/she had to ask someone how to do it...
Nah - just moving on to other threads trying to get the answers there
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
April 18, 2012 at 1:14 pm
Brandie Tarvin (4/18/2012)
How about a slight change of subject. Still "worst questions" but of the humorous sort.We've all heard about the admin assistant who switched from typewriters to computers and started whiting out the monitor to correct misspelled words. Or the priest who pulled the round film out of a 3.5 floppy to stick it in the disk drive where it got stuck.
What was (to you) the funniest, most gut-busting question you ever had to answer in your capacity as an IT / SQL Server person?
The closest I ever came to the 'put it back in the box' type of troubleshoot was when I used to do over-the-phone troubleshooting. Lady calls up, gets one of the other guys on the floor, and is bamboozled. He ships it over to me for top tier support since we could spend more time on issues without getting burned for it (phone time was god).
Turns out her computer seems to glitch out and reboot whenever she leaves it alone for a bit and works on something else. She's gotten to saving everything every two minutes but it's starting to get a bit rediculuous. I walk her through some standard Troubleshooting tests for Win 98 (current at the time) and figure out it's most likely hardware. Probably a short in the power supply or some other glitch.
Well we get her box swapped out and the only thing that's not new is the old drive they swapped in. Problem persists. Okay, some random setting, maybe a glitch to power-save settings in the registry, horrible driver... who the hell knows. Well, we're not going to troubleshoot this to death.
Well, since Os/Drive must be the issue... we swap all her files over to a fresh drive with a fresh OS ghost and installs of the necessary software.
Problem Persists. WTF?
Eventually I get a local tech to sit with her waiting for the issue. They're having a nice chat and he notices something... she kicks her foot when she's thinking and not doing any work on the computer...
Her power-pack, and thus wires, was RIGHT where her foot was under the desk. Swapped the power pack so that she didn't have any 'loose' plugs (you know how sometimes the socket just won't hold a plug well?) and problem resolved.
NARF!
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
April 18, 2012 at 1:28 pm
Brandie Tarvin (4/18/2012)
Or the priest who pulled the round film out of a 3.5 floppy to stick it in the disk drive where it got stuck.
I actually had this happen to me back in '85...had a customer who cut open the Tyvek to pull out the disk for an upgrade to an application we developed. Had to drive four hours one-way to do something that should have been able to be done over the phone. This was also the same customer who stored the tape for the system backup lying against a telephone...the kind with the magnetic ringer...
April 18, 2012 at 1:32 pm
Brandie Tarvin (4/18/2012)
How about a slight change of subject. Still "worst questions" but of the humorous sort.We've all heard about the admin assistant who switched from typewriters to computers and started whiting out the monitor to correct misspelled words. Or the priest who pulled the round film out of a 3.5 floppy to stick it in the disk drive where it got stuck.
What was (to you) the funniest, most gut-busting question you ever had to answer in your capacity as an IT / SQL Server person?
My favorite story was when an enduser called with problems about getting shocked from the computer. The person did not have a grounded outlet in the house so decided to remove the 3-prong plug, strip the wires and plug the exposed copper wires direct into a 2-prong outlet.
My next favorite is from a truck driver that was having boot problems. He opened the computer, removed the power supply and then took the power supply apart. To test the power supply, he held the capacitor in his hands and plugged it into the wall to confirm that it was still working.
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
April 18, 2012 at 1:34 pm
Brandie Tarvin (4/18/2012)
How about a slight change of subject. Still "worst questions" but of the humorous sort.We've all heard about the admin assistant who switched from typewriters to computers and started whiting out the monitor to correct misspelled words. Or the priest who pulled the round film out of a 3.5 floppy to stick it in the disk drive where it got stuck.
What was (to you) the funniest, most gut-busting question you ever had to answer in your capacity as an IT / SQL Server person?
Back around 89 or 90, my girlfriend at the time worked in the Penn State computer lab where students could come in and use the computers. One kid using a Mac Classic came up to her to ask for help. He was installing a program and the process told him to "Insert Disk 3" and he couldn't get it in.
She went over to the computer to see what was wrong (I tagged along 'cause this seemed weird) and found he'd put in the first disk, somehow jammed in the second disk without taking the first one out and was now trying to wedge the third one in under the first two, but couldn't get it in there.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
April 18, 2012 at 1:41 pm
Evil Kraig F (4/18/2012)
Brandie Tarvin (4/18/2012)
How about a slight change of subject. Still "worst questions" but of the humorous sort.We've all heard about the admin assistant who switched from typewriters to computers and started whiting out the monitor to correct misspelled words. Or the priest who pulled the round film out of a 3.5 floppy to stick it in the disk drive where it got stuck.
What was (to you) the funniest, most gut-busting question you ever had to answer in your capacity as an IT / SQL Server person?
The closest I ever came to the 'put it back in the box' type of troubleshoot was when I used to do over-the-phone troubleshooting. Lady calls up, gets one of the other guys on the floor, and is bamboozled. He ships it over to me for top tier support since we could spend more time on issues without getting burned for it (phone time was god).
Turns out her computer seems to glitch out and reboot whenever she leaves it alone for a bit and works on something else. She's gotten to saving everything every two minutes but it's starting to get a bit rediculuous. I walk her through some standard Troubleshooting tests for Win 98 (current at the time) and figure out it's most likely hardware. Probably a short in the power supply or some other glitch.
Well we get her box swapped out and the only thing that's not new is the old drive they swapped in. Problem persists. Okay, some random setting, maybe a glitch to power-save settings in the registry, horrible driver... who the hell knows. Well, we're not going to troubleshoot this to death.
Well, since Os/Drive must be the issue... we swap all her files over to a fresh drive with a fresh OS ghost and installs of the necessary software.
Problem Persists. WTF?
Eventually I get a local tech to sit with her waiting for the issue. They're having a nice chat and he notices something... she kicks her foot when she's thinking and not doing any work on the computer...
Her power-pack, and thus wires, was RIGHT where her foot was under the desk. Swapped the power pack so that she didn't have any 'loose' plugs (you know how sometimes the socket just won't hold a plug well?) and problem resolved.
NARF!
I wasn't present for this one but heard about it from several who were.
Years ago at Data General in Millford, MA; they were experiencing a problem with one of their minicomputers that was rebooting for no apparent reason at 5:00 PM every night. The FE's had run numerous diagnostics, they brought in highly experienced troubleshooters to work on it, and nothing. One night they had the FE's, senior management and others all hanging around waiting for the system to reboot.
While watching the system, they heard the door to the computer room open and shut, and then the system shutdown and rebooted. Looking up they saw the problem. When the janitor came into the computer room, the plug to the system was in his way. He unplugged it, stepped around and plugged it back in.
Two things happened because of that. Additional subfloor power was installed and the janitor lost his job.
April 18, 2012 at 1:58 pm
Just complaining for a second
Scope for variables in SSIS are utter crap, it'd be better if scope didn't even exist here. Yes, I hear it has been fixed in 2012, but seeing as I won't get to use that until 2016 or 2020, that's cold comfort.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
April 18, 2012 at 1:59 pm
SQLRNNR (4/18/2012)
Brandie Tarvin (4/18/2012)
How about a slight change of subject. Still "worst questions" but of the humorous sort.We've all heard about the admin assistant who switched from typewriters to computers and started whiting out the monitor to correct misspelled words. Or the priest who pulled the round film out of a 3.5 floppy to stick it in the disk drive where it got stuck.
What was (to you) the funniest, most gut-busting question you ever had to answer in your capacity as an IT / SQL Server person?
My favorite story was when an enduser called with problems about getting shocked from the computer. The person did not have a grounded outlet in the house so decided to remove the 3-prong plug, strip the wires and plug the exposed copper wires direct into a 2-prong outlet.
My next favorite is from a truck driver that was having boot problems. He opened the computer, removed the power supply and then took the power supply apart. To test the power supply, he held the capacitor in his hands and plugged it into the wall to confirm that it was still working.
Wow. I...wow.
You know that the fan belt in your car says to turn the engine off before installing? Think maybe this guy is the reason.
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
April 18, 2012 at 2:02 pm
Stefan Krzywicki (4/18/2012)
Just complaining for a secondScope for variables in SSIS are utter crap, it'd be better if scope didn't even exist here. Yes, I hear it has been fixed in 2012, but seeing as I won't get to use that until 2016 or 2020, that's cold comfort.
+1
I accidentally created two identically named variables, one at package level and one within a container. Took me FOREVER to figure it out. My mistake, but still, wasn't intentionally changing the scope when I created them, just accidentally clicked on the wrong damn thing before I created the variable.
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
April 18, 2012 at 2:08 pm
;-);-):sick:
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
April 18, 2012 at 2:10 pm
jcrawf02 (4/18/2012)
Stefan Krzywicki (4/18/2012)
Just complaining for a secondScope for variables in SSIS are utter crap, it'd be better if scope didn't even exist here. Yes, I hear it has been fixed in 2012, but seeing as I won't get to use that until 2016 or 2020, that's cold comfort.
+1
I accidentally created two identically named variables, one at package level and one within a container. Took me FOREVER to figure it out. My mistake, but still, wasn't intentionally changing the scope when I created them, just accidentally clicked on the wrong damn thing before I created the variable.
Yeah, I'm at the point where I make sure every variable is created at the package level. I just had to change 10 variables, all "evaluate as expression" that build on one another because the FlatFile Connection is at package level and can't read anything at a lower scope, though all the file manipulation is done in a Foreach Loop container.
Now I have to go through the entire package and look at the Parameter Mapping 'cause SSIS will throw an error unless I do, even though I'm not changing a damn thing on those screens.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
April 18, 2012 at 2:12 pm
Stefan Krzywicki (4/18/2012)
jcrawf02 (4/18/2012)
Stefan Krzywicki (4/18/2012)
Just complaining for a secondScope for variables in SSIS are utter crap, it'd be better if scope didn't even exist here. Yes, I hear it has been fixed in 2012, but seeing as I won't get to use that until 2016 or 2020, that's cold comfort.
+1
I accidentally created two identically named variables, one at package level and one within a container. Took me FOREVER to figure it out. My mistake, but still, wasn't intentionally changing the scope when I created them, just accidentally clicked on the wrong damn thing before I created the variable.
Yeah, I'm at the point where I make sure every variable is created at the package level. I just had to change 10 variables, all "evaluate as expression" that build on one another because the FlatFile Connection is at package level and can't read anything at a lower scope, though all the file manipulation is done in a Foreach Loop container.
Now I have to go through the entire package and look at the Parameter Mapping 'cause SSIS will throw an error unless I do, even though I'm not changing a damn thing on those screens.
That is one of the most frustrating things with SSIS - opening everything and confirming the settings after a minor change.
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
April 18, 2012 at 2:15 pm
SQLRNNR (4/18/2012)
Stefan Krzywicki (4/18/2012)
jcrawf02 (4/18/2012)
Stefan Krzywicki (4/18/2012)
Just complaining for a secondScope for variables in SSIS are utter crap, it'd be better if scope didn't even exist here. Yes, I hear it has been fixed in 2012, but seeing as I won't get to use that until 2016 or 2020, that's cold comfort.
+1
I accidentally created two identically named variables, one at package level and one within a container. Took me FOREVER to figure it out. My mistake, but still, wasn't intentionally changing the scope when I created them, just accidentally clicked on the wrong damn thing before I created the variable.
Yeah, I'm at the point where I make sure every variable is created at the package level. I just had to change 10 variables, all "evaluate as expression" that build on one another because the FlatFile Connection is at package level and can't read anything at a lower scope, though all the file manipulation is done in a Foreach Loop container.
Now I have to go through the entire package and look at the Parameter Mapping 'cause SSIS will throw an error unless I do, even though I'm not changing a damn thing on those screens.
That is one of the most frustrating things with SSIS - opening everything and confirming the settings after a minor change.
Yeah, another fun one I found is in creating XML files. If I change the length of the string specifying the output path, the process fails. There's no fix for it short of changing it back or to somthing the same length or re-creating the item at the control flow level and deleting the old one.
C:\Out\Files\Filename.xml changed to
C:\Out\FilesA\Filname.xml requires a complete re-creation of the step.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
Viewing 15 posts - 35,536 through 35,550 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply