Yeah, that was definitely an interesting subject line. LOL. I would recommend keeping each person as a separate entity in your database, and relating them together. This way you can still track spouses, but if one is no longer a customer, then you can archive just that one.

If your database is set up so both spouses are on the same record, but you don't want to lose one spouse's information after a death/divorce, then you could duplicate the record, note it accordingly, and then archive it.

It's really just how YOU want to do it. I would opt for the first method. I like to keep each person separate. Group them together if you want, but each person should be their own entity. Kind of like how I have it set up in the ABCD.