Viewing 15 posts - 49,186 through 49,200 (of 59,093 total)
karthikeyan (7/16/2008)
Jeff,how about my code ?
What size column do you thing NAME = '' will make? Also, look at the update... which NAME shall it use to do the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2008 at 8:40 am
RyanRandall (7/14/2008)
update #TEST set Descr = replace(replace(replace(Descr, ' ', '¬ '), ' ¬', ''), '¬', '') where Descr like '% %'
(Where...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2008 at 8:07 am
Ok... now that I've had a bit of coffee... 😛
In the original problem posted, San didn't care about which name was returned so just use the MIN or Max name...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2008 at 7:37 am
Dugi (7/16/2008)
Hi Jeff!Your code here just selecting and ordering asc the data inside the table it doesn't do any elimination of duplicate records!
Can you explain little bit this!
Dugi
I believe that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2008 at 7:17 am
Dugi (7/16/2008)
Hi Jeff!Your code here just selecting and ordering asc the data inside the table it doesn't do any elimination of duplicate records!
Can you explain little bit this!
Dugi
Heh... Sure! ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2008 at 7:15 am
I wouldn't recommend that way... it has a While loop in it and a couple of other performance related problems. Try the following, please... it also explains how it...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 11:45 pm
There are a couple of ways... I believe the fastest for large data sets in SQL Server 2000 would be in the following...
http://www.sqlservercentral.com/articles/Advanced+Querying/61716/
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 11:39 pm
riga1966 (7/15/2008)
I think you are right.
I replaced UPDATE code and ran it.
But it now gets stuck inside a loop.
I run this SP a a script. I put lots of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 1:45 pm
Heh... you guys are missing the real problem! 😉 The real problem is why does the OP NOT care about which data is returned? If you don't care,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 12:12 pm
Heh... I feel the same... but I said "Today, just this one day, I shall not rant." 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 12:08 pm
karthikeyan (7/15/2008)
use distinct keyword
Let's see how you would do that, Karthik... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 8:55 am
I know disk space is relatively cheap... I just can't bring myself to suffer the overhead of storing XML in a database anywhere except a temporary staging table. With...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 7:06 am
paulhunter (7/15/2008)
In the .NET world you don't grant access to the internal code and data structures except thru properties and methods, so don't treat your database differently.
THAT is one of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 7:01 am
After you fix the updates and try the run (please let me know how that goes) again, then next thing I'd try to do is get rid of the While...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 10:11 pm
Yep... I found that undocumented alias form of update, too. While it seems to work quite well, you may not want to take a chance on it...
[font="Courier New"]...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 10:00 pm
Viewing 15 posts - 49,186 through 49,200 (of 59,093 total)