Viewing 15 posts - 58,021 through 58,035 (of 59,067 total)
Must be a nasty copy'n'paste error... The code doesn't work as posted...
GO must be the only thing on a line...
Every /* must be match with an */...
...
However, I agree...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2006 at 9:18 pm
Ken,
Your solution was fine, as well... I was responding to Fintan who apparently didn't read either of your posts very well.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2006 at 6:26 pm
Look at the SELECT! That's where the meat of Ryan's example is...
Ryan's post was an example to demonstrate the method for using the "mon yyyy" format as a datetime that you...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2006 at 6:47 am
Understood... you're not really changing the column type... just making it so it won't take bad data. Most vendor apps can withstand this type of change even if they've made...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2006 at 6:29 am
Nice.....
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2006 at 6:50 pm
You can really tell that Time has had to deal with this before
I share Ryan's sentiment... nice job!
Gail, thanks for the feedback......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2006 at 6:36 pm
I always wait on "Very Urgent" requests like this that have such a simple basis... it usually means that someone is taking an SQL test as part of an interview and,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2006 at 11:05 am
Heh... what if there was nothing from yesterday, either? Peter's solution is good.
But, why is there even a need to check the date? Tomorrow's news will likely not happen today.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2006 at 10:55 am
Sorry, I don't know Neetal... I'm pretty much at a loss on this one...
Can anyone else help on this? I'm neither and sp_oa Ninja nor a mail ninja...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2006 at 10:52 am
If it was working before, then the devil is in the data...
What creates the IP address on the SMTP Server? If it's DHCP and someone rebooted it, it may...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2006 at 10:17 pm
Gail,
I know you said you checked, but try this on the table that produces the error...
SELECT *
FROM Test
WHERE AMOUNT LIKE '%[^0-9]%'
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2006 at 10:09 pm
Yes, it's possible...
EXEC Master.dbo.xp_CmdShell "DIR d:\path\*.trn,d:\path\*.bkp /s/b"
If you actually want to use the file names, create a table with a nice wide VARCHAR column and do this...
INSERT INTO yourtable (widevarcharcolname)
EXEC...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2006 at 6:57 am
I absolutely agree... for man-power scheduling purposes, ok... for simple reporting, doesn't matter.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2006 at 6:39 am
Here's another way to find what the day of the week is without regard to @@DateFirst...
SELECT DATENAME(dw,GETDATE())
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2006 at 6:37 am
Or, you could do this...
SET @variable = ISNULL(@variable,0)
... for inline code, you don't even need to change the value... just use the formula...
SELECT ISNULL(@variable,0)
FROM yada yada
... OR...
SELECT yada yada
FROM wgga...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2006 at 6:30 am
Viewing 15 posts - 58,021 through 58,035 (of 59,067 total)