January 3, 2014 at 4:17 pm
hi,
i am Kannan. i need tmplate for loading flat files into staging as well as historical simultaneously. now i am currently using data flow transformation in for each loop container. first i am loading files into satging server, then inserting to historical server. kindly clarify any other better ways to load the same.
thanks in advance,
Kannan.
January 3, 2014 at 4:39 pm
Kannan Vignesh (1/3/2014)
hi,i am Kannan. i need tmplate for loading flat files into staging as well as historical simultaneously. now i am currently using data flow transformation in for each loop container. first i am loading files into satging server, then inserting to historical server. kindly clarify any other better ways to load the same.
thanks in advance,
Kannan.
you need to provide more details about what you want to do.
January 3, 2014 at 4:47 pm
Kannan Vignesh (1/3/2014)
i am Kannan.
Hello, welcome to SSC.
i need tmplate for loading flat files into staging as well as historical simultaneously.
You've combined three things here at once.
First, that you're looking to generate a template. You don't want to create a template for this because each flat file usually has different construction. If they're the same exact metadata (same field types, same sizes, same order) than maybe you want a template. Then again, for just one or two more, copy/paste is more efficient.
Next, you want to load flat files into staging. That's a simple data flow. Are you having trouble with that component?
Lastly, you say historical. What do you mean by historical? Are you trying to archive the original file for auditing or are you trying to save the record changes into an audit component? The first you'd do want to do in SSIS, the second you'd want to do via a trigger and/or MERGE command to load the older records to another audit table.
now i am currently using data flow transformation in for each loop container. first i am loading files into satging server, then inserting to historical server. kindly clarify any other better ways to load the same.
You would first need to clarify my above questions in this regard. We need a lot more detail then the generic overview you've given us.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
January 3, 2014 at 5:07 pm
curreuntly using structure:
staging server
1.duplicate check--> 2.data flow transformation(flatfileconnection to oledbdestion(temptable) with looping -->3. temp table to live table(staging table)--> 4. insert log table
after that (historical server)
temp table(used in staging server)-->historical table..
January 3, 2014 at 5:28 pm
thank u..
all flatfiles having same kind of data,no of columns also same. data flow task is enough for loading.
historical server contains all data from the beginning like staging. but in staging maintain only ten days data.
my package is working fine. but sometimes if any body runs query to retrive large data in historical server means loading will be affect.
January 4, 2014 at 2:12 pm
I agree with everything Craig has stated.
If I am looking at this thread correctly, one of your challenges is loading into a final target table while that target table is under a query load? If so, the data loading performance guide is a great reference, but ideally you want to have a load time window when minimal activity is happening in the database. However, if you CANNOT avoid this situation, there are ways to mitigate this such as Trace Flag 610 and other stuff in this guide:
http://technet.microsoft.com/en-us/library/dd425070(v=sql.100).aspx
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply