Venu--

It sounds like you are on the right track. It is definitely a good idea to practice restoring your backups.

I would suggest that you create a test database to work with. That way you could practice a side-by-side restoration (restore the backup file as "Database2" to exist alongside Database1); you could over-ride the existing (corrupted) Database1 (by using the REPLACE command in your script), and you could learn about differential backups and point in time restorations.

These are all good tools, but you really should not experiment with a production database.

I'm not sure what you are asking for with regards to testing a "corrupt" database. With a test database you could perform many actions to simulate potential mistakes. You could delete entire tables, you could "accidently" delete a user, or you could test your ability to restore to a point in time by having a job which inserted record into a test table every minute. You could then delete some of those records and try to recover the data by using differential or log backups.

Be sure to look at Microsoft Books On Line (BOL) for ideas and commands for these options.

Cheers,

Elliott