Viewing 15 posts - 58,726 through 58,740 (of 59,067 total)
Bull2000,
If you use the concatenate method using the TAB character (CHAR(9) in code) instead of a comma as a delimiter, the output might just cut&paste into Excel with no other...
--Jeff Moden
Change is inevitable... Change for the better is not.
Cory...
This works the way you want... leading zeros and mm/dd/yyyy format intact...
DECLARE @Date VARCHAR(30)
SET @Date = '2/3/2005'
SELECT CONVERT(VARCHAR(10),CONVERT(DATETIME,@Date),101)
----------
02/03/2005
(1 row(s) affected)
--Jeff Moden
Change is inevitable... Change for the better is not.
The log file probably grew for a pretty good reason. If you shrink it and it decides to grow again, especially if the growth size is small or is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
Try this, instead...
"select boy + REPLACE(STR(age,7,4),' ','') + ' is years old'
--Jeff Moden
Change is inevitable... Change for the better is not.
If it truly is a "DateTime" column, it just doesn't matter what format you store it in so long as it is one recognized by SQL. It will have...
--Jeff Moden
Change is inevitable... Change for the better is not.
If it truly is a "DateTime" column, it just doesn't matter what format you store it in so long as it is one recognized by SQL. It will have the...
--Jeff Moden
Change is inevitable... Change for the better is not.
Not trying to be difficult here... hex doesn't normally work quite the way you described so could you post an example of the hex number and what the expected outcome...
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 15 posts - 58,726 through 58,740 (of 59,067 total)