Hire a performance tuning professional to do a file IO and waitstats analysis to find out exactly what sql server is waiting on. Worst-performing-query analysis would be done too....

I am pretty certain that this entire process can be made SET based without a UDF (killer) nor the looping (extra killer), but it will take more time that a...

Does sound like a DTS problem. These can be a PITA to deal with, but there are online resources you can find on how to properly configure.

I also recommend...

chetanr.jain (8/24/2010)

---

@Ashish

Go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource..

open it on notepad and search your index name over here.

We cannot open the database File ( data or log) in a notepad or...

Deadlock troubleshooting and resolution:

http://blogs.msdn.com/bartd/archive/2006/09/09/Deadlock-Troubleshooting_2C00_-Part-1.aspx

Note there are 2 additional parts to this blog series.

You can also get a professional on board who could probably resolve the issue in a matter...

The most important things to do are file IO stall analysis and wait stats analysis. That will tell you what SQL Server is having an issue with, and that...

+1 for ola.hallengren.com!!!!

1) You should do it when it needs to be done. many variables to that answer.

2) Easiest and best way...

We need to have a much deeper discussion on data access patterns, etc to give GOOD advice here. But I would try RAID 1 for OS and tempdb, RAID...

1) buffer cache hit ratio 99+ but page life expectancy very low indicates lots of IO but the IO subsystem is keeping up (otherwise BCHR would be low due to...

MANY things could be at fault here: too little RAM, poor IO, missing indexes, bad data structures, bad code, out of date statistics, poor maintenance practices, etc,etc.

I...

I HIGHLY recommend the database maintenance stuff (FREE!!) from ola.hallengren.com. Learn to use that stuff and stay away from maintenance plans!!

One additional suggestion: load the data in UPPER case since you are burning sql server CPU cycles to do this on every output?

common culprits for large tlog files:

1) FULL recovery mode but not doing ANY tlog backups

2) leaving long running tranactions open even in SIMPLE mode. then committed transactions cannot be...

Steve Jones - Editor (8/17/2010)

---

While you can hint for some types of joins, or indexes, I'm not sure you can control join order. The optimizer looks at statistics, data sizes,...