ScottPletcher (4/4/2013)

---

It sounded like one of those types of processes, where you basically just need a temporary "cache" of results / report. Typically those are easy enough for a...

Lowell (4/4/2013)

---

rajarshi_ghosh_05 (4/4/2013)

---

{snip}

No. We dont bother about the temp table data not if anything happens like network failure or server restart or user system restart! We dont have to preserve...

Lynn Pettis (4/4/2013)

---

ScottPletcher (4/4/2013)

---

Lynn Pettis (4/4/2013)

---

ScottPletcher (4/1/2013)

---

sharky (3/31/2013)

---

Lynn Pettis (3/29/2013)

---

SQLRNNR (3/29/2013)

---

Lynn Pettis (3/29/2013)

---

ScottPletcher (3/29/2013)

---

The advantage to tempdb is that there is less overhead writing data there since SQL "knows" it...

DiverKas (4/2/2013)

---

rajarshi_ghosh_05 (4/2/2013)

---

Guys, No luck. DBAs are not going to give me the permission to create table in tempdb so I come up with an idea to put both updlock...

Guys, No luck. DBAs are not going to give me the permission to create table in tempdb so I come up with an idea to put both updlock and holdlock...

That's true but there are several process...

Great idea!!!:w00t: This should works for me!! i just tried a little bit testing on this and it works!! .... Will post u the details after i actually implemented it..

Thanks...

The highest time to keep the table alive is 120min.

Is it possible to keep the table alive by locking it or anything else?

Actually i am importing csv file in the database through sp. the temp table is required to keep the validation error messages. When user wants to see the error messages...