>> 1. Is there a pattern to the ID list, or is it just a random blast of IDs?

> Random.

Shoot.  Well, there goes that idea...

> Are there any obvious...

The primary reason to send a recordset from a client to the server is if the client has modified the recordset.

In your case, it appears you're performing additional queries against...

You can never be too rich, too thin, or have too much free data and log space.

If you get rid of the GROUP BY, you must also get rid of the SUM() (This is if you plan on using the detail in your report.  Otherwise, leave...

That COMPUTE BY clause splits your results up into lots of tiny, independant resultsets, each divided by an additional independant resultset with your COMPUTE BY results for the preceeding data resultset. ...

1. Is there a pattern to the ID list, or is it just a random blast of IDs?  If there's some method to the ID madness, then there should be...

Which edition of SQL Server 2005?

Enterprise and Developer Editions are good to 50 named instances per server.

-Eddie

Yup, the auto-growth is your problem.  Growing database files is disk-intensive, and is only happens when the space is needed, which is during writes.  In your case, it appears to...

SELECT CASE WHEN @checked IN ('Y', 'True',
Eddie Wuerch
MCM: SQL
 

IIRC, there are few topics in 2072A (the MS 5-day SQL Server admin class available at most training centers) that don't make the trip to SQL Server 2005.  There are...

The restored database will use the original file sizes.

DBCC SHRINKFILE is the way to go.

I'd advise taking a full backup first, expanding the log file considerably and taking a log...

Ensure that the constraints are being created using WITH CHECK instead of WITH NOCHECK.

You can see how this affects your sample code by doing the following:

1.  Run your sample above...

1.  Snapshot reporting refers to read-only access of database snapshots created on a mirror server (SQL Server 2005 Enterprise Edition).  Mirrors and snapshots are new to SQL 2k5.  The scenario...

The key part is that when the CHECK constraints are created, they perform the 'check existing data on creation' step.  If you build them with EM, that isn't done by...

That 'touch' is part of normal query resolution: the table schema is validated during parsing - which occurs before the WHERE clause is hit.  The table data is not queried.  Thus...