Viewing 15 posts - 50,821 through 50,835 (of 59,091 total)
What's wrong with using the Profiler?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 6:36 pm
Something "like" this should do it...
IF Column1 LIKE '[0-9][0-9]-[A-Z][A-Z]-[0-9][0-9]-[0-9][0-9][0-9][0-9]'
BEGIN
---your code here---
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 6:34 pm
True NULLs frequently show up as "nothing" and you shouldn't change that. If you want to see the word 'NULL', then write a SELECT that changes null values to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 6:30 pm
Like this...
SELECT *
FROM (--==== Test data
SELECT '43161234' AS Value UNION ALL
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 6:24 pm
dfalso (5/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 5:40 pm
Understood.
You guys go ahead and call it whatever you want...that's the beauty of programming. I named it after the 2nd definition of "Tally" found here...
http://education.yahoo.com/reference/dictionary/entry/tally
... which says...
2.a. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 5:14 pm
I love testing... got any test code you'd like to share? Paging is always one of those PITA's that people (not you) have a hard time getting their arms...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 1:13 pm
Same thing applies, Lynn... let the developers do what they want in Dev... keep them out of QA, UAT, and Prod.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 1:04 pm
Matt Miller (5/1/2008)
speaking of dupes...methinks we've all been duped into continuing to beat up on this topic, since the OP is long gone...:)
Yep... gotta love it when the OP bails...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 1:02 pm
Heh... sorry about the "soapbox" coming up... 😀
The "best" way to do all of this is to not let dupes into production tables to begin with. Unknown data should...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 12:10 pm
John Mitchell (5/1/2008)
Or this one, which uses less string manipulation, but does contain dynamic SQL:
Nicley done but, be careful... get more than 8000 characters (about 16 rows in the example...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 11:59 am
Michael Valentine Jones (5/1/2008)
Jeff Moden (5/1/2008)
Michael Valentine Jones (5/1/2008)
It's probably better to avoid using a reserved word, like INDEX, for a table name.
Or "number" or "sequence" or... that's all part...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 11:50 am
RyanRandall (5/1/2008)
IIt's all much of a muchness really.
'zactly... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 9:27 am
And, yeah... you could call it "Numbers"... but I'm one of those old guys where the table name shouldn't be a plural... :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 9:18 am
Michael Valentine Jones (5/1/2008)
It's probably better to avoid using a reserved word, like INDEX, for a table name.
Or "number" or "sequence" or... that's all part of the reason why I...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 9:12 am
Viewing 15 posts - 50,821 through 50,835 (of 59,091 total)