Viewing 15 posts - 50,986 through 51,000 (of 59,098 total)
karthikeyan (4/25/2008)
Adrian,You are correct. But i don't have the permission to create functions. Can you provide some other alternate ways ?
You could either ask for the privs or get the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2008 at 6:57 am
MarkusB (4/25/2008)
The most simple option would be using LIKESELECT myvarcharCol from mytable
WHERE myvarcharCol LIKE '%project%'
Another option would be using the PATINDEX function
SELECT myvarcharCol from mytable
WHERE PATINDEX('project',myvarcharCol) > 0
Try either of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2008 at 6:55 am
Gary,
The spaces you're getting is probably because of the data or datatype... For example, are you using CHAR or VARCHAR in the existing table? Are there trailing spaces in...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2008 at 6:34 am
rbarryyoung (4/24/2008)
Jeff Moden (4/24/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2008 at 6:26 am
I agree that there're a lot of things, like this conversion, that should be done in the GUI instead of SQL Server. Displaying commas in dollar amounts and formatting...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2008 at 6:20 am
I'm sorry... my bad... not enough coffee. I thought you wanted to know what the "N" was (as most frequetly do) and didn't read the rest of the WHERE...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2008 at 7:47 am
My appologies... I missed the fact that this is for display purposes...
You don't need a TempTable nor any form of dynamic SQL for this in SQL 2005... this will do...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2008 at 7:35 am
Sorry for not getting back to this sooner... Barry went in the same direction that I would have. (Thanks for the honorable mention in the code, Barry :))
Karthick, look around...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2008 at 7:22 am
Heh... sorry Gus, I took it the wrong way... thought for sure it was directed at me and didn't understand why especially since you know me pretty well... thank you...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2008 at 7:16 am
Good explanations, Gus.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2008 at 7:09 am
Mahesh Bote (4/23/2008)
No cure needed... they automatically drop at the end of the proc (poet and don't know it, too!)
Thanks Jeff for updating me. I was under impression...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2008 at 6:53 am
John Mitchell (4/23/2008)
You can avoid the "speed at all cost" methodology if you want... but I'd suggest that you haven't and you won't. Considering all that you've written about...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2008 at 6:47 am
Wanna tell me what's really going on? This code has errors in it in the form of variables that were never declared. That means this code doesn't take...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2008 at 6:36 am
Heh... that's a mess, huh? And now, you understand why properly documented code and properly named columns/tables are so valuable. 😛
I'll take a look, Karthick...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2008 at 6:12 am
vyas (4/21/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2008 at 12:07 am
Viewing 15 posts - 50,986 through 51,000 (of 59,098 total)