Heh... what an idea... maybe I'll title it "Porkslinger: Have Chops, Will Travel." 😛

... and, if you write it correctly, it will also do just one "record" correctly, as well.

Two set based "passes", if needed, will still be light years faster than nested loops.

I'm "old school", too, but I sure don't mind being called "Jeff" on these forums. ...

dr_csharp (10/7/2008)

---

thanks jack . i do this :

CREATE TRIGGER test ON CallRecorder

FOR INSERT

AS

DECLARE @RecId INT;

DECLARE @BeginTime NVARCHAR(8);

SELECT @RecId=RecId,@BeginTime=BeginTime FROM Inserted

set @BeginTime=substring(@BeginTime,1,3);

Update CallRecorder

...

GilaMonster (10/7/2008)

---

Jeff Moden (10/7/2008)

---

the limit on the number of indexes for a table is much less than that. (Teach a person to fish) Lookup "Maximum Capacity Specifications" in Books...

J (10/7/2008)

---

Rats !

Another application where I was dead sure the only way to do it was a double set of cursors: calculating the FIFO value of an inventory.

Outer loop: items...

Actually, in SQL Server 2000, there are places where...

Oh yeah... almost forgot... you could also use UNPIVOT... look it up. I don't use it... I normally do it the way you did it.

The way you did it is fine, Karthik... only change I would make is to change all the UNION's into UNION ALL for performance and data integrity reasons. UNION...

Dugi (10/7/2008)

---

Jeff Moden (10/7/2008)

---

I've used it for "cleaning" data... you know... remove all numbers, remove everything but the numbers, remove special characters, remove adjacent multiple spaces (although there are better...

This type of concatenation is usually a bad idea especially if your intent is to store the result somewhere in the database as permanent data (not that you are, but...

tendayit (10/7/2008)

---

Hi,

I tested the modified procedure and it is better than the one i posted on the site. Thank you very much. I came across something this morning that i...

What Gail means is that there is no reason to use a cursor to do a "Cross Tab" report. Now, I'm not going to troubleshoot the size stored procedure...

You can always use SET ROWCOUNT 1 and then do the delete. Don't forget to set the rowcount back to 0.

It does, however, show the fundamental flaw that others...

I've used it for "cleaning" data... you know... remove all numbers, remove everything but the numbers, remove special characters, remove adjacent multiple spaces (although there are better ways to do...