A trigger on a busy table was using a Rule Based Optimizer
We had done a 'rough' system test for upgrading from 9i to 10g, but the system did not have a realistic production load put on it
The DBA group placed the upgrade into production and suddenly the system drags to a crawl
It took us a very short amount of time to figure out the problem, but a few hours to deal with the existing change control process and satisfying a DBA manager, who failed to let us know that there was a major change with the database release, that dropping the hint entirely (he had been on the team that introduced it years earlier) would be the best way to go since the new Cost Based Optimizer would recognize the query and make adjustments for it.
A trigger on a busy table was using a Rule Based Optimizer
I understand you come from a different angle on this whole 'merica thing.
For a large portion of the population, for the years from say 1950 until the late 1980's it was totally normal to get a job out of high school, to join a union associate with that job and to work that job until retirement, with a decent pension. This was not unusual for white collar (professional, non-union) positions either.
Just how common this was started to trend downward through the 1990's, both in the union trades (which were decimated as legacy companies failed to keep up with quality and production) and in white collar positions as eager workers from overseas (familiar?) hit the job market and demonstrated their capabilities and lack of expectation of a life-long position with a pension.
Some upper executives made the mistake of believing that all over-seas applicants where as capable or enthusiastic as the first (and second, third) wave of fresh minds that hit the job market, when in fact they were the upper percent of a percent of their nation's respective bell curves, and started making plans to pitch their local workers under the bus in hopes of bringing on endless droves of freakin braniacs who would have no expectation of wages or benefits that native workers would expect
From my stand-point (my father had the same employer for 40+ years, I have had one employer that I was at for more than a decade, with most lasting less than five years) there are trade-offs between seeking long term employees vs 'contract' work. Long-term employees can benefit a company by providing deep knowledge of the organization and may benefit projects by understanding how thet fit in to the ethos of the culture. They can also be horrible lard-asses who want to ride on the coat-tails of the few employees who want to trailblaze and develop new markets.
Similarly, contract labor, outsourcing companies, etc can provide incredible new opportunities to existing companies and drive them into new markets. They can also become a persistent crutch that cost tons of money and take all of their knowledge with them when they leave, letting the companies wither and die like hollowed husks who have no capability to stand on their own.
In truth, black and white gets us no-where and in order to be successful companies will need to leverage whip-smart contract labor, while building capable internal teams to support their efforts after they have been sent off to their next world-building exercise. Maybe the 'stability' from 1950 to 1980 was the real 'aberration' and the constant changes driven by an influx of new workers is the real American norm
GP said, " Name one country, where the people have moved UP in life, that runs under socialism"
My post accomplished that, simply raising the bar in order to try and prove some other point that the answer was not intended for is just an exercise in public masturbation
Yeah, it is called 'Enhancing Shareholder Value' these days
The current variation on the theme involves identifying employees that are owed pensions, converting said pensions (long term debt held by the Company) into 401k's, owned by the employee (at a rate below what the pension should have paid out at), then removing the employee from their position while replacing them with contract labor
This looks really great on the balance sheet, but faces long-term viability as companies face loss of job knowledge and higher long-term contracting costs, that outweigh the fudged numbers they used to make the idea look feasible. Unfortunately, the ass-hats that come up with these ideas usually get bonuses and leave their positions before the shit hits the fans and shareholders are left holding the bag of a broken company and out of control contracting fees
Yes, but Oracle currently charges licensing based on the number of cores you are running their software one, databases in particular.
The massive number of cores in this chip (and transistor count increases with core count) would lead to large licensing fees, unless Oracle creates a means to limit the cores that their product runs on based on licensing
In the 90's it was pretty popular to tie application licensing to a CPU ID, I wonder if something similar would come into play here
With 32 cores, this chip must have the Oracle licensing people very excited
Given that no other 777 's have crashed into the Indian Ocean, and that the Indian Ocean Gyre would move wreckage from the West coast of Australia towards Africa...
Some questions come to mind:
1. What are the odds that this is wreckage from MH370?
2. Is there any other reason that people would be dumping 777 parts into the Indian Ocean?
3. If it is from MH370, can analysis of the Gyre provide additional insight into the location of the crash?
4. What are the tools that can be used to analyze the currents of the Gyre, and how accurate are they?
Apparently you missed my inherent snarkiness, having attended said "party school" and encountered prejudiced behavior like the GP refers to.
Not that anybody from Berkeley has ever behaved that way
If the red, green and blue lasers can be 'tuned' for intensity then it can produce colors in the RGB colorspace, which is not necessarily the "full spectrum of visible colors"
Yeah, plus it came from a "party school", not one of those elite left or right coast schools
"anybody can write crappy apps." FTFY
To go a bit further, given cushy enough tools (Dreamweaver comes to mind), any damn fool can put something out there. Will it be useful, or will it actually hamper the work that people are trying to do? That is a good question
What it comes down to, in my mind, is whether are not decent tools are being made available to people who are capable of producing something useful, or beautiful, from them
The common availability of the tools to create software, and the elimination of outrageous barriers to their use seems to be the goal to me
If we accomplish that, then people who have creativity, logic, etc will be able to create software that enables the people who use it to accomplish tasks, perform work, enjoy their lives entertain others, etc...
That seems to be what we should want, rather than some notion that every damn fool will be able to create software
Bang! thank you for saving me from my foggy memory
I tried looking up anything from Heinlein that fit my memories and couldn't find a trace, read a summary from wikipedia on Skylark series and it did not sound familiar, but you hit it dead on.
That would be pretty hilarious, although I would hope to have some compact fission/fusion reactor with about twice the expected life of the trip as a primary power source...
Things do go wrong... I remember an old Heinlein story where Cu (I think) was used to power their star-drive and somebody sent him and another astronaut on a 'one way trip to oblivion'.
They managed to react enough copper out of her wedding band to effect an escape, since Heinlein only killed a few of his protagonists
This could provide a basis for a 'constant acceleration drive', that could travel interstellar distances without requiring a reaction mass