do excess columns slow down a database?

Mitch

I get that there's a point where records can do that, but is it the same for columns?  Currently, my members database has about 40 columns.  They're not all essential fields, and could be broken off into other databases, but for birds-eye views, I liked having it in one place... except if it can slow things down...

Also, how would we know when we're losing speed?  I know that we can speed when debugging.  But even so, I have no idea when "good" starts to become mediocre...

Thanks!

Michael Udinski

Hey Mitch this isn't a simple answer to a simple question. It really depends but in short, I think you are fine. But you bring a good point. You might consider breaking things up into related tables if it makes sense from an organizational standpoint and database management perspective