Re: Core Database integration
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 38440
interpreted = N
texte = Thanks Charles, Our integration is still in the drawing board phase but my initial thoughts are:Perhaps every day (at 5) the orders from WebCat would sync with the Progress written (SQL) database to update it on what it sold. WebCat would also verify customer info against our SQL database and perhaps write any differences to it.One consideration we have is an extra cost for the WebSpeed module which allows for the ODBC/SQL compatibility in our Progress database. From your response, speed might be an issue??? We are thinking about having a feature that will automatically bring up a clients purchase history when they specify who they are and say they have ordered from us in the past. This might happen more than a few times a day??? who knows.Anyway, do you have an idea at what threshold the communication becomes too slow in an ODBC setup?? Our WebServer host is a G4 with a bunch of RAM. I don't think it will be a queque but our SQL database is not a real speed demon. One thing we could do is schedule as many tasks as possible during after ours to avoid the processor tasks and bandwith that is taken up by our Customer Service during the day.Also, our SQL database is behind our firewall which I guess it would take some doing to open up the right ports for talking from WebCat to our progress server inside our LAN.I tend to lean towards ODBC also but would like to more opinions from admins who have integrated ODBC into there WebDNA systems.Thanks again. Charles Kline wrote:> On 9/6/01 1:38 PM, Donovan Brooke
wrote: > [snip] Is this SQL database > going to see a lot of traffic? Will this just be a once in a while thing? > > I have not used WebCat to connect via ODBC but have heard it is a bit slow. > SQL is real easy to use, so my thoughts would be that if you can get away > with the speed, just do the SQL connections and don't worry about trying to > sync the two. > > Hope that helps. > > Charles > > --------------------------------------------------------------- Donovan D. Brooke Systems Administrator/ Assc. Art Director Epsen Hillmer GraphicsI know I'm making progress when I look at the questions I have asked in the past and think to myself... how stupid was that ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Thanks Charles, Our integration is still in the drawing board phase but my initial thoughts are:Perhaps every day (at 5) the orders from WebCat would sync with the Progress written (SQL) database to update it on what it sold. WebCat would also verify customer info against our SQL database and perhaps write any differences to it.One consideration we have is an extra cost for the WebSpeed module which allows for the ODBC/SQL compatibility in our Progress database. From your response, speed might be an issue??? We are thinking about having a feature that will automatically bring up a clients purchase history when they specify who they are and say they have ordered from us in the past. This might happen more than a few times a day??? who knows.Anyway, do you have an idea at what threshold the communication becomes too slow in an ODBC setup?? Our WebServer host is a G4 with a bunch of RAM. I don't think it will be a queque but our SQL database is not a real speed demon. One thing we could do is schedule as many tasks as possible during after ours to avoid the processor tasks and bandwith that is taken up by our Customer Service during the day.Also, our SQL database is behind our firewall which I guess it would take some doing to open up the right ports for talking from WebCat to our progress server inside our LAN.I tend to lean towards ODBC also but would like to more opinions from admins who have integrated ODBC into there WebDNA systems.Thanks again. Charles Kline wrote:> On 9/6/01 1:38 PM, Donovan Brooke wrote: > [snip] Is this SQL database > going to see a lot of traffic? Will this just be a once in a while thing? > > I have not used WebCat to connect via ODBC but have heard it is a bit slow. > SQL is real easy to use, so my thoughts would be that if you can get away > with the speed, just do the SQL connections and don't worry about trying to > sync the two. > > Hope that helps. > > Charles > > --------------------------------------------------------------- Donovan D. Brooke Systems Administrator/ Assc. Art Director Epsen Hillmer GraphicsI know I'm making progress when I look at the questions I have asked in the past and think to myself... how stupid was that ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Donovan Brooke
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Webcat no longer supported? (2006)
[Announce] WebCatalog 2.1 Released (1998)
Separate SSL Server (1997)
WebCatalog Hosting (1996)
Exclamation point (1997)
[Fwd: Rotating Banners ... (was LinkExchange)] (1997)
Running 2 two WebCatalog.acgi's (1996)
WebCat2 - [format thousands] (1997)
E-mail loop ! (1997)
Help with Repost Data msg from form (1997)
WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997)
foreign character sets and conversions (1998)
Max Record length restated as maybe bug (1997)
process SSI (1998)
[WebDNA] Quick Grep question (2009)
Server Creation - vendors (2005)
No luck with taxes (1997)
WebCat (or other) Indexing (1999)
Sorting (1998)
Setting up shop (1997)