Viewing 15 posts - 35,026 through 35,040 (of 59,099 total)
wolfkillj (2/14/2011)
Jeff Moden (2/14/2011)
Ok... the following function will pretty much blow the doors off of other splitter functions including some of my old ones.
WOW!!! That crash you just heard...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 7:45 pm
sql_butterfly (2/15/2011)
This is the update statement within the sproc which is getting stuck and creating deadlock (when run parallely in various sessions)
Update? Where's the code for the UPDATE? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 7:38 pm
Jeff Moden (2/15/2011)
sql_butterfly (2/15/2011)
Any help ?Did you make the corrections I suggested?
Sorry... missed the post where you said you made the changes.
I looked at the splitter function you posted and,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 7:36 pm
mister.magoo (2/15/2011)
konstantinos.christodoulakis (2/15/2011)
Jeff Moden (2/14/2011)
Why not validate and mark all the failures at once using set based SQL? Then you could actually create...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 7:27 pm
mea99sdp (2/14/2011)
my solution seem very slow, is there a quicker way to obtain the shift name?
Yes there is. 🙂 Don't do this in a scalar function. Inline code...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 6:26 pm
tt-615680 (2/15/2011)
Reports are run through out the day as well as bespoke queries which results for the server to run very slow.
There's a high probability that nothing you do to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 5:01 pm
mklein2 (2/15/2011)
Thank Phil.I have already use this function, and I forgot to think at this function
Just remember that a phone number can have no country code or a country code...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 4:49 pm
... and please remember that a view of two tables with no row level relationships WILL cause a CROSS JOIN where the number of rows in the view will be...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 4:41 pm
GSquared (2/15/2011)
;
WITH CTE
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 4:38 pm
dlatch (2/15/2011)
It struck me as throwing a bucket of dung at the wall (twice) and seeing what sticks. He said this is how they "always do it."
'
BWAA-HAAA!!!! And now...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 4:11 pm
POWER relies on a FLOAT conversion which, IIRC, has a maximum precision of 15 digits. Here's an article that demonstrates the problem for another function that does a FLOAT...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 4:08 pm
chintalagiriprakash (2/15/2011)
HiJeff
i placed query including output And how i need an output everything on my question u just look in to my first question ...
Regards
Prakash
Nope... the data in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 12:28 pm
timotech (2/15/2011)
Thanks for your reply, how do i use the FOR PATH XML?Thanks
Sorry. I'm at work right now and can't do a detailed example until I get home tonight....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 12:25 pm
sql_butterfly (2/15/2011)
Any help ?
Did you make the corrections I suggested?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 12:23 pm
GilaMonster (2/15/2011)
Jeff Moden (2/15/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2011 at 12:19 pm
Viewing 15 posts - 35,026 through 35,040 (of 59,099 total)