﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Jayram Tallamraju / Article Discussions / Article Discussions by Author  / Data Import Functionality Using SQL Server / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 19 Jun 2013 00:57:16 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>:D</description><pubDate>Fri, 08 Aug 2008 17:51:20 GMT</pubDate><dc:creator>mcajanarth</dc:creator></item><item><title>RE: Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>"Data Driven Query Task" suck, if you ask me.  Other than that, it's a pretty good overview of what you can do with DTS.  Personally, I put business rules in SQL code, preferably making it data driven so users can modify the imports in simple ways without changing code.cl</description><pubDate>Tue, 16 Aug 2005 17:40:00 GMT</pubDate><dc:creator>Calvin Lawson</dc:creator></item><item><title>RE: Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>&lt;P&gt;Why don't you provide database ?&lt;/P&gt;</description><pubDate>Mon, 15 Aug 2005 10:09:00 GMT</pubDate><dc:creator>Marco Esquivel</dc:creator></item><item><title>RE: Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>&lt;P&gt;As the article is over two years old and the author has not been active on the website since posting the article, I'd say the download is no longer available.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description><pubDate>Wed, 02 Mar 2005 01:17:00 GMT</pubDate><dc:creator>philcart</dc:creator></item><item><title>RE: Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Could you please let me know the URL, where i can find the Sample Code for this.&lt;/P&gt;&lt;P&gt;Thank You&lt;/P&gt;</description><pubDate>Tue, 01 Mar 2005 23:55:00 GMT</pubDate><dc:creator>Dhanunjay Kumar Vootada</dc:creator></item><item><title>RE: Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>I'm brand new to the whole DTS scene, and I found the article very helpful.  However, my task involves some conditional processing.  Could you help me by providing some examples of conditional logic for determining whether the current row is existing or not (ins vs upd)?  I know very little VBscript/ActiceX, but I can extrapolate from examples.I really appreciate it.</description><pubDate>Thu, 17 Jun 2004 18:36:00 GMT</pubDate><dc:creator>Oblio Leitch</dc:creator></item><item><title>RE: Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>This is a very useful article, and should help get us started on our project.  But I can't find the "download" scripts anywhere.  Are they on this website?Iain </description><pubDate>Mon, 22 Sep 2003 06:24:00 GMT</pubDate><dc:creator>irhm</dc:creator></item><item><title>RE: Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>One option to maintain the clean modularity of your notification task is to use two packages to organize or "scope" your code.  The added "controller" package contains an &lt;b&gt;Execute Package Task&lt;/b&gt; for the existing package of ETL tasks. The &lt;b&gt;Send Mail Task&lt;/b&gt; is moved to the controller package with an &lt;b&gt;On Failure&lt;/b&gt; constraint from the &lt;b&gt;Execute Package Task&lt;/b&gt;. Pass the path of the ETL package's log file back to the controller package as a global variable. Set the &lt;i&gt;FileAttachments&lt;/i&gt; property of the &lt;b&gt;Send Mail Task&lt;/b&gt; to the global variable value so that the log file can conveniently be read as an attachment to the failure notification email.This would avoid the development burden of building a custom task or ActiveX script to avoid redundancy. (Of course, a custom task is the direction to go when you need powerful auditing or, especially, an error handler...but throwing COM or Visual Studio into the mix probably won't meet the spec for simplicity of maintenance.) </description><pubDate>Wed, 30 Oct 2002 18:24:00 GMT</pubDate><dc:creator>layne</dc:creator></item><item><title>RE: Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>Paul,You are 100% right. This is very good point. Sample code I supplied uses this approach but failure notification is never sent if process fails initially in any of the tasks. I guess best approach in this case is to have separate failure notification task in each case. Thanks for your valuable comments.Jay </description><pubDate>Thu, 24 Oct 2002 21:38:00 GMT</pubDate><dc:creator>tjayram</dc:creator></item><item><title>Data Import Functionality Using SQL Server</title><link>http://www.sqlservercentral.com/Forums/Topic7651-95-1.aspx</link><description>Comments posted to this topic are about the content posted at &lt;A HREF=http://www.sqlservercentral.com/columnists/JTallamraju/data_import_functionality_using.asp&gt;http://www.sqlservercentral.com/columnists/JTallamraju/data_import_functionality_using.asp&lt;/A&gt;</description><pubDate>Wed, 23 Oct 2002 00:00:00 GMT</pubDate><dc:creator>tjayram</dc:creator></item></channel></rss>