SQL Server Integration Services
•Download as PPTX, PDF•
1 like•2,014 views
This session provides an introduction to using SSIS. This is an update to my older presentation on the topic: http://www.slideshare.net/rmaclean/sql-server-integration-services-2631027
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (7)
Similar to SQL Server Integration Services
Similar to SQL Server Integration Services (20)
More from Robert MacLean
More from Robert MacLean (20)
Recently uploaded
Recently uploaded (20)
SQL Server Integration Services
- 1. SSIS
- 2. Microsoft’s ETL solution bundled with SQL Server E – Extract T – Transform L – Load What is it? Destination Source Source Write Read SSIS
- 3. A simple ETL
- 4. When to use Script YES NO Can one or more components do the same thing? NO YES Use those Unique situation Build custom component Use script
- 5. Confusion
- 8. Very basic queue support
- 9. XML support limitedReasons not to consider SSIS
- 10. Merging Data from Heterogeneous Data Stores Populating Data Warehouses Cleaning and Standardizing Data Building Business Intelligence into a Data Transformation Process Automating Administrative Functions and Data Loading Areas SSIS is strong
- 11. Command line tools (dtexec, dtutil) cannot co-exist with 32bit versions. No DTS support. Limitations on data providers – No Access, Excel or SQL Compact IA64 has more limitations including no designer support X64 Limitations
- 12. Running 32bit on 64bit
- 14. Lookup vs. Merge Join or Execute SQL vs. Execute T-SQL
- 15. Understand which components run asynchronously and which run synchronouslyWhat to watch out for
- 19. Source Control Highest Encryption Easy loading into designer Access by multiple users DB Roles, DTS Roles SQL Backups Able to filter packages Files Server Storage Options Details http://www.sqljunkies.com/WebLog/knight_reign/archive/2005/05/05/13523.aspx
- 21. No more often than 3x avg. execution time. Settings in configuration files. Enable logging (step) and notifications (job). Execute signed packages only. Do not make packages which execute themselves. Scheduling Guidelines
- 22. DTS Upgrade Options Run DTS in 2005 or 2008 Missing the package logs Runs under 32 bit Upgrade using MS Wizard Not compatible with most package Upgrade using DTS xChange Minutes per package Starting from scratch About 3-6 hrs per package conservatively
- 23. Package Upgrade Wizard Built into SQL Server 2008 Pros: Free Works on simple packages Cons: Does not handle ODBC Only handles a few types of text file use cases No Dynamic Properties Task No UDL or legacy database support in data pump Packages only have about a 20% chance of working
- 24. Profiles DTS packages to help with a conversion project plan Rapidly converts DTS Packages to SSIS (2005 or 2008) and applies SSIS best practices Converts tasks that are not handled by the existing SQL Server conversion wizard Includes a SSIS logging repository and reports for trending and alerting Includes BI xPress for new SSIS packages DTS xChangeUpgrade
- 25. ActiveX Script Upgrade Both tools mentioned migrate DTS ActiveX to ActiveX in SSIS ActiveX migrates to SSIS but you would not want to keep it there and it may not run Need for ActiveX Script Task has been replaced with built-in, easy to maintain SSIS tasks File System Object = File System Task Mail objects = Send Mail Task (now has SMTP) ADO objects = Execute SQL Task
- 27. http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/ssisperfstrat.mspx http://ssisblog.replicationanswers.com/2008/01/04/when-to-not-use-ssis--directory--file-iterations.aspx http://marcusrosen.blogspot.com/2008/04/sql-server-2005-integration-service.html http://www.eggheadcafe.com/software/aspnet/32465151/linked-servers-versus-ssi.aspx http://blogs.conchango.com/jamiethomson/archive/2006/06/28/SSIS_3A00_-Comparing-performance-of-a-raw-file-against-a-recordset-destination.aspx http://www.microsoft.com/technet/prodtechnol/sql/2005/ssisperf.mspx References
Editor's Notes
- Create a new packageAdd a data flow componentAdd a flat file connection – set it to the exercise.csv data. So suggested data times.Add a flat file source – bind to connectionAdd conditional splitLink to flat fileSplit on distance > 0Add sortLink to main split outputSort on dateAdd ADO.NET data destination connection manager – to spacedata.exerciseAdd ADO.NET DestinationLink to sort and connection managerDo mappingAdd Variable-Make sure scope is packageAdd Row countLink to conditional split elseLink to variableOn Control flowAdd SMTP taskSMTP connection to webmail.bbd.co.za and windows auth-Message body expression from file and change variableSave -> Run -> CrashChange distance to float on flat file connection, trickle changesSave -> Run -> Email
- SSIS adds layers of support, logging etc... These all add a performance hit and you should not waste time using it for things where a quick BCP or even c# code would be better.SSIS is perfect for batch solutions, it is BAD for near real time solutions. There are tools built into SQL server (linked servers) and other tools (BizTalk) which handle real time well.SSIS is not a SOA/ESB/B2B tool it is a ETL tool.
- Use management studio script to clean data outAdd Excel SourceDelete flat file sourceConnect Excel source to split inputOpen excel source, create new OLE DB connectionTrickle changesSave -> Run -> CrashProject -> Properties -> Debugging -> Run64bitRuntime -> FalseSave -> Run
- Record set info: http://blogs.conchango.com/jamiethomson/archive/2006/06/28/SSIS_3A00_-Comparing-performance-of-a-raw-file-against-a-recordset-destination.aspxMemory – Make sure you have enoughSELECT * - all that meta data and unused columns need processing!Small packages – You can call one package from another. Allows work to be broken up, which means a team can easily work on the solution, makes fault finding easier, lowers over headsComments – DUH!Understand the components is key to super usage – Many can be used to do the same thing. Lookup and Merge Join for instance can both be used to lookup data. Lookup has three modes which imposed performance vs. Memory trade offs where merge join does not. Merge join requires sorted input while lookups don’t. Execute SQL allows any SQL dialect while execute T-SQL allows only T-SQLBecause things can be put into parallel that doesn’t mean they execute in parallel. Some are async and some aren’t!