Viewing 15 posts - 54,391 through 54,405 (of 59,072 total)
Check for triggers, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 11:31 pm
C'mon man... do your own homework... you haven't even tried...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 11:29 pm
Heh... ok... guess I'll get up on the soap box, then...
ALWAYS use the fastest, most effecient code possible... ALWAYS use comments to explain the code unless it's just too, too...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 7:07 pm
Jason certainly had the right idea... and this goes just a bit further for forcing a format... but it's not 100% bullet proof...
DECLARE @test-2 TABLE (SomeDate VARCHAR(20))
INSERT INTO...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 6:59 pm
I agree with Jason... I think ISDATE, by itself, is a very bad way to check for valid dates. For example, the following all return "1" using ISDATE...
[font="Courier New"]SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 5:55 pm
Any import will fail if someone has the sheet open... in my opinion, best way to do this is to make a macro on the spreadsheet to export the correct...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 1:22 pm
David,
"Dropping the time" should be done on the display side of things... not on the import side of things. Reason being is that the only way you can truly...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 1:19 pm
But I am still curious as to why my UDF didn't work.
Your UDF works... but think about it... what do you get when you concatenate a NULL with...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 9:09 am
Just a personal opinion...
I think you may be trying to do too much in a UDF. I think the UDF should do nothing but find the number you're looking...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 8:37 am
The picture of what you wanted in your first post is not visible.
Layout some text on the next post that depicts the format that you would like. Use the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2007 at 8:32 am
I'm thinking this is wrong...
SELECT * FROM IPGDB..SHPHST
WHERE SIDATE > '2007-10-16'
AND SIDATE <= '2007-10-17'
Should be...
SELECT * FROM IPGDB..SHPHST
WHERE SIDATE >= '2007-10-16'
AND SIDATE < '2007-10-17'
Other than that, your transaction is pretty...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2007 at 7:45 pm
Kenneth Wilhelmsson (10/26/2007)
SQL Server is very obedient and sorts exactly as asked to..
...if that wasn't exactly what one intended, is another matter..
The 'fault'...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2007 at 7:39 pm
How would you like to import 5 million rows in about a minute? Post, say, 100 rows of data as an attachment and I'll show you how to build...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2007 at 7:35 pm
Roger that...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2007 at 7:10 pm
bharani (10/23/2007)
ya, but my team want that to be an int value...
Your team is absolutely wrong... Peter Larson has a good viable solution... storing any date or time as other...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2007 at 5:38 pm
Viewing 15 posts - 54,391 through 54,405 (of 59,072 total)