make updates in a temporary database

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 57642
interpreted = N
texte = I have a site where making to the changes during "peak" periods causes my admin functions to basically go s-l-o-w or the admin pages freeze up it seems. Only during these peak user periods. It's not practicle to make changes during off-peak periods, so that can't be the solution. I'm thinking that when I'm making changes to the database, and people are accessing this same database during this period, that's when my issue appears. It's not a large database, maybe 2 megs or so. I was thinking working on an exact duplicate of the "live" database and then when changes are done "swapping" the worker version with the "live version. Anyone doing something like this?? How did you approach it all codewise? I'm still using vers 4.5 Thanks   __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover ------------------------------------------------------------- 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://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: make updates in a temporary database ( Brian B. Burton 2004)
  2. Re: make updates in a temporary database ( Lester 2004)
  3. Re: make updates in a temporary database ( Lester 2004)
  4. Re: make updates in a temporary database ( Tim Robinson 2004)
  5. Re: make updates in a temporary database ( "Sal" 2004)
  6. Re: make updates in a temporary database ( charles kline 2004)
  7. Re: make updates in a temporary database ( "Gary Krockover" 2004)
  8. make updates in a temporary database ( Lester 2004)
I have a site where making to the changes during "peak" periods causes my admin functions to basically go s-l-o-w or the admin pages freeze up it seems. Only during these peak user periods. It's not practicle to make changes during off-peak periods, so that can't be the solution. I'm thinking that when I'm making changes to the database, and people are accessing this same database during this period, that's when my issue appears. It's not a large database, maybe 2 megs or so. I was thinking working on an exact duplicate of the "live" database and then when changes are done "swapping" the worker version with the "live version. Anyone doing something like this?? How did you approach it all codewise? I'm still using vers 4.5 Thanks   __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover ------------------------------------------------------------- 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://webdna.smithmicro.com/ Lester

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:

'page impression' techniques for banner ads (1999) Semi-OT: PanIP patent infringement case (2001) [WebDNA] Webdna, Css & ie (2011) Date Comparison (1998) Secure Server (1997) Playin Tricks (2006) Re:slowness (1998) WCS Newbie question (1997) Searching multiple Databases (1997) emailer setup (1997) Setting up WebCatalog with Retail Pro data (1996) Demo math questions (2000) 2.0 Info (1997) Math (1997) Reserved Words (2003) 2nd WebCatalog2 Feature Request (1996) [date] formatting bug inside [orderfile]? (1998) how many (hideif & showifs) is too many? (2001) What am I missing (1997) process SSI (1998)