|
Home > Archive > SQL Anywhere Mobile > February 2006 > Shrink the Log file of the database
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Shrink the Log file of the database
|
|
| Helveta 2006-02-25, 9:50 am |
| We are using Sybase ASA 9.0.2 on a central server. Several
PDA's synchronise via Mobilink to this database. The
database file (.db) is about 15Mb, but the TransationLog
(.log) has now reached 100+Mb. At first I though about isng
the -m flag on the database engine to delete the Transaction
log after each control point, but in the notes it suggests
that the Transaction log is needed by Mobilink.
Is there a method to shrink the Transaction log on a
scheduled basis.
Thanks
Alex
| |
| Breck Carter 2006-02-25, 9:50 am |
| The transaction log on the *consolidated* database is not needed for
MobiLink synchronization.
The -m option is generally not recommended because it limits your
options when it comes time to restore from a backup. You should
instead use dbbackup to backup the database and log file, then rename
and restart the log file. For example:
" %ASANY9%\win32\dbbac
kup.exe" -c "..." -r -y bkup
Breck
On 22 Feb 2006 08:09:21 -0800, Helveta wrote:
>We are using Sybase ASA 9.0.2 on a central server. Several
>PDA's synchronise via Mobilink to this database. The
>database file (.db) is about 15Mb, but the TransationLog
>(.log) has now reached 100+Mb. At first I though about isng
>the -m flag on the database engine to delete the Transaction
>log after each control point, but in the notes it suggests
>that the Transaction log is needed by Mobilink.
>
>Is there a method to shrink the Transaction log on a
>scheduled basis.
>
>Thanks
>Alex
--
breck.carter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
|
|
|
|
|