Viewing 15 posts - 47,851 through 47,865 (of 59,095 total)
You bet. Thanks for the feedback.
Just remember... if you can't wedge a clustered index in there like I did, this solution will not work correctly.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 5:59 am
cdex3 (10/8/2008)
ID RecType PKIdentifier RecordData
1 01 acc00108 Text
2...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 5:50 am
JohnDBA (10/8/2008)
This solution is close to what I need, but I need to create groups. I cannot create groups with jbmRank. 🙁
I will read that article. Thank you...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2008 at 5:19 am
Ok... I borrowed some data and assume that you don't actually have a primary key... this should give you and idea...
--drop table #shuffle
DECLARE @NameCountPlus1 INT
SELECT @NameCountPlus1 = COUNT(*)+1...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 9:54 pm
If you haven't read the article that Matt listed, you really need to go back and read it so you understand why the following works... and it works at a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 9:52 pm
What is the primary key of the table?
Also, since this is your first post, you might want to take a look at the link in my signature below... folks will...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 7:34 pm
I remember... it's a pretty tough task because it's not just quotes that Sergiy has to worry about with the data he showed me. It's data from a "properly"...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 7:16 pm
Absolutely...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 6:37 pm
Thanks... I'll take a look.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 6:36 pm
Chris Morris (10/8/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 6:11 pm
ggraber (10/8/2008)
You don't have that kind of flexibility with...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 6:08 pm
ggraber (10/8/2008)
I just presented this concept at work using your split csv example.
I was just trying to think what other examples...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 6:01 pm
PIVOT would likely be slower than a good ol' Cross-Tab. See the following... peformance charts are near the end of the article...
http://www.sqlservercentral.com/articles/T-SQL/63681/
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 5:47 pm
If we knew more about the process that requires this action to occur, we might be able to help better. It's difficult to imagine a call recorder that would...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 6:28 am
Actually, why does this need to be done in a trigger? This sounds like a process specific to a particular proc and should probably on be done from a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2008 at 6:24 am
Viewing 15 posts - 47,851 through 47,865 (of 59,095 total)