Account without long-lasting activity — to remove or not to remove?

Well, how would a compromise solution not to be removed without notice to the user. I think the ideal option to send an email with a link to confirm that the account is needed. Pass the link and confirm that the record is needed if not delete it after 7 days after sending the request for confirmation. IMHO reasonable...

Definitely not.
Once a week for sure hear from "lost" user — "Damn, was in the army, all thought, and then surprise, the account still exists. Thank you!"

Yes, the question is moot. But I prefer going on a long forgotten website, discover that I had recorded a year ago.
Although now I am confused by the words "online 1 year and 1 month", because to actually use the service I'm starting just now.

Maybe you can in the database to have a field that indicates activity of the user, if the user is inactive box switches to false and all entities associated with this account is not used, the user is notified about it, but always able to return your account, just go to the site and thereby changing the false to true, I think you can come up with many more ways to reduce the load using this field.
Or can these users be stored in a separate database, from which they then can be returned when you move a user to the database is inactive, it is also worth to notify.
\r
To remove in any case it is not, users, anything can happen, someone decided to live a year away from civilization, someone has a huge project at work and no time to visit the resource, thousands, and removal in any case will lower the loyalty, the bits anyway, but people do.

In my opinion optimally to do something like "Backup". For example, did not come people a year and his account is archived, with him on the mailbox will be sent an email before and after the "backup". But in the archive all this Ivanitsa no more than say 2 years, then deleted.
\r
Pros:
— Do not lose user
— Discharged base
\r
Cons:
-it takes place in the second database for the archive

Do not delete.
\r
If such questions arise from the fact that a large number of users, type function get_user_name slowly start to work, then I would change the way of storing information about users. And the people are happy, and no brakes. There are no cons.

In any case, never remove the filled in data. Because anything can happen )
\r
If this in any way affect the performance of the system, make a mailing list that its data has been transferred in "archive", and throw off the link to recover.
\r
When "arhiviranje" transfer user data to another server.
\r
And don't forget to create the system recovery!