Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it a good practice to have an is_deleted column in a SQL Server table or there’s another way of dealing with this question?
Another solution I can think of is to delete that row and inserting it to another table for deleted rows.
What’s the best solutions?
Thanks in advance.
Depends.
I’d go with the
IsDeletedfield, and then every-now-and-then run an archive process that moves these rows off to an archived table, such that they don’t take up room in commonly-queried tables, but can still be retrieved when required.