There are several points that you have to take into consideration here.
First off, you are pitting the relevance of the project (given the job description) versus the physical length of your resume. Most employers do not want to scan 6 pages of individual database projects you've been involved in, no matter what the job is. You have to really concentrate on highlighting relevant projects, and leave lesser items for discussion during the interview.
Secondly, it is quite often your side projects that will even get you the interview in the first place, no matter the magnitude. For example, I once wrote a ridiculously simple cartesian mapping application in an ActiveX control that would allow you to assign a coordinate grid to an image, and then track little boat icons on it given the coordinate of a real boat. It took probably 8 hours to write. I didn't even get around to making it update from a live gps feed or database.
I later interviewed with a company that makes an online mapping application. I made sure to include the project with links to a sample, and I'm convinced it's the reason I got in the door (and eventually hired), since they asked me about it endlessly during the interview. The relevance of the project vastly outweighed the actual size of it - what was important was that they found out that I understood the concepts they were looking for.
And on top of all this, you have to weigh the "feel" of the company, based on what you can discover about it. Is it a "cool" company, that might cater to idiosyncratic developers? Maybe put some more "fun" kind of projects on there. Is it a large bureaucratic company that is looking for people that follow directions and conform? Maybe limit the projects you include a little bit more.
And above all, don't overhype a project and make it sound like you did more than you really did. This will come out in the interview and leave you embarrassed and them disappointed. Stick to what you did do and what you do know. I've interviewed developers that put projects on their resume that they did 3 years ago in school, and then can't recall a single thing about the project. This just makes them look terrible. I'd say it's the #1 mistake from people that I've interviewed.