Archival and purging

How to implement a optimal archival and purging in MSSQL SERVER
databases?? That depends on what you mean by archival and purging. You need to find out what the business requirements are for all of your data first. After you have clearly defined that, you can map out the data that will fit that business requirement. You can only then create the optimal archive and purging processes, which will vary greatly by what those requirements are.|||Thanks for that, My requirement is quite simple.
I am working for a popular bank and I have to retain data only of the past 3
years and other data must be archived.

any clue/url links to assist me|||Create views for all tables that need to be archived/purged. Don't forget to take into account all dependencies. The views should have a WHERE clause that would filter out anything that is less than 3 years old:

...WHERE <date_field> <= convert(char(10), getdate(), 101)

Use those views to archive the data. You can use BCP if you want to keep that as text files and then zip them up, or you can have a separate database that you can populate with archived data, then back it up, and then empty it (truncate for example on all tables). Then you use the same set of views to perform your deletes from your production database.