Because it occurs before execution starts. The...

Make the index on column2 (which you haven't shown) covering. Whether that's a good idea overall depends on how expensive that key lookup is and how expensive the additional modifications...

Probably stale statistics. Try an UPDATE STATISTICS <table name> WITH FULLSCAN. If it works, schedule a job that runs the update stats on a regular basis against that table.

No, there isn't. SQL 2000 doesn't keep track of any of that, even 2005 onwards only tracks usage since the last restart.

What was the code that you tried?

By the way, you might want to do some reading on SQL Injection and why your code is a security vulnerability as written.

You need a representative workload for DTA to be even remotely accurate, so that's a trace file (or table, makes no difference) that recorded as much of a business cycle...

Just to give you an idea of the work involved in your request...

When I was still consulting I got a request to quote for consolidation of three SQL Servers into...

Yup, scoping means that the temp table will be dropped automatically as soon as the dynamic SQL finishes. Way around that is to create the temp table outside the dynamic...

Daily transaction log backups? That means that up to 24 hours data loss is acceptable, so restoring to 1PM should be fine.

If it's not fine, then that log backup...

Neeraj Dwivedi (12/17/2013)

---

Try this.

SELECT

B.name AS TableName

, C.name AS IndexName

, C.fill_factor AS IndexFillFactor

, D.rows AS RowsCount

, A.avg_fragmentation_in_percent

, A.page_count

FROM sys.dm_db_index_physical_stats(null,NULL,NULL,NULL,NULL) A

INNER JOIN sys.objects B

ON A.object_id = B.object_id

INNER JOIN sys.indexes C

ON B.object_id =...

David Knapp (12/17/2013)

---

I could not get this to work if the DB is running in SQL 2000 compatibility mode. I think for that the script needs to be changed a...

The latter...

You can change compatibility level up and down as much as you like. It's just a switch controlling how the query execution engine interprets some T-SQL constructs.

Sounds like a NOT EXISTS, but it's not going to be measurable difference in performance just from changing that.