Viewing 15 posts - 49,201 through 49,215 (of 59,099 total)
Heh... I feel the same... but I said "Today, just this one day, I shall not rant." 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 12:08 pm
karthikeyan (7/15/2008)
use distinct keyword
Let's see how you would do that, Karthik... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 8:55 am
I know disk space is relatively cheap... I just can't bring myself to suffer the overhead of storing XML in a database anywhere except a temporary staging table. With...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 7:06 am
paulhunter (7/15/2008)
In the .NET world you don't grant access to the internal code and data structures except thru properties and methods, so don't treat your database differently.
THAT is one of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2008 at 7:01 am
After you fix the updates and try the run (please let me know how that goes) again, then next thing I'd try to do is get rid of the While...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 10:11 pm
Yep... I found that undocumented alias form of update, too. While it seems to work quite well, you may not want to take a chance on it...
[font="Courier New"]...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 10:00 pm
Riga,
I'm still looking at the code but I did find a problem that's prevalent throughout the code where there are updates...
See anything wrong with the following code?
[font="Courier New"]-- Update all...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 9:51 pm
I think you're importing directly to the final table... why not import into a staging table and then you can do some validations and trimming before the data goes into...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 5:22 pm
Ummmm, so convert the result to a Bit datatype... all that is being returned are 1's and 0's... no -1's...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 2:23 pm
Just curious... the SIGN method with the subtraction from the ABS seems to work just fine as a negative number detector...
DECLARE @v-2 INT
SET @v-2 = -10
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 2:17 pm
Do you still have the code for it?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 1:55 pm
GilaMonster (7/14/2008)
Actually, I did suggest ISNumeric, with the warning that it's not perfect. Does your like allow for - and .?
No... but those can easily be added while excluding a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 8:00 am
You mean withing T-SQL? Sure... import the file... delete the desired rows... export the file. You could also write some VBS using the System File Object to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 7:57 am
First, it would be a great help if you'd take a little time to post your data in a more readibly usable format so that we can actually write a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 6:51 am
... heh... and before anyone even thinks of suggesting ISNUMERIC, try this...
SELECT ISNUMERIC('$1000') UNION ALL
SELECT ISNUMERIC('1,000') UNION ALL
SELECT ISNUMERIC('3d2') UNION ALL
SELECT ISNUMERIC('2e3')
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2008 at 6:46 am
Viewing 15 posts - 49,201 through 49,215 (of 59,099 total)