December 17, 2013 at 10:48 am
Hi guys,
I am working on a project, part of which is the extraction and transformation of large record sets. This happens every hour from 5am to 10pm weekdays and at 11pm each night. The current solution is a VB.NET exe that is started by an SQL job. The VB code is mostly ADO.NET.
What would the benefits be if I migrated the code in an SP?
Would I get better exception handling and exception reporting?
What would be easier to debug?
Which would be faster?
December 17, 2013 at 12:04 pm
ETL tools of choice for SQL Server is SSIS or SQL Server Integration Service. You can get rather complex with your extract & transforms. There are other third party tools where you can develop ETLs. I know SAP has their Data Services which my present employer is utilizing for a lot of data movement.
SSIS packages are built in the SQL Server Business Intelligent Studio which is a derivation of Visual Studio.
As for reporting issues/problems on your ETL just all depends what the requirements are.
Finally, as for performance, well depending on the ETL design, complementary loading stored procedures the process can perform quite well.
Hope this helps.
Kurt
Kurt W. Zimmerman
SR DBA
Lefrak Organization
New York, NY
http://www.linkedin.com/in/kurtwzimmerman
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply