Oh wow. That's a first for me. He is right though. Almost any question can be answered by the suggestion to go and read...

It's like said before. It could be so many things. Especially with the indexes you have. I suspect page splits are going to be pretty expensive. So some inserts will...

Oh, and the ID column doesn't need to be included with the covering index since it's the clustered key. The key values in a clustered index are always available within...

This index, IX_StudentServices_StID_R_DU_PID_SeID_L_GS_FD_D_SC, and this index, Indx_StudentID, are basically the same because the leading edge, the first column is the same. You really don't need the second index.

That's not getting...

Excellent. When they're funny, they're really funny.

If it's just time, it could be contention, blocking, that made it run longer the second time than the third. It could be that the second time required a page...

Adding an index will allow the COUNT process to find something with fewer pages than the entire table. Otherwise, you have to do a table scan, every time, no options.

Please don't cross-post between the topics. Many of us read all the various groups and this just diffuses the conversation. Can I suggest that further comments go this thread:

http://www.sqlservercentral.com/Forums/Topic729538-357-1.aspx

I'd suggest books. First off, all the Inside SQL Server 2005 (or 2008) books are worth reading. Ross Mistry's book on 2008 Administration is good. Joe Sack's book on Transact-SQL...

It just sounds like a databse with two data files & two log files. Make sure, if you're restoring it to a new server, you get all four files into...

First, if you can post the actual execution plan instead of the estimated, it'll make a huge difference in trying to figure out what's going on.

Next, I'm not sure...

GSquared (6/4/2009)

---

One problem I've run into with char(1) for this is that some clever developer somewhere along the way inevitably wants to put T/F in a column that also has...

You can also use a CHAR(1). A little more flexibility than bit, but then it has a little more flexibility than bit.

ANSI_DEFAULTS

ANSI_NULLS

ANSI_PADDING

ANSI_WARNINGS

CONCAT_NULL_YIELDS_NULL

From MSDN

How old is the backup? Has more data been added to either database? Has either one had statistics updated or indexes rebuilt? Are you using identical parameters inside the queries...