Viewing 15 posts - 556 through 570 (of 595 total)
Sounds more like you need a few derived columns rather than a conditional spit. You could then take the parts of the string that you need using the SUBSTRING and...
June 25, 2013 at 7:25 am
Although MERGE isn't available in 2005 you can still replicate it to a decent degree. See here for some links.
Since you're not letting on what type of load this...
May 16, 2013 at 6:10 am
The OLEDB command component in SSIS is a row by row transformation - I'm not surprised it's slow. If you must update changing rows, then consider using a MERGE in...
May 16, 2013 at 4:14 am
What method are you using to update the rows (in your original solution)? Is this a Data Warehouse? What is the size of the table?
May 16, 2013 at 3:33 am
No problem, happy to help.
Ranking functions are described here: http://msdn.microsoft.com/en-us/library/ms189798.aspx
They're quite handy 🙂
November 14, 2012 at 8:15 am
If you don't mind which code it is then something like
WITH Cte AS
(SELECT ref_id,
cus_id,
code,
amt,
ROW_NUMBER() OVER(PARTITION BY cus_id ORDER BY amt DESC) AS Rank
FROM
z_temp)
SELECT Code, count(*) FROM cte WHERE...
November 14, 2012 at 7:09 am
I'm happy to help 🙂
There are two screens attached here (too big for one!)
You'll notice something that I missed from my original description. If it's a new business year...
September 13, 2012 at 4:14 am
There are a few ways this can be achieved, depending on your data. I'll describe a solution I did for a client recently and hopefully it'll help you out....
The way...
September 12, 2012 at 6:17 am
Hi,
Sorry for the delayed reply, work has been mad.
It's a difficult one to do unless you are loading in a full table each time (and not doing anything incrementally). If...
August 2, 2012 at 4:32 am
If the destination is a SQL Server db, you cannot beat a MERGE statement in T-SQL for performance.
As for the Oracle thing, SSIS would be your best bet. Do...
July 27, 2012 at 8:47 am
Another thing you may want to consider is adding in some sort of check to see if the columns actually have different values. I use CHECKSUM for this....
[Code="sql"]
WHEN
MATCHED AND
(
CHECKSUM
(
[Source].whatever
)
<>
CHECKSUM
(
[Target].whatever
)
)
THEN...
July 19, 2012 at 6:17 am
What steve said is right. The actual code would be
ucase(fields!ifieldname.value)
July 11, 2012 at 9:22 am
Doh! I meant to say the XML code for the drillthrough action. 🙂
May 31, 2012 at 9:09 am
Hi Dave,
Post the MDX and I'll take a look. 🙂
May 30, 2012 at 12:45 pm
If you use it in SSIS, for example, it can break your package if a new column is added.
Also, staying on the ETL thoughts, it's not always prudent to...
November 14, 2011 at 8:17 am
Viewing 15 posts - 556 through 570 (of 595 total)