Re: SQL upsizing

From: Edhy Rijo (erijo_at_msn.com.NO_SPAM)
Date: 03/16/05


Date: Wed, 16 Mar 2005 14:30:02 -0500

Hi Jeff,

I agree with Dan, but make not mistake, if your application requires to use
a SQL database MS, MySQL or ORACLE, then your programming habit must change.
Your users will get used to the new way of getting the data and will really
appreciate the speed gain if they are suffering some kind of slow data
retrieval now.

Maybe it is even time to do an overhaul to the application. If you are not
using a framework, I will suggest you to start shopping around for a good
one that really support Client Server. I use Visual ProMatrix
www.promatrix.com for many years and am really happy with it. The idea
behind the framework is to use classes already proven that will expedite the
application development and help you with the C/S stuff, and get ready to
use remote views, cursor adapters and in some cases SQL Pass Through (SPT)
to get your data for some custom procedures.

Good Luck!

-- 
Edhy Rijo
www.progytech.com
Bronx NY
Visual ProMatrix Life MVP!
"Jeff Grippe" <jgrippe@hilldun.com> wrote in message 
news:113guut55cc3lcf@news.supernews.com...
> This is going to be a very hard sell to my users who have gotten used to 
> certain ways of doing things such as "Browsing all customers". I saw the 
> client/server fox book and while it seems like a must have it doesn't 
> cover the specific topic of converting non-c/s apps in as much detail as I 
> need.
>
> Where are the 15 years worth of articles?
>
> Thanks,
>
> Jeff
> "Dan Freeman" <spam@microsoft.com> wrote in message 
> news:OrVMUGlKFHA.1176@TK2MSFTNGP12.phx.gbl...
>> Jeff Grippe wrote:
>>> Has anyone been through this type of conversion and can you tell me
>>> how you've solved some of these problems? Are there any articles or
>>> books that specifically address moving from VFP Tables to SQL server
>>> based databases?
>>
>> There are about 15 years' worth of articles out there, and several books.
>> Start here:
>>
>> http://www.hentzenwerke.com/catalog/csvfp.htm
>>
>> Your entire mindset needs to change when moving to a client/server
>> architecture. The "zen" is to only retrieve those records needed for the
>> current task. Browse all customers? NO! You ask for a name and bring back
>> only those that are a close match for a picklist if needed.
>>
>> The mantra is to minimize the amount of data traveling across the wire.
>>
>> Your SEEKs and REPLACEs are still possible using remote views, preferably
>> parameterized to limit their size.
>>
>> Good luck!
>>
>> Dan
>>
>>
>
> 


Relevant Pages

  • Re: Relational database & OO
    ... And when was the last time you saw an RDB that stored a telephone ... The modern relational theory permits to store values of user-defined type: ... Neither do the relational model or SQL. ... Your comprehension of the SQL database performance is not good. ...
    (comp.object)
  • Event log errors after moving sharepoint 3.0 database
    ... After following a procedure to move the location of the SQL databases from ... SQL Database 'WSS_Content' on SQL Server instance ... The local computer may not have the necessary registry ... information or message DLL files to display messages from a remote computer. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: ISA Log to SQL Database Question
    ... I am actually logging to an Access DB and the logs had grown to over 2 GB. ... The MSDE that comes with ISA or the real "full" MS SQL ... >> I have a question about ISA Logging to a SQL Database. ...
    (microsoft.public.isa.configuration)
  • RE: Automate Active Directory User Maintenance
    ... Hmmm...I know Quest has an ID management tool as well, but they are pricey. ... We've set it up for a client where the information is read from a SQL table ... could it evaulate the users in the SQL database ...
    (microsoft.public.windows.server.active_directory)
  • Re: IIS & SQL, NT authentication for Web
    ... Hi Dan. ... | Subject: Re: IIS & SQL, NT authentication for Web ... | I guess I wanted to confirm that, yes a user should Authenticate to SQL ... as your Internet users won't have Windows NT accounts on your ...
    (microsoft.public.sqlserver.security)