I have an Extremely large DataBase File - is that bad?

[Victor Wise]

Hello,

 

I was wondering if there were negative aspects to having a ridiculously large DB file. I started out at about 50k, now, i've almost reached a megabyte in size. As far as I can tell, this is really just saturation from pointless searches and navigation.

 

Are there any negative affects of this? Is it worth dealing with?

 

 

Thanks,

 

victor

[tapuahk]

Hello,

 

I was wondering if there were negative aspects to having a ridiculously large DB file. I started out at about 50k, now, i've almost reached a megabyte in size. As far as I can tell, this is really just saturation from pointless searches and navigation.

 

Are there any negative affects of this? Is it worth dealing with?

Thanks,

 

victor

 

Iif you are referring to the super tracker mod increasing the size of your mod you need to go in and delete rows using the admin.

 

If not what modification are you using the is causing the database to grow so large from "pointless searches"??? >_<

[Jack_mcs]

Hello,

 

I was wondering if there were negative aspects to having a ridiculously large DB file. I started out at about 50k, now, i've almost reached a megabyte in size. As far as I can tell, this is really just saturation from pointless searches and navigation.

 

Are there any negative affects of this? Is it worth dealing with?

Thanks,

 

victor

That's not very large for a database. I have some clients whose database is over 70 MB. Some contributions will cause the database to grow more than they should and the tables they use should be cleared every-so-often. But at only 1 MB, I doubt that that is the case here. You should optimize the database periodically in phpmyadmin (or install the contribution that does that) and make backups, but other than that, there shouldn't be any concern.

 

Jack

[♥Vger]

As Jack said, 1Mb is nothing for the size of a db. We've got customers with databases over 200 Mbs in size.

 

Vger

[AJRYAN]

I have the user tracking mod on my site, and it can grow pretty fast. If you're using

that you should periodically empty the table - you may want to save the results

first though. My DB is about 40MB without it, but often gets up to over 120 pretty quickly.

I have a relatively small site with about 1200 products, with probably about 2-300 that

do not have descriptions.