Search results for query: *

I appreciate all the help provided above - the end result is we are processing 5,000,000 records per loop, and we are getting 90 million updates per hour. The query literally takes about 2 hours - before it took more than 40 hours. The print command still puzzles me - at 1,000,000 in the...

Last year I went from Microsoft Access to SQL Server 2005. It was a big change - and I purchased three books that I continually pickup and reference: 1) Sams Teach Yourself Microsoft SQL Server T-SQL in 10 Minutes. ISBN-13: 978-0-672-32867-1 2) Microsoft SQL Server 2005 for Dummies ISBN...

I updated the query to the following: USE AROI DECLARE @TMin int; --sets the first record of the database DECLARE @TMax int; --sets the last record of the database DECLARE @Rmin int; --sets the first record of the loop DECLARE @Rmax int; --sets the last record of the loop -- Get the first...

There are several concerns when running these large updates - first is the maximum size of the log files I can create is 220GB, and on the last pass of this query, it grew to 210GB before I started the rollback. It took almost 45 hours to get to that point. By using a LOOP statement - it will...

I am processing massive updates to tables - usually between 150 million and 200 million rows updating. The queries can grind for 30-48 hours before finishing. I want to reduce processing time - will LOOP statements to select sub-sets of the data assist in performance? The first table has 168...