<p>What is the best method to transfer data from sales table to sales history table in sql server 2005. sales history table will be used for reporting.</p>

[{'answer_id': 79668, 'author': 'Ricardo C', 'author_id': 232589, 'author_profile': 'https://Stackoverflow.com/users/232589', 'pm_score': 1, 'selected': False, 'text': '<p>Bulkcopy is fast and it will not use the transaction log. One batch run at the end of the day. </p>\n\n<p>Deleting the copied records from your production server is a different situation that needs to be planed on that server\'s maintenance approach/plans. Your reporting server solution should not interfere with or affect the production server.</p>\n\n<p>Keep in mind that your reporting server is not meant to be a backup of the data but rather a copy made exclusively for reporting purposes.</p>\n\n<p>Also check on the server settings of your reporting server to be on <a href="http://technet.microsoft.com/en-us/library/ms191164.aspx" rel="nofollow noreferrer">Simple recovery model</a>.</p>\n'}, {'answer_id': 79705, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 0, 'selected': False, 'text': '<p>Most solutions will require 2 steps;\n-copy the records from source to target\n-delete records from source.\nIt is essential that your source table have a primary key.</p>\n\n<p>The "best" method depends on a lot of things.<br>\nHow many records? \nIs this a production environment? \nWhat tools do you have?</p>\n'}, {'answer_id': 79786, 'author': 'Nat', 'author_id': 13813, 'author_profile': 'https://Stackoverflow.com/users/13813', 'pm_score': 0, 'selected': False, 'text': '<p>Unless you are moving a large amount of data, a simple stored procedure should do the trick. \nA <a href="http://msdn.microsoft.com/en-us/library/ms187910.aspx" rel="nofollow noreferrer">sql server job</a> can manage the timing of when to call the proc.</p>\n'}, {'answer_id': 79889, 'author': 'jason saldo', 'author_id': 1293, 'author_profile': 'https://Stackoverflow.com/users/1293', 'pm_score': 1, 'selected': False, 'text': '<p>Take a look at SSAS.  OLAP is built for reporting and is easy to query with tools like excel pivot tables.</p>\n'}, {'answer_id': 11977761, 'author': 'AtharvaI', 'author_id': 354502, 'author_profile': 'https://Stackoverflow.com/users/354502', 'pm_score': 0, 'selected': False, 'text': '<p>if you just want to move the data to another table, use BulkCopy/BulkInsert. if you want to build reporting I would suggest a BI solution such as MS Analysis Service (OLAP). </p>\n\n<p>It is difficult and in my opinion ugly to maintain two or more history/archive tables in the same database. For a reporting solution you will be considering all the tables for that piece of information anyway. History/Archive tables should only be used if you are going to put the data away and not touch it for a long period of time, ie. archive it away outside the operational DB.</p>\n'}]
['https://Stackoverflow.com/questions/79468', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/14752/']