Viewing 15 posts - 38,266 through 38,280 (of 59,098 total)
Duplicate post... please see the following for another answer. THIS is why you shouldn't duplicate posts, folks...
http://www.sqlservercentral.com/Forums/Topic926260-149-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2010 at 11:55 am
Nick-260698 (5/21/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2010 at 11:49 am
Atif Sheikh (5/21/2010)
Anamika (5/21/2010)
Hi,Thanks for the inputs. both are working fine
thanks,
regards,
Ami
If the comma separated list is as long as 1000s of list items, it would be better to with tally...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2010 at 11:43 am
SELECT CAST(ServerName [font="Arial Black"]AS[/font] varchar(15)) as Server,
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2010 at 11:39 am
Heh... It certainly "depends" but try rebuilding indexes without a clustered index and see what happens. Keep in mind that indexes also "split" except they frequently do so by...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2010 at 11:29 am
Heh... ol' BitBucket beat me to it. See the link he refers you to because there are many ways of doing what you ask. Without data expressed in...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2010 at 11:23 am
I've never heard of that classic problem before.
The classic "how many times did the machine turn on or off" problem is usually accompanied by data that looks like the result...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2010 at 10:58 am
BSavoie (5/21/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2010 at 9:53 am
Here you go... as usual, the details are in the comments...
--===== Original test data setup from the post. This is NOT a part of the solution.
DECLARE @GuestData TABLE (...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2010 at 10:16 pm
Heh... rookie mistake on my part. I don't normally do SAVEs of code I'm working on for the forum because it normally just doesn't take that long and, if...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2010 at 8:54 pm
Heh... this whole thread is proof postive that one picture is worth a thousand words. As soon as I saw the pattern in the data you posted with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2010 at 6:48 pm
Just to add my two cents... I loved this article. It's well written, the code is formatted for easy readability. Topics were exposed in the correct order. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2010 at 12:17 pm
shaytoder (5/20/2010)
my mistake,for some reason i thought this approach will use seeks and not scans,
but now i tried it again, and i see scans.
sorry...:blush:
That's been the common problem throughout this...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2010 at 12:06 pm
Heh... just had to post back before I went to work. There's a trick that uses the difference between two different partitions used while creating ROW_NUMBER that might take...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2010 at 8:23 am
That's exactly what I had in mind. I'll try to get to this after work tonight.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2010 at 8:15 am
Viewing 15 posts - 38,266 through 38,280 (of 59,098 total)