More on the replication story. Anyone have an idea? I find it funny as hell myself. "Open a browse on a table and it's all there pick what you want."
> The reason we are looking for a way to migrate updates to SQL Server over > to > FoxPro is to put a band-aid on a performance problem until they have the > time to rewrite the application in .NET. > > Currently, they have an application written in Visual FoxPro 8 that used > to > have a FoxPro database on teh backend. They moved the database to SQL > Server, but still use the FoxPro front end. They have a data layer in the > middle that handles passing the data back and forth between the FoxPro app > and SQL Server. > > The problem is that they have screens that pull back all the data from > certain key tables that are pretty large. I don't know all the specifics > (since I know almost nothing about FoxPro) but they say when they had the > FoxPro database, the app would simply open a pipe to the data and they > could > bring back the first screen full of data in a couple of seconds, and then > Foxpor would leave the pipe open so it could smootly scroll > forward/backward > throught the results without having to issue another data request. > Therefore, the application is not built with any form of paging > capability. > > The proplem they've run into now that SQL Server is the database is that > in > order to simulate the scrolling capability of the FoxPro based tables, the > middle layer has to pull all the data into a cache area first. Needless to > say, this takes a long time (5 minutes or more). The users are not happy > having to wait that long everytime the data needs to be pulled into the > cache, not when they used to be able to bring the data up in a matter of > seconds. > > They realize the proper way to write the app for SQL Server would be to > put > in a paging mechanism and bring back data in chunks, but that would > require > and extensive recodign of the application to put that change in all the > screens. Since they are in the process of completely rewriting the > application in .Net to replace the FoxPro app in the next year or two, > they > dont' want to spend that much effort rewriting the existing app at this > time. > > As a quick fix, they had the idea of having the application connect to and > read from FoxPro tables as it did before. These FoxPro tables woudl be > copies of the tables in SQL Server. SQL Server would still be the > datasource > of record so all updates woudl go to the SQL Server tables only and some > mechanism would be needed to keep the FoxPro tables updated in near-real > time. Hence, the reason I was looking for a replication solution. Looks > like > I may need to go another route than recplication however, something with > minimal latency. > > However, if anybody has any other ideas how to solve the query performance > problem another way, I'd be open to any suggestions. > > -Ray > > ---------------------------------------- > Ray Rankins - [EMAIL PROTECTED] > Gotham Consulting Services, Inc. > www.gothamconsulting.com > >> -----Original Message----- >> From: Stephen Russell [mailto:[EMAIL PROTECTED] >> Sent: Sunday, February 11, 2007 5:59 PM >> To: [EMAIL PROTECTED] >> Subject: RE: [SQL2K] Replication to Foxpro >> >> Ray Rankins <mailto:[EMAIL PROTECTED]> wrote: >> > The initial thought was to write a process that would kick off on a >> > scheduled basis to pick up the changes and forward them to Foxpro, >> > but a) wanted something that was more real-time, and b)thought we'd >> > try replication before going to the trouble of writing a custom >> > process. >> > >> > Where is this Profox site you mention that I can post this >> query too? >> >> You have to register @ leafe.com. You can save your time, I >> already posted >> it there. You can try the UT www.universalthread.com which is a free >> membership but will ask you to pay for better services. >> >> No replies as of yet. >> >> I guess why push back to Fox? When they should be reaching >> from SQL Server >> instead :) >> >> >> >> Stephen Russell >> DBA / .Net Developer >> >> Memphis TN 38115 >> 901.246-0159 >> >> "A good way to judge people is by observing how they treat those who >> can do them absolutely no good." ---Unknown >> >> http://spaces.msn.com/members/srussell/ >> >> -- >> No virus found in this outgoing message. >> Checked by AVG Free Edition. >> Version: 7.5.441 / Virus Database: 268.17.35/680 - Release >> Date: 2/10/2007 >> 9:15 PM >> >> >> >> >> ------ >> For archives, see http://www.sswug.org/archives >> For list assistance, contact [EMAIL PROTECTED] >> To unsubscribe, email [EMAIL PROTECTED] with >> UNSUBSCRIBE SQL2K in the body of the message. >> >> > > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact [EMAIL PROTECTED] > To unsubscribe, email [EMAIL PROTECTED] with > UNSUBSCRIBE SQL2K in the body of the message. > > > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
