Great article.  Nice to see a not so SQL-intensive article, but still showing how SQL can be used in this context.  Good stuff 🙂

I've just started coding my first asp.net app and I'm glad to see that the approach I've taken matches the 'right answer' from the article!

Thanks for the info about there being no technical reason.

As for your other questions, if there is a standard in place then alterations to a table must conform to that...

I'm not Scottish, I just say 'aye' a lot.

I agree with your observations regarding the order of PK fields, especially being able to see at-a-glance the correct order for a...

Aye, that's the approach I used to take.  It just seems 'right' to have the PK first.

However, I am wondering if there is a technical reason - performance perhaps - ...

It may need running during the day if it fails at night.

Any other ideas as to why my current approach struggles to work using a Transaction?

There are 3 parts to...

Ok, stop trying to scare me!

Hey, I'm not ignoring what you are saying, but the least I can do is try it out, right?

Thanks for the tips, guys.

The job will (generally) be running at a time when no users are on the system.

I'll look into the 'Select...Into' approach.

🙂

Recovery as in rolling back a transaction?  Is 'Select...Into' a quicker method than 'Insert...Into'?

Anyone else have trouble with Transactions like this?  Surely, SQL can handle Transactions with this many inserts/deletes?

Maybe it can't and maybe a re-design is required.  However, I'd rather find a...

Depending on the load (whether it's a net-change load or a full load) I can be deleting anything from 1 to the full 1.5 million.  Good tip about Truncate, especially...

Good stuff - I've been wondering how that was going to work.

Oh my, another question with a stupid answer

I do check for @@Error after Insert/Update statements, it's just missing from here for brevity.  If there are any errors, then I issue a rollback.

I can't provide the data I...