You need to define temporary...

you can always create an index, use it and then drop it.

Assuming an ETL job. I'd just enable/disable it so that I don't have to...

Michael Valentine Jones (10/28/2010)

---

Ninja's_RGR'us (10/28/2010)

---

Michael Valentine Jones (10/28/2010)

---

Ninja's_RGR'us (10/28/2010)

---

Michael Valentine Jones (10/28/2010)

---

Ken McKelvey (10/28/2010)

---

While snapshot isolation can be very useful, you should google 'write skew anomolies', check your code and...

Michael Valentine Jones (10/28/2010)

---

Ninja's_RGR'us (10/28/2010)

---

Michael Valentine Jones (10/28/2010)

---

Ken McKelvey (10/28/2010)

---

While snapshot isolation can be very useful, you should google 'write skew anomolies', check your code and do a lot of...

Michael Valentine Jones (10/28/2010)

---

SQL Server handles this...

That's my main concern. I'm supporting...

Lynn Pettis (10/28/2010)

---

The delimited split function linked above is not necessarily the best, it is loop based.

Do a search of this site for delimited split. I know I have...

http://www.sqlservercentral.com/scripts/Miscellaneous/30225/%5B/url%5D

Michael Valentine Jones (10/28/2010)

---

Have you verified you are using the normal read committed isolation level for both transactions?

Have you tried setting your database to use row-version isolation?

ALTER DATABASE MyDatabase SET...

Are both databases, or even all 3 databases on the same drives?

Do you separate log files from data files on different drives?

Do you have enough ram to run this process?

Unless there was a miscommunication on the specs.

Maybe the consultant wanted to add a new archive server because the current prod server is near capacity. In which case, then...

Not if the next time your run the proc, you use parameters...

What have you tried in there? I've never seen that fail so far?

krypto69 (10/25/2010)

---

I flushed the cache and re-ran the proc using same parameters..I can't make it run slowly on my stage server...I tried changing params and no matter which I choose...

I'm out of ideas at this point... I'll call in reinforcement.

Yes. Or more to the point, the wrong compiled plan is generated when using those parameters.

Assuming you saved the correct plan. Flush the proc cache from your test...