Viewing 15 posts - 54,301 through 54,315 (of 59,098 total)
Ah... got it. Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 10:26 pm
You bet... thanks for the feedback. Gotta love those "3rd party vendors". 😛 Only reason I knew how to do this is because I had to fix one...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 10:11 pm
winston Smith (11/6/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 10:07 pm
Henry Omodara (11/6/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 10:00 pm
Not to over simplify too much... but why don't you just use CASE statements?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 9:56 pm
Ummm.... how does putting it into extended properties make it any more accurate than putting it in a header comment? Sure, I understand it make it more accessible, but...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 9:45 pm
The SSIS package should be able to check if incoming rows already exist previously, perform updates if there were changes on any columns, and insert a new row if data...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 9:43 pm
True enough... and nicely done. I was being a bit sarcastic because the OP didn't want to use a stored procedure... I went a bit overboard with a way...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 9:10 pm
Duplicate post...
http://www.sqlservercentral.com/Forums/Topic419299-266-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 9:02 pm
If you have a table that looks kinda like this called "yourtable"...
CREATE TABLE yourtable (ProductName VARCHAR(10), SubmissionID INT)
INSERT INTO yourtable
(ProductName,SubmissionID)
SELECT 'AAA',123 UNION ALL
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:59 pm
Heh... this reminds me of doing volumetric rotations in Calc II... instructor was busting our chops about how he could do immensely accurate calcs to calculate the amount of material...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:37 pm
Heh... yeah, and I absolutely agree... the "proper documentation" fairy got on my shoulder, again.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:28 pm
Sure it's easier... that's not the name of the game... name of the game is nearly-continuous availablity of the data... depending on the size of the table, you may have...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:25 pm
A really great way is to include some revision history in the header comments of the proc... you know... the same place where you identify what the proc does, what...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:18 pm
Do you mean that you need to drop the time before you compare? If so...
WHERE DATEDIFF(dd,Table1.TimeStamp1) = DATEDIFF(dd,Table2.TimeStamp2)
Do be aware that because you have column names in formulas, there...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2007 at 8:13 pm
Viewing 15 posts - 54,301 through 54,315 (of 59,098 total)