FW: Oracle/Sybase/Informix/MS-SQL Server

I think this thread is getting way out of hand. The question was to compare NT and Unix as database servers, not to compare personal preferences. (Please don't blow up on this) I personally have worked with both as far as database servers and I think they both have their place. For example if you we going to setup a small (say 100-300 Meg) database with a small (say 5- 25) number of users I think there are any number of NT solutions out there that can handle your needs. But say on the other hand your say at least one of the two above areas is larger you may see benefit to moving to a Unix server. The reason why I say this is that there are a lot of small shops out there that have no IS people on their staff and I don't care what anyone says but for a low volume server you can not beat NT. This is easy to say since most of my experience is from the UNIX world but its true. Russ }---------- }From: Scott P. Smith[SMTP:spsmith@ix.netcom.com] }Sent: Friday, December 27, 1996 2:31 PM }To: informix-list@rmy.emory.edu }Subject: Re: Oracle/Sybase/Informix/MS-SQL Server } }I feel like I have to point out that vi as well as UNIX shells and }utilities have been available for Windows/Windows NT for years. I've used }MKS toolkit (contains awk, vi, make, etc.) on Windows and it's worked fine }for me. } }I do have some complaints about Windows though. My biggest complaint is }that it took Microsoft until Win95 to provide a 32-bit preemptive }multitasking protected memory environment. Also it wasn't until Win95 that }Microsoft included TCP/IP as a part of the OS. Before that, you had to use }a third party TCP stack. The main reason I choose to develop software for }Windows is that ~100 Million people run it. } }>Unix, is, on the other hand *expert* friendly. The tools are powerful }>and flexible. The ancient test of a good tool is that not only does it }get }>used for things which the author never intended, but that it performs }>*well* in these circumstances. } }> I use the vi editor. It's got a learning curve like a brick wall, but }> having mastered it, I wouldn't swap it for *anything*. }> }> When confined to Microsoft, I pull my hair with frustration of the }extreem }> difficulty I have in persuading it to do the things that should be }trivial. }> } }