Move data from Production to Development database
In my humble opinion and since this is an SSIS Forum, the easiest + elegant way to move, or in your case I guess copy a database (since you are taking it from test to prod) is by using a Copy Database Wizard - http://msdn.microsoft.com/en-us/library/ms188664.aspx. To start, in SQL Server Management Studio, in Object Explorer, expand Databases, right-click on the target database, point to Tasks, click Copy Database and way you go. Read on the article above.Arthur My Blog
January 22nd, 2011 2:55pm

you can select all tables in the Import/Export Wizard ( select top most check box near the source label) then click on "edit mappings" then in new window, check the "delete rows in existing destination table" Am I understood your request clearly?http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2011 2:57pm

When I restore a database, I loose all of the permissions for stored procedures and functions. Also I go through the steps of removing the application user account from a schema, and recreating the account. But doing so looses all the permissions from the stored procedures. The database is small in terms of data, but is complex in terms of the number stored procedures and functions. I want to be able to do this restore frequently so I can make production data available for testing the application. So reseting all these permissions is a big pain. So is there a way I can do the restore and not loose permissions etc. I am running SQL 2005. Thanks in advance...Ed Ed
January 22nd, 2011 3:38pm

you can generate sql script for permissions and after restore just run that script on target database.http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2011 3:53pm

Normally when a database is restored, the database logins and the server logins just need to be re-associated. Look at the system stored procedure "sp_change_users_login". http://technet.microsoft.com/en-us/library/ms174378.aspx The Action that you most likely need is "Update_One". there are some examples at the bottom of that web page. HTH Craig Bryden - Please mark correct answers
January 22nd, 2011 3:58pm

Hi Ed, The question you had is "How to move databases between computers that are running SQL Server". In order to move databases from one server to another server, we need to Move the databases Transfer the logins and passwords Resolve ophhaned users Move jobs and alerts Change the sp_configure settings to match the previous system There is good article describes how to do so: http://support.microsoft.com/kb/314546 If you have any more questions, please feel free to ask. Thanks, Jin ChenJin Chen - MSFT
Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2011 3:59pm

Reza - Your suggestion is the one I went with. At my employer I mainly using SQL 2000. I am starting to use SQL 2005. I am disappointed to see that the Export Wizard in SQL 2005 seems nowhere as robust as the SQL 2000 was. I have looked around in SQL 2005 to try to find somthing that can allow the easy selection of many tables and have the choices that SQL 2000 had. I tried the new Export Wizard. It is very user unfriendly compared to the older SQL 2000. I looked into SSIS and I do not see something there that allows the movement of data from a lot of tables to another database. The problem with the export wizard of 2005 was that I had to go into each table and select that I want to delete all records in the target. So am I looking in the wrong places? Is it really there I just haven't found it? :) Thank you for your Help - EdEd
January 22nd, 2011 4:47pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics