troubleshooting Question

How should I handle 'working' tables?

Avatar of vstack
vstack asked on
ASP.NETMicrosoft SQL Server 2008
2 Comments1 Solution142 ViewsLast Modified:
Hi guys,

This is a database design question.  I have a table tblObjectives that holds the objectives our courses.

The curriculum developers will be able to edit and add objectives.  The tblObjectives is 'live' to the faculty so changes are viewed immediately.  This is good but I would like to allow curriculum people to update the db without the faculty seeing changes until they have been approved.

Currently, the curriculum guys use the system to save a .pdf of the current version which the instructors can view while the course is under modification.  While this works to a certain extent, (when they remember to do it) I was thinking that maybe I should have a 'working' table where courses under revision would reside until all changes have been approved.  At that point, the 'working' data would be moved to the permanent tblObjectives.

I would like some input on how a 'professional' database designer might handle this sort of thing. Maybe I am completely off base.


Join our community to see this answer!
Unlock 1 Answer and 2 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 2 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros