>>I don't want to start a "My database is better then your database" war ... but I need advice.
>>
>>We are have two servers connected by a hub:
>>#1 10BaseT\Ethernet - Novell 4.1
>>#2 Coax - Novell 3.1
>>
>>We will need to connect the new network to existing networks.
>>The current 4.1 network is max'ed out.
>>
>>Currently, we use Foxpro\Visual Foxpro\Visual Basic for our database needs. We need to start working with some gig sized databases (number crunching\accounting stuff). Assuming we use Visual Foxpro\Visual Basic, there are two questions.
>>
>>What operating system do we go with (NT Server or Netware).
>>What SQL backend should we use (MS SQL Server/Oracle/Sybase/etc)?
>>
>>We are mostly accountants here that also do programming but know very little about networking & client-server. We do not have a systems administrator (I hate installing software that says "Ask your network administrator".) Obviously we are going to have to take classes in whatever platforms we choose.
>>
>>But which platforms?
>>
>>Thanks,
>>Gene Berger
>>Nationwide Warehouse & Storage
>>Columbus, OH
>
>From practical experience of regularly working with mega sized files (mortgage data, et al.) approaching 2G in both FPD under DOS - both of which max out at 2G as also does VFP3, all of these under both netware and WINNT, and from looking at using MS-SQL for same reasons you quote, I heartily agree with Craig Berntson's reply to you in all respects.
>
>NT is relatively easy (my opinion) to set up, and also for users to use. VFP has speed and far greater scope for handling data manipulation and queries than MS-SQL however, with this arrangement you can always "upload" to MS-SQL if ever such a need arises later. In VFP you can also more readily potentially skirt the "huge file size" issue by careful design of constituent tables within the "Database", splitting stuff out into smaller related tables. Also VFP is going to be MUCH Faster than VB with files of this size. And finally, but certainly not the least important is that here in UT you have access to an enormous wealth of experience and support (not too obvious plug is it? :)) ). HTH. /psb.


I totally agree. Design the application in VFP using views and then upsize it to SQL Server. I might also suggest picking up last month's Databased Advisor that had an article on handling HUGE databases.

Craig