Re: Pervasive SQL 8.6

Thanks very much for your help.

Bill Bach wrote:
> You are correct, PSQL8 does NOT use log files in the same way as other
> databases, and backups are done by copying the files off to tape -
> -making them MUCH easier than other systems.
>
> If you plan on backing up the system while users have files open, then
> you'll want to have the Backup Agent to help with this -- a cheap
> add-on product. (www.goldstarsoftware.com/buagent.asp) Otherwise,
> you'll want to manually set up continuous operations mode -- see the
> article here (www.goldstarsoftware.com/press.asp) on getting proper
> backups.
>
> As for performance, you'll want to have lots of memory on the server --
> With Windows 2003 Advanced or Enterprise, go with as much as you can
> afford. With Win2003 Standard, the max the OS will see is 4GB. The
> database should be configured with 600MB to 800MB of cache, and for a
> system with 4GB of memory, you'll want to DISABLE the L2 cache (Max
> Microkernel Memory Usage = 0) and ENABLE the OS cache (System Cache =
> ON) for best results.
>
> In the disk channel, be sure to set up a striped and mirrored set of
> drives (RAID10) for the database files. If you can put a simple stripe
> for the Transaction logs, this is helpful, otherwise go with a single
> drive. Also, set up your SAN with a configuration of 80% memory set
> for write caching, and 20% for read or read-ahead caching. Having
> multiple FC I/O channels can certainly help, as well.
>
>
> Beyond this, there is no one "right" answer for performance monitoring.
> In fact, I recently helped a customer with a huge 8-way server, 32GB of
> memory, and a big, fast SAN with 4 FC cards, and we ended up changing
> some settings AWAY from what was normally considered optimal in order
> to gain performance. Just remember that your mileage will vary, and
> you should tune it for your own environment (and budget).
> Goldstar Software Inc.
> Building on Btrieve(R) for the Future(SM)
> Bill Bach
> BillBach@xxxxxxxxxxxxxxxxxxxx
> http://www.goldstarsoftware.com
> *** Chicago: Pervasive.SQL Service & Support - July 19-22 ***
> *** Chicago: Pervasive DataExchange Class - July 27-29 ***
>
>
>
>
>
> jrobertsatcorpnet.com.au wrote:
>
> > Hi,
> > I am new to this database product (normally MSSQL) and currently doing
> > a 15gb database migration to a new server. The new server has the
> > following specs:
> > 2 x 3.6 Xeon
> > 4gb Ram
> > 2 x 36gb Mirrors (1 for System and 1 for Logs)
> > HDS 2tb SAN with 2gb Cache
> > However after starting the install with the framework vendor I have
> > been told that PerSQL doesn't use logs and backups come just from
> > straight file copys. Is this correct? I have been looking through the
> > settings and transactional logging in enabaled and set to the same
> > drive as the system files. Are these the same sort of logs used in
> > MSSQL? Also performance is the key reason for this upgrade so I really
> > want to tune this server as well as possible. I have done the
> > following:
> > -Set the /gb switch in the boot.ini and set the cache allocation size
> > to 2gb
> > -Moved pagefile.sys to the SAN for better IO and enabled the use
> > system cache setting (i'm not sure if this is correct with the DB
> > being on the SAN?)
> >
> > I'm sure i'm still a long way off getting it working properly though
> > so any advice would be greatly appreciated. These are some of the
> > other settings I'd really like some input on:
> > -Log Buffer Size
> > -Transaction Log Size
> > -Transaction Log Directory
> > -Working Log Directory
> >
> > Thanks for reading!
> > James

.

Relevant Pages

  • Re: Database Size, Database Corruption, Message Store & Storage Group
    ... More careful monitoring of the server. ... Each extra storage group also requires more memory at startup, ... Also it is important to know if there was actually database corruption. ... In terms of backups, you should look at "how" you are performing backups. ...
    (microsoft.public.exchange.admin)
  • Re: SceCli Error 1202 filling up the Event Log!
    ... > after restarting the Win2003 server, the secedit.sdb database does not get ... >>> security database and have it recreated. ... >>> configuration\windows settings\security settings, you should inventory ...
    (microsoft.public.win2000.advanced_server)
  • Re: Pervasive SQL 8.6
    ... and backups are done by copying the files off to tape - ... you'll want to have lots of memory on the server -- ... drives for the database files. ... set up your SAN with a configuration of 80% memory set ...
    (comp.databases.btrieve)
  • Re: Moving DB Server
    ... NOT ALL THE SETTINGS, SUCH AS (registry settings: e-mail server setting, content sources settings: indexes). ... COPY the config database from A to B ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Win2k3 SP1 error: New transaction cannot enlist in the specifi
    ... Glad to hear it, Ronan, and it might come in handy to know that if the s**t ... > are NO installed COM+ components has to have the same COM+ MSDTC settings ... >> to a Windows Server 2003. ... >> Do you use SQL Username and password, or SSPI to logon to the database ...
    (microsoft.public.windows.server.general)