Viewing 15 posts - 56,881 through 56,895 (of 59,101 total)
Uh... Don't know about anyone else, but I wouldn't use ISNUMERIC for this... case in point...
SELECT ISNUMERIC('13E5')
SELECT ISNUMERIC('13D5')
SELECT ISNUMERIC('13.5')
SELECT ISNUMERIC('13,5')
SELECT ISNUMERIC('$135')
etc... etc...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2007 at 4:56 pm
Don't need Case if there's always a space (ack...
I'm a poet and don't know it) ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2007 at 6:05 am
Actually, not quite true... you can "return [apparently] non-deterministic values" if you trick the heck out of it...
First, create a view that looks something like this...
CREATE VIEW GetNow
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2007 at 5:54 am
You must have a really old copy of BOL, Carl
Here's a copy of what BOL says about the decimal data type...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2007 at 8:55 pm
Hey Remi and Anders... nice tag team you guys made!
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2007 at 8:49 pm
Ummmm.... You might want to read up on what a "Table Alias" is... it'll make that code look a lot cleaner... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2007 at 8:48 pm
...forgot the divide example... you want THIS kind of crappy accuracy?
Tell me which company you're writing this for so I can make sure I...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2007 at 8:44 pm
I sure would like to know why you think MONEY gives incorrect results... 4 decimal places isn't enough? Maybe not for interest calcs and monthly payment calcs...
But David and...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2007 at 8:39 pm
If the CLR UDF's don't, firing "n" number of queries certainly may... especially when "n" number of queries are calling UDF's... sounds like lots and lots of RBAR (pronounce "ree-bar"...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2007 at 8:24 pm
What kind of error are you getting... you might also post your code so we can help more. And, don't forget, you must have "SA" privs to use it.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2007 at 8:20 pm
... and, BEST, you need to identify how table A and table B relate to each other... what would the join columns be?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2007 at 6:48 pm
Ummm.... take the ORDER BY out of the view... you should do the order by in procs that reference the view, not in the view itself.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2007 at 7:08 am
How 'bout the fact that BOL says "OFF" is the default?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2007 at 6:09 pm
Does SQL 2K5 WorkGroup have either BCP or OSQL? The reason I ask is that the cursor method will take a comparitively very long time... for every line you write to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2007 at 6:12 am
Thought I'd add one... see "M3"...
select
M1 = right(1000000+MyNumber,4) ,
M2 = right('0000'+convert(varchar(20),MyNumber),4),
M3 = REPLACE(STR(MyNumber,4),' ','0')
from
(
select MyNumber=1 union all
select 10 union all
select 44 union all
select 7777 union all
select 9999 union...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2007 at 5:38 am
Viewing 15 posts - 56,881 through 56,895 (of 59,101 total)