Viewing 15 posts - 37,516 through 37,530 (of 59,072 total)
kscott-851323 (7/22/2010)
The client will send a flat file containing all the columns defined in the target table. For example, the target table will have 3 columns defined as...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 6:05 pm
Robb Melancon (7/22/2010)
Joe Celko (7/22/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 5:47 pm
This might be a case where a trigger is useful. Have the trigger update the "Total" table whenever there's a change in inventory.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 5:33 pm
Mike C (7/22/2010)
Jeff Moden (7/22/2010)
Mike C (7/22/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 4:38 pm
kscott-851323 (7/22/2010)
Unfortunately, I have do not have much control on what the client sends in the files, so the number of columns can change constantly. The Client can...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 4:28 pm
Eugene Elutin (7/22/2010)
Jeff Moden (7/20/2010)
...it would be interesting to have a simple race between the built in REPLACE (T-SQL) and a CLR.
In a simple race single T-SQL REPLACE outperforms CLR...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 4:23 pm
bteraberry (7/22/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 4:17 pm
You bet... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 4:14 pm
Eugene Elutin (7/21/2010)
Jeff Moden (7/21/2010)
...Don't you have a column in the table that contatins the date and time that a row was inserted?
It wouldn't help to track DELETE's...
No, but it...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 4:01 pm
peter-757102 (7/22/2010)
Jeff Moden (7/22/2010)
I've not tried this particular example but I'm pretty sure that you don't actually need the index hint when you use an ORDER BY to get the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 3:57 pm
Mike C (7/22/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 3:56 pm
Joe Celko (7/21/2010)
SUM(<expression>)
OVER (PARTITION BY ..
...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 3:50 pm
mzak (7/21/2010)
I figured Jeff would mention this shortly after I posted the requested T-SQL so I was anticipating it :-).
Nope... Wasn't even going to go there because I did understand...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 3:45 pm
mzak (7/21/2010)
SET ANSI_NULLS OFF
GO
SET QUOTED_IDENTIFIER OFF
GO
CREATE Function [dbo].[Distance] (
@Lat1 as decimal(18, 6),
@Long1 as decimal(18, 6),
@Lat2 as decimal(18, 6),
@Long2 as decimal(18, 6))
Returns decimal(18, 6)...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 3:41 pm
bryan.duchesne (7/21/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2010 at 3:31 pm
Viewing 15 posts - 37,516 through 37,530 (of 59,072 total)