Comments on: A Fast Way to Update Large Amount of Data in SQL Server With Select Into Statement http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html Random thoughts and news by Andrew Chen and friends Thu, 09 Feb 2012 14:05:53 +0000 http://wordpress.org/?v=2.5 By: Michael Brönnimann http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-151491 Michael Brönnimann Tue, 23 Aug 2011 11:55:02 +0000 http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-151491 A free <b>Community Edition of SQL Parallel Boost</b> can be downloaded at <a href="http://sqlparallelboost.codeplex.com" rel="nofollow">CodePlex</a> :smile: A free Community Edition of SQL Parallel Boost can be downloaded at CodePlex

:smile:

]]> By: Tech Helper http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-137262 Tech Helper Tue, 10 May 2011 18:37:16 +0000 http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-137262 You will need to delete in stages for best results, see this thread for more on deleting large amounts of sql data.. :arrow: http://www.techhelpcentre.com/showthread.php?t=242889 You will need to delete in stages for best results, see this thread for more on deleting large amounts of sql data.. :arrow: http://www.techhelpcentre.com/showthread.php?t=242889

]]> By: Michael Brönnimann http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-136886 Michael Brönnimann Sat, 07 May 2011 11:02:04 +0000 http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-136886 Instead of going thru the INSERT and sp_rename path, which also requires to rebuild any other table constraints and indexes, you may consider executing a regular UPDATE with parallel execution... Parallelization for queries (SELECT) is covered quite well by the SQL engine itself, but when it comes to large volume data modifications (UPDATE, INSERT, DELETE), the standard engine does parallelize towards best use of all available resources (disk, multiple cpu-cores, etc.). Therefore you may have a look into the approach of SQL Parallel Boost at http://www.ibax.ch/-IBX-/plain.simpleimagetitletextlinklist.en.solutions.products.parallelboost/default.aspx This approach can also be used to execute multiple SQL statements in parallel. A purely SQL engine related parallelisation solution takes advantage of minimized complexity and has no 'external' components like SSIS involved, Furthermore it's the best performing solution regarding task splitting and synchronization, as it hasn't potential connection and communication overhead. The overall performance gain thru parallelisation with SQL Parallel Boost is up to 10 ! In case you don't wan't to rebuild your own solution, SQL Parallel Boost provides a self-contained pure T-SQL based solution, which can be easily embedded in existing applications and ETL process tasks. Instead of going thru the INSERT and sp_rename path, which also requires to rebuild any other table constraints and indexes, you may consider executing a regular UPDATE with parallel execution…

Parallelization for queries (SELECT) is covered quite well by the SQL engine itself, but when it comes to large volume data modifications (UPDATE, INSERT, DELETE), the standard engine does parallelize towards best use of all available resources (disk, multiple cpu-cores, etc.).

Therefore you may have a look into the approach of SQL Parallel Boost at
http://www.ibax.ch/-IBX-/plain.simpleimagetitletextlinklist.en.solutions.products.parallelboost/default.aspx

This approach can also be used to execute multiple SQL statements in parallel.

A purely SQL engine related parallelisation solution takes advantage of minimized complexity and has no ‘external’ components like SSIS involved, Furthermore it’s the best performing solution regarding task splitting and synchronization, as it hasn’t potential connection and communication overhead. The overall performance gain thru parallelisation with SQL Parallel Boost is up to 10 !

In case you don’t wan’t to rebuild your own solution, SQL Parallel Boost provides a self-contained pure T-SQL based solution, which can be easily embedded in existing applications and ETL process tasks.

]]> By: adam http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-69925 adam Fri, 11 Sep 2009 22:31:10 +0000 http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-69925 select into and insert into CAN be equivalent in speed. select into will create locks while determining the data structure though. for small datasets, insert into is less typing. for cases where you will need to keep locks to a minimum, you can do a select into where 1=0 and then an insert into. Allows you to not have to code out the table creation while getting everything structurally you need. select into and insert into CAN be equivalent in speed. select into will create locks while determining the data structure though. for small datasets, insert into is less typing. for cases where you will need to keep locks to a minimum, you can do a select into where 1=0 and then an insert into. Allows you to not have to code out the table creation while getting everything structurally you need.

]]> By: Andrew http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-23049 Andrew Wed, 16 Apr 2008 13:32:11 +0000 http://www.siusic.com/wphchen/a-fast-way-to-update-large-amount-of-data-in-sql-server-with-select-into-statement-112.html#comment-23049 That's probably true but I didn't have that observasion. If anyone can provide some input on what is the underlying difference between "select * into table from" and "insert into table select * from" it will be great. That’s probably true but I didn’t have that observasion. If anyone can provide some input on what is the underlying difference between “select * into table from” and “insert into table select * from” it will be great.

]]>