If you are looking at table partitioning then you have Enterprise Edition of SQL Server. If an 80GB table (or 5M inserts per day) is causing performance problems on Enterprise Edition...

First off make all your columns NOT NULL. It is inefficient to store NULLable datatypes when all rows will have data.

The simplest way to do this is with...

Go away Joe.

Randy, I can virtually guarantee you that a competent consultant could quickly find a myriad of misconfigurations, suboptimal infrastructure, poor mx, bad queries, BAD indexing, etc. etc. etc. A fair...

Microsoft's page has the following about putting things in master: "If you do, master must be backed up more frequently."

There is no reason for you to no do what you...

Just poke around and do things with various object and actions and lots of EF code will drop out. I'm sure you will notice the nvarchar(4000) parameter declarations. 

1) It is stupid to not backup master regularly.

2) You can protect against that by having a single script (or easy mechanism to run a bunch of scripts)...

Jeff, don't forget to add in LOCKING THE TABLE for potentially an extended period. This almost certainly needs to be batched into some number of rows per batch, using a...

That's pretty messed up. 

Do the queries that DO complete successfully begin with the same SELECT @@SPID;?

SSMS is a huge pile of HORRIBLY CODED ENTITY FRAMEWORK CRAP,...