I totally agree with Cyric. A generic white-box may work for a one or two server cluster, but not for time-critical systems. Besides, building a white-box with the kind of components you would need is still going to be in the tens-of-thousands of dollars....considering you will need stuff like Hot-Swappable Drives, Fiber HBA's, Redundant Power-supplies, dual (if not quad) processors, Gigs of memory...stuff that is very expensive and not-so-easy to find...basically vendor specific. With that kind of money being spent, it pays to just buy the vendor's package.
Fair enough, glad we got that settled.
We seem to feel the same way about Oracle. My ex-employer used to rave about it, and at my current job some of our production sites use it...but we try to push SQL Server to our clients. I've always felt that Oracle was way overpriced for what you get in the package...
That was a typo...it was going to be "two teams from India, One from New York"....had a serious brain fart I guess.
Sorry if I offended the AC, but his post didn't make any sense (not that mine did either)
Did the article state that the Oracle India team wrote the MSSQL conversion tool or just the child post? Either way, writing code to convert from SQL Server to Ingres is still catering to the competition. True, it may pull the minor few off of SQL Server, but once they are on Ingres the chances of them moving from there to Oracle are gonna be slim.
Yeah, no kidding. With all of the buzz about Indian programmers losing customer data and now catering to the competition, sure makes me want to offshore more and more...
I totally agree with Cyric. A generic white-box may work for a one or two server cluster, but not for time-critical systems. Besides, building a white-box with the kind of components you would need is still going to be in the tens-of-thousands of dollars....considering you will need stuff like Hot-Swappable Drives, Fiber HBA's, Redundant Power-supplies, dual (if not quad) processors, Gigs of memory...stuff that is very expensive and not-so-easy to find...basically vendor specific. With that kind of money being spent, it pays to just buy the vendor's package.
Fair enough, glad we got that settled. We seem to feel the same way about Oracle. My ex-employer used to rave about it, and at my current job some of our production sites use it...but we try to push SQL Server to our clients. I've always felt that Oracle was way overpriced for what you get in the package...
That was a typo...it was going to be "two teams from India, One from New York"....had a serious brain fart I guess. Sorry if I offended the AC, but his post didn't make any sense (not that mine did either) Did the article state that the Oracle India team wrote the MSSQL conversion tool or just the child post? Either way, writing code to convert from SQL Server to Ingres is still catering to the competition. True, it may pull the minor few off of SQL Server, but once they are on Ingres the chances of them moving from there to Oracle are gonna be slim.
ummm....3 teams one...2 were from India, one was an Indian in New York. Sounds like you didn't read the post, much less the article.
Yeah, no kidding. With all of the buzz about Indian programmers losing customer data and now catering to the competition, sure makes me want to offshore more and more...