With respect to your question about how well a 2 billion row table will perform, the answer is "great" unless you do a poor job of designing the database and...

A common error in estimating something (the required size of a database, new product sales, world population, etc.) is to take a series of worst-case or best-case values and then...

As a database designer/developer one of the most difficult things to do is to differentiate between what the customer/manager SAYS you need to do and what the product/business REALLY needs...

I find it interesting how many different ways we can find to solve a problem using T-SQL. Here is another way to strip-off the time and just return the...

I believe your UPSERT analysis is interesting, but too simplistic for 2 major reasons:

1. the effect of locks (UPDATE uses a more restrictive lock than IF EXISTS)

...

When you say you ran it manually does that mean you ran it manually from your box or you ran it manually from the SQL Server box?  I strongly suspect...

Try this:

SELECT RIC,COUNT(*) as myCount,

       SUM(CASE WHEN compliant75pctRule = 'T'         THEN   1 ELSE 0 END) AS [Compliant],

       SUM(CASE WHEN compliant75pctRule IN ('T', 'F') THEN...

After you build your @SQL string you try to execute it by saying:

exec @SQL

but you need to enclose the @SQL variable in parentheses like you do when you create the...