I am using a SQL 2008 express edition. Windows Client-server architecture. Datalayer sits in the server. I am planning to implement database archiving and DB backup restore . the difference between them is in archiving i need to delete the entries after i take the backup. I also need to restore the DB in a different pc. what are the mechanisms i should be looking at.
Since you're using Express you won't have access to SQL Agent, so you'll need to schedule and control this through your own code. Backup and restore are obvious topics to look up. Since you're planning on deleting data I'd suggest ensuring that your database is in the right recovery model and if you have it on Full that you have log backups in place. Further, you should focus on breaking up your delete transactions into smaller chunks to ensure that you don't have to grow the log to large sizes. Except for the lack of SQL Agent that's pretty much the same things to cover that you'd need to do if you were on the full product.
Well, for the archiving bit, it sounds like you just want to run a truncate on all the tables after you take the backup. To restore a backup on a local machine, we use a powershell script to go out to the network, copy the latest backup locally, and then restore it. Just a thought.
My personal opinion...it sounds like you're using SQL Express to save some dough when you really need to store much more data than it can handle. What I think you're proposing to do is not really archiving, but copying a database and truncating or deleting just as dykesa says above. This will do nothing but cause you major headaches down the road. My advice if my assumption is right is to spring for the license or find an alternative that can handle the load. And if my assumption is not correct, well, then I just don't understand! :)