[p4] Very big Perforce file : db.have

[Melissa Kacher]

It's completely normal. Db.have will always be the largest file in
Perforce, and it is in no way unusual for it to be many Gigs in size.
It's not dangerous in any way to NT, or to Perforce. I've seen a dozens
of databases with db.haves in that size range, all on NT,  and none of
them have had a problem. 

If this still bothers, you can shrink the db.have somewhat. Delete all
obsolete clients from you database. Then take a checkpoint, and restore
that checkpoint to rebuild the db.have in the most compact manner.

If you have a real problem with your database because of this, I'd
submit that your server and your database are mismatched. Get a more
powerful server, with a hefty amount of CPU and memory and good disks.
Don't go overboard on any one component (CPU, memory, or disks) but keep
them all balanced.


Thanks,
Melissa


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Andres Fuentes
Sent: Wednesday, August 09, 2006 7:37 AM
To: perforce-user at perforce.com
Subject: [p4] Very big Perforce file : db.have
Importance: High

	Hello all,

recently I've changed our license file in the perforceroot folder, for
that I revised the rest of files and someones are very big...
Could be dangerous for our Perforce system that any db.* files has more
than 2Gb size? 
I know that this is critical on NT, but could be dangerous on Linux to?
Exists any way to repare it?

Thanks in advance


A.F.
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user