re: Large Database Options?

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 22473
interpreted = N
texte = >We are in process of adding more memory to handle the db but I anticipate >that I will run into the same problem later on. This database was provided >by one of our suppliers. I will need to integrate databases from 4 or 5 >more suppliers once I get this working. I was just looking for some other >options in conjunction with throwing more memory at the system.There are certain hybrid approaches you can take, one of them being to use the [SQL] context to grab information that is less-frequently used (such as product descriptions, customer history, etc.). That way you keep the necessary high-speed data in WebCatalog's fast-access RAM-based areas, and you maintain the other slower data in the slower back-end databases like SQL.Also, we've found that many people get databases with huge numbers of trailing spaces in them (a holdover from the old mainframe days) and simply stripping those will shrink the RAM footprint of WebCatalog significantly. Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. re: Large Database Options? (PCS Technical Support 1999)
  2. Re: Large Database Options? (Bob Minor 1999)
  3. re: Large Database Options? (Juliana Sun 1999)
  4. Re: Large Database Options? (Kenneth Grome 1999)
  5. Re: Large Database Options? (Dave MacLeay 1999)
>We are in process of adding more memory to handle the db but I anticipate >that I will run into the same problem later on. This database was provided >by one of our suppliers. I will need to integrate databases from 4 or 5 >more suppliers once I get this working. I was just looking for some other >options in conjunction with throwing more memory at the system.There are certain hybrid approaches you can take, one of them being to use the [SQL] context to grab information that is less-frequently used (such as product descriptions, customer history, etc.). That way you keep the necessary high-speed data in WebCatalog's fast-access RAM-based areas, and you maintain the other slower data in the slower back-end databases like SQL.Also, we've found that many people get databases with huge numbers of trailing spaces in them (a holdover from the old mainframe days) and simply stripping those will shrink the RAM footprint of WebCatalog significantly. Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ PCS Technical Support

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:

syntax question, not in online refernce (1997) raw field names (2001) Help! WebCat2 bug (1997) [WebDNA] Which one, how to install (2013) off topic - dna snipets (1997) NT version (1997) emailer setup (1997) Payment Processors (2006) Quickie question on the email templates (1997) mailhost-check (1999) Looking for a Manual (1997) [WriteFile] problems (1997) blank page from template (1997) $Append for Users outside the ADMIN group (1997) test (2003) SQL db type (2006) Help formatting search results w/ table (1997) WebCatalog as a ListServ (1998) autosensing lanague selection (1997) Sort Order on a page search (1997)