Hello Everybody, I have a requirement where in I will have to move content from one web app to another web app in the same far. Well this migration process has to be automated and scheduled at midnight everyday. My thoughts for this requirement are: 1. Have a batch script scheduled. And basically this script is gary lapointe extensions where in it will copy the content from one list to another list. OR 2. have a Workflow running at background (this is tedious and I am convinced by this approach) OR 3. Content Deployment path in central admin Can somebody suggest me a better approach for this or if any of the above approaches are correct then let me know pros and cons of that method. thanks in advance

The simple way is STSADM -o import/export . Create batch script and run it form scheduled tasks.Oleg

Hi, What is the amount of data you want to move ? Is it only a list, a sub-site or a site collection ? For a site collection, you can use content deployment path in central admin. For a specific list it's possible to use the custom STSADM command from Gary Lapointe or create a custom timer job. For an entire subsite, you can also create your own custom stsadm command or create a custom timer job. Here is a link where you will find information about create a custom timer job : http://msdn.microsoft.com/en-us/library/cc406686(office.12).aspx As usual with Sharepoint there is more than one solution for a requirement. You have to choose the one that fits best your requirement. Hope it helps you, MarioMon Blog/My Blog (in french) LinkedIn

Hello Mario, There is lot of data which has to be moved on regular interval. And its only specific lists. Not the entire site collection or subsite. And can you let me know what is the difference between timer job and task scheduler. Whats the advantage of having timer job over scheduled job?

Hi, A timer job is similar to a scheduled task. Many features in SharePoint rely on timer jobs to run services according to a schedule. The Windows SharePoint Services Timer service (SPTimer) runs timer jobs. The first advantage of the timer job is that you keep everything in SharePoint rather than create a console application and configure it in the Windows Task Scheduler . The second one is that the timer service knows the topology of the SharePoint farm, and that you can load balance the jobs across all the servers in the farm or tie them to specific servers that are running particular services. I have to say that it's easier to create and debug a console application or a batch file than a custom timer job. If you're not comfortable with a timer job, you can choose the scheduled batch script.Mon Blog/My Blog (in french) LinkedIn

Hi, Gary Lapontes stuff works and is easy to use, dependent on your experience. Content Deployment is probably the easiest as there is a GUI, and can be scheduled or run manually. The choice isnt always about the best method, its what do you know and does your skill set enable you to resolve the business requirement both short term and long term or how long will it take you to learn. If your serious about SharePoint one day you will know all of the methods discussed and a few that have not been mentioned... Additional Methods: 1. If you know C# or VB create an event receiver and keep the content synced, you dont need to Create a WF. Your just copying the new items into another list 2. If you know SQL use SSIS you can read write data in SharePoint using the SSIS SharePoint Connector available on Codeplex http://sqlsrvintegrationsrv.codeplex.com/releases/view/17652, and documented on MSDN http://msdn.microsoft.com/en-us/library/dd365137.aspx -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.