Viewing 15 posts - 54,436 through 54,450 (of 59,089 total)
Thanks for the feedback... I've not had the same nightmare with the file system as you, though. Maybe I've just been lucky, so far.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 8:11 pm
Susan Laing (10/23/2007)
CAST(
CASE WHEN ISDATE(SUBSTRING(params, PATINDEX('%[ImportDate=%', params)+13, 19) )...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 8:06 pm
Heh... dunno about anyone else, but as stated in my last... I'm just testing for duration comparisons of simple parallel methods, Ken... what are you going on about?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 7:59 pm
I'm not so worried about me reading into such questions... I'm more worried that someone will take the answer as the gospel and mess up their data when they actually...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 7:41 pm
By default, SQL Server is not case senstive... you would have had to setup case sensitity when you setup the server or made a change to the who server after...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 7:35 pm
Jeff your method is equisite as usual
Thank for the nice compliment, Adam...:blush:
Hopefully, Luissantos doesn't have a million rows...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 7:22 pm
You bet... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 7:13 pm
Heh... I like the "downtown" explanation better.
Light on = True... Light off = False... NULL = who the hell stole my lamp 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 7:11 pm
Heh... good... not my eyes... just time of day. Thanks, Matt.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 9:27 am
Ah... got it... Looked more like VBS. Not sure why folks don't just write real code... doesn't take any longer 😛
DECLARE @A INT --Defaults to NULL on...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 9:13 am
rockzcm (10/24/2007)
I agree.Null is an very interesting data type.
a=null
b=null
if a=b then 'Yes'
Else
'No'
You will expect to get No since you cannot compare two null values.
Even more interesting... the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 8:44 am
Sergiy (10/22/2007)
There was a typo in the formula.
Also I corrected small logical error in the code:
[Code]
IF OBJECT_ID('dbo.fnAddWeekdays_Sergiy','fn') IS NOT NULL
DROP FUNCTION dbo.fnAddWeekdays_Sergiy
GO
CREATE FUNCTION dbo.fnAddWeekdays_Sergiy...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 1:45 am
Peter Larsson (10/24/2007)
BUT... I am missing data from SQL Profiler regarding CPU/DURATION/READS and WRITES for the different methods used.
When I started out with SQL Server 2005 and PIVOT...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 1:30 am
VAIYDEYANATHAN.V.S (10/23/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2007 at 1:10 am
rog pike (10/23/2007)
rises to the level of a shot across the bow of a ship
whose course needs dire correction).
Exactly what...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 23, 2007 at 11:43 pm
Viewing 15 posts - 54,436 through 54,450 (of 59,089 total)