Article View: borland.public.vdbase.data.sql
Article #1625Re: SQL or not
From: Joe Yuzamas
Date: Mon, 10 Nov 1997 00:00
Date: Mon, 10 Nov 1997 00:00
61 lines
2988 bytes
2988 bytes
Anthony Suggestion... Order VDB 7.0 Client/Server. It has a native driver for MS SQL Server. Then rewrite your apps using SQL. That is if you really want to use MS SQL Server. My preference would be to stay away from MS SQL Server. But then thats my preference. -- Joe < jyuzamas@wrdiss1.robins.af.mil or jyuzamas@sprynet.com > Anthony Lopresti <anthonylNOSPAM@lawdiary.com> wrote in article <01bcebc7$dd08ec20$a8fba126@LoprestA>... > I thought I wanted to migrate MS SQL Server, but then I read the various > threads in this newsgroup concerning the use of it or similar dB servers. > So, in my never-ending quest to consume bandwidth, I want to re-kindle the > debate, but this time, within the context of _my_ scenario. > > I have a VdB app that I wrote to handle the logistics side of the part of > our business that generates 85% of our revenue. It's main table has 100 to > 200 K records at any time during the month with 88 bytes per record plus a > memo field. The table is a DBF and I use DML exclusively - no SQL. I need > two more apps: one to automate a paper-based part of our business that > generates the other 15% of our revenue; and another to replace a DOS > clipper program that a 3rd party wrote for us many moons ago to handle our > invoicing and accounts receivable. > > My first reaction was to build the two new apps with VdB, but I don't have > the time, and other people have already written apps to handle these, so > why re-invent the wheel? But, our highest priority with systems is that > they be highly, and preferably, seamlessly integrated. At the very least, > I don't want multiple copies of tables (like customer files) existing > simply because the apps don't want to (or care to) share data with other > apps. > > So, the solution I thought I came up with was to purchase apps that use MS > SQL Server to get their data. Then, I would simply convert my existing > apps to use MS SQL Server instead of DBFs. But, it sounds like I'm > probably going to take a performance hit on my main app (which runs slow > enough as it is) if I convert to MS SQL Server. > > Am I wrong? Is there a better way of doing this? Am I better off building > the two new apps in VdB with DBFs? > > BTW, I have about 6 users on an NT 4.0 network, but the main app resides on > a Win95 "server" for logistical and cost reasons (I can upgrade it to NT > server if need be). > > Thanks. > > PS Don't send me e-mail, I don't have access to that account anymore. >
Technical Details
Message-ID:
<01bcedf3$65ee8ea0$1030f489@jyuzamas.robins.af.mil>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<01bcebc7$dd08ec20$a8fba126@LoprestA>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: ff5a1,ef8a746a45c3dbae X-Google-Attributes: gidff5a1,public From: "Joe Yuzamas" <jyuzamas@wrdiss1.robins.af.mil> Subject: Re: SQL or not Date: 1997/11/10 Message-ID: <01bcedf3$65ee8ea0$1030f489@jyuzamas.robins.af.mil> X-Deja-AN: 288331455 References: <01bcebc7$dd08ec20$a8fba126@LoprestA> Organization: U.S. Air Force Newsgroups: borland.public.vdbase.data.sql