February 14, 2011 at 10:37 am
Comments posted to this topic are about the item What is SSIS? Step 1 of the Stairway to Integration Services
Andy Leonard, Chief Data Engineer, Enterprise Data & Analytics
February 17, 2011 at 11:15 am
Hi Andy,
Any chance that you can move your articles out of the future and into the present? The first article has a posting date of 2011/03/30 and this is only 2011/02/18. Thanks for articles and allowing us to go back to the future to read them!
Jim
March 29, 2011 at 11:59 pm
Nice introductory article, Andy! Can't wait for the rest of the series.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 30, 2011 at 3:24 am
Thanks for the article - I look forward to the next ones.
I try and use SSIS for any new ETL functionality we need, but as for having the time to migrate our hundreds of old DTS packages, forget it. Whatever Microsoft want, DTS will still linger on for a few years yet it many organisations I think.
March 30, 2011 at 7:00 am
Andy,
Great article and I am looking forward to the rest of the series. I am just starting to learn SSIS as my company is looking for faster ways to view data. I am hoping to run SSIS packages which reads data and dumps it into an excel file which can be viewed by managers.
We are finding reports from our ERP to be very slow and the time it takes to run queries which produce the same data is 10 times faster.
I just have a couple of questions for you. You mention C# as a scripting tool in conjunction with SSIS. How important is it to know C# for SSIS and what shortcomings do you face without it?
Is it difficult to take queries I have successfully run and transport them into an ssis package to be run as a job?
Thanks for the article and your reply.
March 30, 2011 at 9:21 am
jberg-604007 (2/17/2011)
Hi Andy,Any chance that you can move your articles out of the future and into the present? The first article has a posting date of 2011/03/30 and this is only 2011/02/18. Thanks for articles and allowing us to go back to the future to read them!
Jim
I had the same initial thought. I thought. But my take was, FINISH THE SERIES NOW!!! :w00t: Great article to start off the series.
March 30, 2011 at 9:50 am
Good article Andy, I look forward to reading the rest of the series..
CEWII
March 30, 2011 at 10:07 am
Thank you! I Look forward to Step2 and beyond. I work at a place that provides very little technical training, so this type of article is invaluable.
March 30, 2011 at 4:16 pm
Love your work Andy... look forward to reading the subsiquent articles.
Does anyone know if anything similar has been done for Analysis Services... "now there is one puppy I have trouble understanding."
Dave
March 30, 2011 at 4:17 pm
Thanks Andy, I am looking forward to the next step in the series.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
March 30, 2011 at 11:42 pm
Andy,
Great article i am dying know more about SSIS, looking forward to read the rest of the series.
thanks buddy great work
March 30, 2011 at 11:51 pm
Hi Andy,
Great article I am dying to know more about SSIS, looking forward to read the rest of the series.
thanks buddy great work
March 31, 2011 at 3:51 am
Good stuff. Looking forward to the rest of the articles to improve my SSIS knowledge.
March 31, 2011 at 6:48 am
Andy
This is great stuff... Eager to read the rest....
April 3, 2011 at 1:03 pm
kwoznica (3/30/2011)
You mention C# as a scripting tool in conjunction with SSIS. How important is it to know C# for SSIS and what shortcomings do you face without it?
Is it difficult to take queries I have successfully run and transport them into an ssis package to be run as a job.
Hi kwoznica,
You have the choice of C# or VB for scripting in SSIS 2008 and 2008 R2. It's not mandatory to know how to script to write SSIS packages, but knowing scripting adds another tool to your toolbelt for building SSIS (and other) solutions. I recommend you learn as much as you can.
You can use the Execute SQL Task to run queries in SSIS. Most developers mature as they work with a language or platform - their coding style evolves. Many SSIS developers start learning SSIS by building packages using the Import and Export Data Wizard. This wizard actually creates an SSIS package in RAM and then executes it. You can save the package and open it for editing or re-execute it later.
Other SSIS developers begin by using only Execute SQL Tasks for T-SQL operations. They use the SSIS Control Flow as a "workflow engine" (it's an excellent workflow engine!) and learn the Data Flow later.
:{> Andy
Andy Leonard, Chief Data Engineer, Enterprise Data & Analytics
Viewing 15 posts - 1 through 15 (of 41 total)
You must be logged in to reply to this topic. Login to reply