Without more data, the main thing I can suggest is, make sure it's a covering index that you're using.

In other words, if there are columns in the Select clause that...

I've had false positives on that column. I haven't investigated why, but I've found stored procs that had no changes, but where the "last modified" in the system view...

I might take it one step further and, instead of a reporting table with a clustered index, I might use an indexed view. It would depend on how the...

I use trace logs and trigger-based auditing. (I even wrote articles about it for this site last summer.) I've found those to be quite adequate to my needs.

I...

In Control Panel, under Add/Remove Software, you have the option of installing more/less Windows features. You would add IIS through that.

I have to do this kind of thing all day every day (actually, I have automated procedures that do exactly this). Since I work for a direct mail company,...

I found some data about that error at:

http://sqlserver-qa.net/blogs/perftune/archive/2007/05/14/sql-server-has-encountered-occurrence-s-of-cachestore-flush-for-the-cachestore.aspx

I'm assuming you've already got the basics, like normalization and table design, from DB2, so the main thing for you will be learning the specific features of T-SQL, and the...

Matt Miller (12/3/2008)

---

GSquared (12/3/2008)

---

It won't matter as much in a Group By as it does in a Where, since the Where clause problem is table/index scans instead of seeks, and...

Have the first proc create a temp table. As each proc is called, insert your logging data into that same temp table (assuming they are all called in the...

skjoldtc (12/2/2008)

---

I have a question for the frequent posters? Do you spend you employer's time answering questions here or are you doing it on your own time. If on your...

Just save each part. That's easy enough.

Glad I could help. Well done on fixing it.

As has been mentioned already, I love working myself out of a job. I've just about done that with my current employer, and I'm just about ready to move...

It won't matter as much in a Group By as it does in a Where, since the Where clause problem is table/index scans instead of seeks, and that doesn't apply...