I found myself using one just the other day, and although it was by far the neatest and most readable option for the logic I was using, I still felt...

Google too (it's been a while since college, and theat's the only time I've really known all the names of things). Of course by now, the top hit on...

Paul - that's exactly what I did when BOL didn't quite give enough information to answer.

I agree with your view on the 2 point question; sorry for doubting you.

(In real...

There would have been less guesswork involved if the full error message had been given instead of just an extract:

Query processor could not produce a query plan because of the...

You don't even need the WHERE clause. I've just done an SSIS step where I needed a single row returned, but didn't care about the contents, so I used

SELECT...

If you don't think you have, the easiest way to check is to check the "Scan for Startup Procs" configuration setting. If this is False, then you don't have...

Are you doing the restore from SSMS rather than a query? When SSMS opens its restore window, it starts a session using your default database. If this is...

Sadly, my BOL diving didn't go deep enough. I got to here: http://msdn.microsoft.com/en-us/library/ms189275(SQL.100).aspx, which...

I'm obviously too suspicious. I thought of that,...

I'm confused as to why you would consider '1753' to be an invalid date (assuming we're using the Julian calendar).

Datetime datatype runs from 1st January 1753, and the implicit and...

You don't really avoid using cursors or loops - if you have a look inside sp_msforeachtable and sp_msforeach_worker, you'll see it uses them itself.

For me, the main reason for using...

If you don't mind using undocumented procedures, you can simplify it slightly by replacing all the loop stuff with:

exec sp_msforeachtable @command1='insert #TempTable exec sp_spaceused ''?'''

I also convert the "KB" values...

Are you sure you need an SSIS package?

Could you use something like this in T-SQL (the variable's not strictly necessary, just makes it easier to change):

DECLARE @batchSize INT

SET @batchSize=25000

WHILE 1=1

BEGIN

DELETE...

I have no idea why I put inner joins in there. In my head they were lefts. 🙂

As a starter, here's one way you could get the totals you want:

select a.conName, b.bTotal, c.cTotal

from #tableA a

inner join (select conID, SUM(Total) as bTotal from #tableB group by conID) b

on...