Just for kicks I would update the MDAC's, you can get the latest from MS website.

Also, this may help - http://support.microsoft.com/default.aspx?scid=kb;en-us;812817

Are you able to register with a different known-good SQL account?

There are other cooler ways to do this but the fastest way might be to do a select distinct (those 3 columns) into a second table, dump the original table...

Just so I understand, did you replace the machine that SQL server was on? Or just the client machines?

My vote would be the first one, big difference in processing between those two, maybe these links would help:

http://www.sql-server-performance.com/q&a2.asp

http://www.sql-server-performance.com/performance_monitor_counters.asp

http://www.sql-server-performance.com/fixing_bottlenecks.asp

http://www.sql-server-performance.com/sql_server_performance_audit3.asp

Forgot the year, you could group by datepart(yy,dt) as well and include it in your select

select datepart(mm,dt) as Month,max(datepart(dd,dt)) as MaxDay

from table

group by datepart(mm,dt)

BOL has examples for almost every SQL keyword that SQL server supports. So, yes, BOL would be excellent to see working examples of T-SQL code. That second URL lists some...

THis page may help - http://www.sqldts.com/?293,1

I was suggesting you use SQL tasks in DTS to run the scripts to add IDENTITY columns and alter the tables to make PK's...

1) suser_sname() may help

See these resources

http://aspfaq.com/show.asp?id=2496

http://vyaskn.tripod.com/tracking_sql_statements_by_triggers.htm

http://www.nigelrivett.net/AuditTrailTrigger.html

http://archive.devx.com/dbzone/articles/sh0902/sh0902-3.asp

http://www.standardreporting.net/survival/view.aspx?_@id=53431

HTH

Get BOL for free - http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en

More resources here - http://www.aspfaq.com/show.asp?id=2423

Recommend BOL too - http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en

Frank, the clustered index is part of the non-clustered index, it doesn't touch the clustered table/index if the query involves ONLY the clustered key and any NCI'ed column. It doesn't...

I agree with Colin, best way to test your performance is to use the command "set statistics IO on" and watch your logical IO

1) NOLOCK is a locking hint you can use to avoid contention in waiting for exclusive locks to finish. NOLOCK will create a non-schema verified lock which means you could...