Viewing 15 posts - 50,026 through 50,040 (of 59,091 total)
I've never known hardware to be the solution to any performance problem... not ever.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2008 at 4:43 pm
On top of that, the SalesRepList column is TEXT instead of VARCHAR... it could probably be converted to VARCHAR quite easily.
Once converted, you can easily split the column with a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2008 at 12:13 pm
adi.cohen (6/15/2008)
Thanks!!the XML solution was very helpfull 🙂
So... are you using SQL Server 2000 or not?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2008 at 12:07 pm
What's wrong with a good ol' concatenation function that works in 2k and 2k5?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2008 at 12:06 pm
It would be far better to use something besides Word as your input GUI. Excel would be a better "poor man's" GUI than Word for this type of thing.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2008 at 9:32 am
Your sample data doesn't match your sample table. See the URL in my signature to get a better answer quicker...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2008 at 9:27 am
rbarryyoung (6/15/2008)
This is one way. Not the fastest, but not terrible, and easy to understand and remember:
Um... nope... a single update will update any given value once and only...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 15, 2008 at 9:23 am
Set up a script or proc that reads sysprocesses every 30 to 60 seconds to check for the presence of "Active" spids. For that matter, you could run sp_who2...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2008 at 9:58 pm
Like Steve said earlier, this brings up the subject of "What is right" and that's where most of the contention comes up. To me, "Right" not only means that...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2008 at 9:40 pm
yolip (6/14/2008)
I apply this sample into my existing cursor, but unfortunately it slows down my speed from 15 seconds to 19 seconds. it doesn't work as metioned.
That, my friend, is...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2008 at 9:26 pm
Matt Miller (6/14/2008)
In my mind, in order to BE effective, you have to be right.
Absolutely beauf! Couldn't have (and, obviously didn't) said it any better. I...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2008 at 9:23 pm
You know... Sergiy is right. We expect "perfect" from everyone except the people that write software. We're talking about leaving out the 10-20% for software... what would you...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2008 at 5:49 pm
Heh... I could probably live with leaving out 10-20% improvement... too bad it's never that low. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2008 at 5:37 pm
Which script?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2008 at 5:31 pm
I don't know, Steve... Good peoplem like yourself, keep saying that good enough is enough. That refactoring code should be carefully considered. That you need to get things...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2008 at 5:16 pm
Viewing 15 posts - 50,026 through 50,040 (of 59,091 total)