March 2, 2010 at 9:20 am
Finally bit the bullet and started converting some of my DTS jobs to SSIS. Hopefully it is just a learning curve because so far it has been very painful.
I wrote what I thought was a simple SSIS to read three external flat data files and load the data into a table.
I finally was able to get the job to run through sql server agent but not consistently.
Often the job would blow up because it could not access one of the three flat files. I went down the road of it being a permission issue but eliminated that possibility because it occasionally worked. On a lark I changed the UNC location of the files from \\serername\common$\directory to \\ipaddress\common$\directory and now it works consistently. Could sql server agent not be resolving the server name within a given timeframe and if so can the timeout timeframe be changed?
Thanks
David Weil
March 2, 2010 at 9:47 am
David, I have no idea about your issue but would like to comment on SSIS in general.
The learning curve is very steep and painful.
I too was introduced to SSIS via requirement to convert some DTS packages to SSIS. I HATED it for at least two years. Mainly due to the explicit conversion you have to do now and the cryptic error messages. I've also struggled a lot with why one needs SSIS at all if you can do almost all of it in SQL.
I read somewhere that one should use SSIS for the E and L of the ETL and leave the T to SQL, that made much more sense to me. Worx has a book titled professional SSIS or something that also helped a lot.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply