Viewing 15 posts - 35,641 through 35,655 (of 59,099 total)
I know this is an older post but could you post the fn_IntListToTbl, please? Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2010 at 4:34 pm
rasha.adel82 (12/19/2010)
Hi ,I belive Pivot which is a new TSQL 2005 feature can do it easily
Pivot is also quite a bit slower than a good ol' fashioned crosstab. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2010 at 4:06 pm
pankaj.nainu1 (12/19/2010)
I am facing some problem while updating a column through trigger.
I have a table User_Records with n number of columns, one of the column is SequenceNumber. When first time...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2010 at 12:07 pm
The Dixie Flatline (12/19/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2010 at 9:55 am
pdanes2 (12/19/2010)
I only looked at this briefly but I'd say the WHERE clause is totally unnecessary. Unless someone messed with the server-wide settings, NULLs won't join anyway.
Hmm, yes, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2010 at 9:44 am
The community is you. All of you out there that somehow join in reading blogs, writing blogs, attending events, volunteering and more. My life is better for getting the chance...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2010 at 7:08 pm
GSquared (12/17/2010)
Jack Corbett (12/17/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2010 at 6:57 pm
pdanes2 (12/18/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2010 at 6:51 pm
Ah! Now I remember. I haven't lost my mind after all! 😛
I was building an "interim step table" while converting a million row "Adjacency List" (Parent/Child model)...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2010 at 6:04 pm
Weeeelllll CRUD! I can't duplicate the problem I was having before. Yes, it's easy to duplicate the fact that the reads for a CTE will be twice as...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2010 at 5:12 pm
ALZDBA (12/17/2010)[hrYou should expect the column level correlated selects will produce RBAR behaviour. ( Read Jeff Modens articles on how to prevent that ! )
"It Depends". The joins used...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2010 at 8:26 pm
Heh... I use GETDATE() for several reasons but these are my favorites... It has fewer characters to type, I've used it forever, I don't believe in the myth of portability,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2010 at 7:14 pm
vinothraj (12/16/2010)
I've checked elapsing time for each of those and got approximate time is less for current_timestamp than getdate().Is current_timestamp better? i think so....
Please post the test code. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2010 at 7:08 pm
It sounds like a classic "connection leak" or a "memory leak" in the CLR's.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2010 at 7:00 pm
The Dixie Flatline (12/17/2010)
Note to Jeff Moden: It may not be "Nasty Fast" but it's "Wicked Quick"
Heh... too funny, Bob. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2010 at 6:57 pm
Viewing 15 posts - 35,641 through 35,655 (of 59,099 total)