Sure, it's a common table expression. It's new in 2005. They function similar to derived tables, but can be referenced multiple times in a give procedure and, most importantly for...

And the recursive section of BOL has an example doing almost exactly what is being requested here. You ought to be able to take the example & make it...

We took a script from SQL Server Central that checked fragmentation and then decided whether or not to reindex or defragment (great script, used it for years, I'm not sure...

Oops. Did a bit more testing & found you need to add this at the end:

OPTION(MAXRECURSION 0);

Or you could...

No promises on performance but:

DECLARE

@BeginDt DATETIME;

DECLARE @EndDt DATETIME;

SET

@BeginDt =

I had to meet a similar need. We figured out that there were only a few constants. So, instead of trying to design a storage engine to get at data...

100% agreement with everything you said and thank you for saying it. Situational awareness has to extend past one's self. If something looks bad, it probably is. Do something about...

I'd move this kind of processing into SSIS. You've really stepped outside what TSQL is meant to do with all the file I/O. You'll probably get the same or better...

Thank you. Yes, that is on the list as a possibility. I'm just trying to explore the space and I'm not finding much in the way of documented approaches.

True, and it's something I'm looking into, but it makes me even more nervous. As the article you link to states, if the app isn't processing this information as fast...

That would eliminate any chance of holding locks, but it will put more of a load on tempdb since table variables are stored there.

I'm not really looking to radically...

I doubt this will give you everything you might need, but it will certainly get you started. These are Microsoft's Best Practices as implemented by their own consultants.

http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/default.mspx

We probably could use BCP and realize some performance improvements, definately. However, we're finding the performance is more than adequate, we've got it in Production as well as having tested...

From this, you should try adding an index to the temp table, [#ProducedHour]. The first one I'd try, and you will need to test anything you do, would be to...

#6Df65D3E is probably a statistic added to one of the tables because an index is needed for the query you're running and that index isn't there. The worktables are usually...