UPDATE #tblUpload1

Set Section = tblSection.ID

FROM #tblUpload1

inner join tblSection

ON #tblUpload1.Section=tblSection.Description

Should do it.

MSDN.com has detailed data about what's changing between versions. What's new, what's removed, etc.

It probably wouldn't be that difficult to build something to do that in SSIS.

;with CTE (Row, Col1, Col2, Col3) as

(select row_number() over (partition by col1, col2, col3 order by col1),

col1, col2, col3

from dbo.Table)

delete from cte

where row >...

Technically, they both tell SQL Server to do the same thing.

The thing to keep in mind is that, most of the time, you aren't telling SQL Server how to do...

Is there any reason to not write a query (proc/view) in SQL, then use SSIS to export that?

I don't know of a way to make it use a different drive for that. May not be one.

The first point isn't a question. Can't answer that.

Second one, use Profiler and/or server traces. Find blocks/deadlocks, find long-running queries. Also use the system views to find...

Two questions to start with:

First: What type of database(s) are you dealing with? Are they OLTP (lots of updates, inserts, deletes) or OLAP (very few updates, deletes, large inserts...

What query?

Different CPU(s), different hardware, different server load, different data in tables. Lots of things could be the cause.

You can't defrag a table that doesn't have a clustered index. Simple as that.

I'm not sure what "SCCM 2007" is, but the error message is saying that there's a serious problem with your database and you'll probably have to recover it from a...

Is the XML file simply huge? That's what the error message seems to indicate to me.

They're all going to be in that business.

Why not install a copy of Dev Edition on a home PC? You mentioned you don't want to, but I'm curious, because...