SQL Server Integration Services
•Télécharger en tant que PPTX, PDF•
6 j'aime•10,882 vues
The presentation from my talk on what is SQL Server Integration Services (SSIS). It looks at it in Microsoft SQL Server 2008.
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (16)
Similaire à SQL Server Integration Services
Similaire à SQL Server Integration Services (20)
Plus de Robert MacLean
Plus de Robert MacLean (20)
Dernier
Dernier (20)
SQL Server Integration Services
- 1. SQL Server integration services
- 2. What is it? Microsoft’s ETL solution bundled with SQL Server E – Extract T – Transform L – Load Destination Source Write Read SSIS
- 3. Demo A simple ETL Demo
- 4. Demo You can get a little crazy...
- 5. Why?
- 9. Very basic queue support
- 11. What’s New in 2008 Lookup transformation performance improvements and new caching options ADO.NET Source and destination components Data profiling task and viewer Wizard interface for defining source and destination Scripts (for the Script Transform) are now done in Visual Studio and thus in .NET languages. New package format Three new data formats for working with times
- 12. x64 Limitations 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
- 13. Demo Running in 32bit on 64bit!
- 15. Lookup vs. Merge Join or Execute SQL vs. Execute T-SQL
- 17. Storage: Files or Servers Details http://www.sqljunkies.com/WebLog/knight_reign/archive/2005/05/05/13523.aspx
- 18. References 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
Notes de l'éditeur
- PREP:SQL Server BIDS – Demo Solution openSQL Server Management Studio with cleanup scriptZoomITMake sure the solution is in 64bit mode!
- 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
- Show completed solution data flow
- At a simple level moving data around sounds very easy, but when you break it down, it gets more and more complex and different needs requires different tools.SSIS is not a swiss army knife. It is a specialist tool.
- 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.
- Lookup PerformanceThe ability to take rows that do not have matching entries in the reference dataset and load those rows into the cache.The ability to use separate data flows to load the reference dataset into the cache and to perform lookups on the reference dataset.Data profiling is used to profile the data in SQL server to see the quality/type of data. Useful for identifing improvements and fixing bugsThere is a tool to convert to the new format.
- 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!