| Author |
|
rogerxw
Newbie
Joined: November 12 2008
Location: United States
Online Status: Offline
Posts: 10
|
| Posted: April 22 2009 at 01:33 | IP Logged
|
|
|
My pwrhome.db is over 200MB. Is it too big? I used ph_trimeventlog (2). What else is in the database? How do I clean it up?
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: April 22 2009 at 08:41 | IP Logged
|
|
|
Unless you’re trying to automate a whole apartment complex I would say that is large. Mine is 12MB and I trim to 2 days. Have you actually verified the trimming of the database actually occurred?
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
AllanMar
Groupie
Joined: April 02 2007
Online Status: Offline
Posts: 45
|
| Posted: April 22 2009 at 13:07 | IP Logged
|
|
|
I had this problem before. I let the event log grow until my db was huge. Then after running the trim event log it seemed to work but the database stayed huge. As I recall using the Rebuild option in the Database Maintenance utility solved the problem.
EDIT: It was either that, or some SQL commands Dave gave in a thread here on a similar topic. I can't remember actually
Edited by AllanMar - April 22 2009 at 13:08
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: April 22 2009 at 14:31 | IP Logged
|
|
|
Maybe this will address it. From Dave:
“The rebuild option is great if you've let your database get out of control such as never cleaning out the eventlog. If you let the DB get large and then clean the eventlog, the actual physical size will still remain. You can then use the rebuild option of the phupg to copy all of your data into a fresh new DB.”
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
rogerxw
Newbie
Joined: November 12 2008
Location: United States
Online Status: Offline
Posts: 10
|
| Posted: April 28 2009 at 00:40 | IP Logged
|
|
|
thank you for the input. I will try to rebuild.
|
| Back to Top |
|
| |
rogerxw
Newbie
Joined: November 12 2008
Location: United States
Online Status: Offline
Posts: 10
|
| Posted: September 29 2009 at 11:37 | IP Logged
|
|
|
Using phupg to rebuild the 2.1b database is great. My pwrhome.db is now only 5MB instead of 216MB. All event logs and web logs are still intact. Those are the biggist tables in my database. Thanks.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 06 2009 at 14:58 | IP Logged
|
|
|
Just an FYI, I would typically try to keep the PowerHome database to no more than 20MB. Adaptive Server Anywhere really doesnt have many problems (unlike MS Access) operating at the much larger sizes, but it will tend to go slower and make things like backups take that much longer.
As long you perform a regular ph_trimeventlog (or ph_exporteventlog if you want to save all your log data) then you should be good.
Dave.
|
| Back to Top |
|
| |
syonker
Senior Member
Joined: March 06 2009
Location: United States
Online Status: Offline
Posts: 212
|
| Posted: April 07 2015 at 09:07 | IP Logged
|
|
|
I know this is an ancient thread, but figured since
it's on-topic it's a valid place to start.
I'm going to kill my 2.1.4 PowerHome and upgrade to
2.1.5c; however, it's not even fully starting up
because the database is ENORMOUS.
It has actually kakked the remaining space of my
entire allocated hard drive on the VM (for a total of
over 17GB). Since I can't rampe PH to
"Rebuild/Fix/Compact" or do pretty much *anything* I
was wondering if there is a *lightweight* utility I
might be able to hit it with from the command line so
I can get it to a reasonable size for backup prior to
upgrade...?
NOTE: I also get the "sendmail()" error upon
posting to the forum that Skip references in his
latest round of posts.
-S
Edited by syonker - April 07 2015 at 09:08
__________________
"I will consider myself having succeeded when my house becomes sentient and attempts to kill me."
><(((º>`·.¸¸.·´¯`·.¸><(((º>¸.
·´¯`·.¸. , . ><(((º>`·.¸¸.·´¯`·.¸><(((º>
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 07 2015 at 11:05 | IP Logged
|
|
|
S,
Wow, thats a pretty large database. Unfortunately, the
only lightweight utility would be the PowerHome
Database Upgrade utility. What I would do is try the
upgrade to 2.1.5c. In 2.1.5c, the database has been
split into two files with the eventlog in its own
file. When you run the database upgrade utility for
2.1.5c, it won't even attempt to port over the
eventlog data so if it works, you'll have a nice
compact 2.1.5c database that shouldnt get out of hand
again (you can always just delete the phlogs.db file
and start with a fresh empty copy).
If it doesnt work, not sure if you have a backup copy
of a smaller version of the database. It may not be
your latest data but it would be better than starting
from scratch.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
syonker
Senior Member
Joined: March 06 2009
Location: United States
Online Status: Offline
Posts: 212
|
| Posted: April 08 2015 at 07:11 | IP Logged
|
|
|
Yeah, I kind of figured that would be the case. I went
ahead and deleted the sucker outright, and have been
following Skip's thread on upgrading from 2.1.4 to
2.1.5c in this
thread: home.com/forum/forum_posts.asp?
TID=4507&PN=1">http://www.power-
home.com/forum/forum_posts.asp?TID=4507&PN=1
-S
Edited by syonker - April 08 2015 at 07:13
__________________
"I will consider myself having succeeded when my house becomes sentient and attempts to kill me."
><(((º>`·.¸¸.·´¯`·.¸><(((º>¸.
·´¯`·.¸. , . ><(((º>`·.¸¸.·´¯`·.¸><(((º>
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Database too big
