Re: Here we go again...WebDNA - SQL- Clustering
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66719
interpreted = N
texte = I'll be the first to admit that my strength as it pertains to SQL is the scripting/searching/use of it from the front end but as far as transactional logging. Imagine a scenario where the data gets mucked up somewhere throughout the day. And by mucked up I don't mean destroyed or unusable but rather something that managed to effect multiple data sets in an undesirable way. With transactional logging you can run from the point of your latest backup to ANY point in time forward. In fact you can combine this with data export routines to get multiple outputs of your data to find exactly what caused the issue rather than just jumping back to some data set that was thought to be "good". With MySQL and no TL'ing, an aggressive BU plan might have you backing up many times per day to minimize the loss of data in the event of an issue. Even then you're still rolling the dice. With TL you can do a full BU on more reasonable schedules and then move forward using TL to get to the last point in time and space when all was well. This starts becoming more and more important when you're dealing with sensitive data such as accounting data or in the case of schools, attendance and other types of data that come with strict state requirements. Just TRY and get 200 teachers to all enter their data again because your last BU was from the night before or even just 8 hours ago ;-) May God have mercy on your soul ;-) Honestly though, when it came to WebDNA only I was the designer, DBA, Server Admin, and Network Admin all at the same time (not to mention the project manager and client rep, etc ;-) (still am on most projects), but now I have a SQL admin who handles the server stuff as well as Server Admin and Network Admin. Its good because it spreads the load around. Its bad because I am not at the point where I can/need to fix anything and everything in the system. ;-) Anyway, hope the TL stuff makes sense. HTH Alex On 4/4/06 12:46 AM, "Donovan Brooke"
wrote: > A question: "transactional logging"... how does this benefit over a good > backup schematic? -- Alex J McCombie Adventure Skies Interactive (ASI) Alex@Adventureskies.com ------------------------------------------------------------- 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:
I'll be the first to admit that my strength as it pertains to SQL is the scripting/searching/use of it from the front end but as far as transactional logging. Imagine a scenario where the data gets mucked up somewhere throughout the day. And by mucked up I don't mean destroyed or unusable but rather something that managed to effect multiple data sets in an undesirable way. With transactional logging you can run from the point of your latest backup to ANY point in time forward. In fact you can combine this with data export routines to get multiple outputs of your data to find exactly what caused the issue rather than just jumping back to some data set that was thought to be "good". With MySQL and no TL'ing, an aggressive BU plan might have you backing up many times per day to minimize the loss of data in the event of an issue. Even then you're still rolling the dice. With TL you can do a full BU on more reasonable schedules and then move forward using TL to get to the last point in time and space when all was well. This starts becoming more and more important when you're dealing with sensitive data such as accounting data or in the case of schools, attendance and other types of data that come with strict state requirements. Just TRY and get 200 teachers to all enter their data again because your last BU was from the night before or even just 8 hours ago ;-) May God have mercy on your soul ;-) Honestly though, when it came to WebDNA only I was the designer, DBA, Server Admin, and Network Admin all at the same time (not to mention the project manager and client rep, etc ;-) (still am on most projects), but now I have a SQL admin who handles the server stuff as well as Server Admin and Network Admin. Its good because it spreads the load around. Its bad because I am not at the point where I can/need to fix anything and everything in the system. ;-) Anyway, hope the TL stuff makes sense. HTH Alex On 4/4/06 12:46 AM, "Donovan Brooke" wrote: > A question: "transactional logging"... how does this benefit over a good > backup schematic? -- Alex J McCombie Adventure Skies Interactive (ASI) Alex@Adventureskies.com ------------------------------------------------------------- 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/
Alex McCombie
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:
stuck time (1998)
Summing fields (1997)
pc (1997)
Size limit for tmpl editor ? (1997)
Updating fields from different platforms (1998)
HELP WITH DATES (1997)
vs (1997)
t or f (1997)
quick GREP question (2001)
how to include a name in from or to using Sendmail? (2003)
Severe Slowness (2005)
PSC recommends what date format yr 2000??? (1997)
EditPlus 2 WebDNA cliptext (2002)
Migrating to NT (1997)
summarizing date search by month... (2000)
[Webcat 2]Next (1997)
What am I missing (1997)
Check boxes (1997)
MacOS9 plugin 4.0.2b5 template security error (2000)
Web Catalog vs. ICAT (1997)