InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comMon, 20 May 2013 06:11:21 GMT20http://www.sqlservercentral.com/Forums/Topic605835-149-1.aspxI have the same issue and was wondering what you came up with for a sooutionTue, 25 Sep 2012 19:47:52 GMTMike01http://www.sqlservercentral.com/Forums/Topic605835-149-1.aspxI worked on a similar problem where I had to merge 17 departments into a master database, where each department shared a common database schema. The merges took place sequentially, and each merge simply appended its data to the growing master store.One each merge, the primary and foreign keys are re-caculated as the script runs (using a junk variable on each table to save its old key values so they can be used to compute the new values during the merge).I've done lots of this stuff, if that helps.GlenWed, 12 Sep 2012 23:20:39 GMTGlen Cooperhttp://www.sqlservercentral.com/Forums/Topic605835-149-1.aspxActually I've got a similar challenge. I couldn't see any replies here. How did you get on?Tue, 11 Sep 2012 11:07:42 GMTtim.kendallhttp://www.sqlservercentral.com/Forums/Topic605835-149-1.aspxWe have SQL Server databases located on different servers for our hosted web application.Each database can house multiple 'customers' along with their data.We have the need to be able to 'move' data for one or many customers to from one server to another server.Moving the data from one server to another will require copying a 'slice' of data for a selected customer to a destination SQL Server that will already house other customers.Upon moving the data, primary and foreign keys from the source data cannot be directly copied to the destination server, since these most likely will be already generated for another customer on the destination server.We have been looking into several approaches to accomplishing what we want including:1) Writing a Windows Application that taked in user selections for source and destination databases and connectionstrings. Then reading the data from the source database into a dataset or something and sending the data to the destination database in chunks.2) Investigating using SSIS to write a package that will be able to migrate a customers data from the source to destination, also handling the keys? Is this possible?3) Having linked servers on each of our database servers and using cross database querys to 'Insert Select' the data from the source to the destination. Can the linked server name be set in sql dynamically so as to accomidate a users selection for server.I thought maybe some of the SQL experts here have already worked through this type of situation and appreciate any recommendations.Thanks in advance for your suggestionsThu, 20 Nov 2008 07:57:00 GMTdon_querry