SQL Server's Journal (original) (raw)
9:26a
I have some random questions, first using Yukon is there any changes that will affect the way I design databases?
Next, on a specific project I am thinking about incorporating mechanics into the database to help with database replication and backup. For example, one of the tables will be using versioning and I would thinking about adding an achchived bit field and once a day inserting all the records that hadn't been archived into another sql server for backup purposes. Then marking them as archived and thus the record wouldn't ever change because if there was a change there would be another insert with the new version.
As far as the other types of tables, I to would have an archive field and when the record was updated or status set to inactive (in essence deleted) the archived flag would be set back to 0 so it would get archived to the backup database.
Then if ever the main database ever dies, we can just point to the backup database and the data will be current.
Anyone done anything like this? I just don't have alot of experience with database backups and recovery, I mainly let that job be up to the admin guys.