SSIS is a tool that would do the job well. Given certain other conditions, plain old T-SQL would be able to do it just as well. To use SSIS, you'd need to install the bits on a server, create a package for the process, and schedule execution of that package via SQL Agent, or another scheduler, or manual initiation. You would likely need to create a proxy for a domain account with permissions to conduct that work. To use T-SQL, you'd need to create a linked server to the other server/database, craft a batch of SQL commands to copy and truncate data, then use SQL Agent, or another scheduler, or manual initiation to start it. Talk to me now on

Hello, I want to regularly archive a table upto a certain date to another server/database and then purge the original table upto that particular date. Is SSIS the tool I should use? Thanks.

Hello Ryan, When you have complex manipulation, it is always suggested to go for SSIS. In your case, yes you should better use SSIS. Ofcourse you can achive the same with stored proc, but its complex. Best regards