hello all.. we are using Sharepoint 2010. We have a software factory.. they dont have access to client's sharepoint admin application. So, when they create a new sharepoint site, it s ok because they send the entire database to restore at the client. But, the problem is when the application is already working, and we get a new change request ( example: Add a new Library, or add a new field to existing library ). Which is the best way to make a package and send to the deployment team without replacing the entire database ? Thanks !

I would look into using Ship logs functionality that comes with SQL Server. For new libraries you could create it, export it as a template, and the import it on the other side. But for field changes, that is going to be more difficult. Not sure about that one unless you want to use the COM object and run some code. Hope that helps, SharePointNinja

The most robust approach is to use the feature/solution framework. A feature is a package of assets (like a library template) and a "solution" is a collection of one more features. You create the solution, send it to the deployment site and then use a command line program to deploy it to the target farm.--Paul Galvin, Computer Generated Solutions (CGS) Microsoft MVP - SharePoint Blogging @ http://www.mstechblogs.com/paul Twitter @ http://www.twitter.com/pagalvin