SSIS bits 'n' bobs: Recent Comments2008-08-28T05:55:26Zhttp://ssisblog.replicationanswers.com/comments/atom.aspxQuick BlogComment on When to Not use SSIS - directory / file iterations!!!!tag:ssisblog.replicationanswers.com,2008-02-02:806622Paul Ibison2008-02-02T19:47:46Z2008-02-02T19:47:46Z]]>Comment on When to Not use SSIS - directory / file iterations!!!!tag:ssisblog.replicationanswers.com,2008-01-30:800063Nigelhttp://www.maneffa.com2008-01-30T19:40:22Z2008-01-30T19:40:22ZComment on Escaping Double Quotes in Flat Files: SSIS is different to DTStag:ssisblog.replicationanswers.com,2008-01-24:785142JeroenS2008-01-24T09:53:21Z2008-01-24T09:53:21Z"blatekst"","blatekst2","blatekst3" fails in SSIS.. even using the microsoft sample 'undouble' (http://www.microsoft.com/downloads/thankyou.aspx?familyId=b51463e9-2907-4b82-a353-e15016486e1d&displayLang=en) does not work; it hangs first on reading the csv before the " is changed...
Thanks, Jeroen Schoenmakers]]>Comment on Simple Method for Importing Ragged files / Files with Different Row Types in SSIS / Files with a problematic final rowtag:ssisblog.replicationanswers.com,2008-01-14:765944Paul Ibison2008-01-14T08:08:06Z2008-01-14T08:08:06ZCheers.]]>Comment on Simple Method for Importing Ragged files / Files with Different Row Types in SSIS / Files with a problematic final rowtag:ssisblog.replicationanswers.com,2008-01-14:765489bear in a box2008-01-14T01:24:26Z2008-01-14T01:24:26Zjust a thought, and even if so, tests for time to complete vs. file-based ops like above.]]>Comment on Coping with No Column Names in the OLEDB Data Source Editortag:ssisblog.replicationanswers.com,2007-12-09:701759Luke2007-12-09T18:22:53Z2007-12-09T18:22:53Z I haven't been brave enough to test this in SQL 2005, but I see nothing to suggest that it's changed.]]>Comment on Thorough Package Logging - Some Lessons Learned and Recommendationstag:ssisblog.replicationanswers.com,2007-12-09:701720Luke2007-12-09T17:33:19Z2007-12-09T17:33:19ZComment on Coping with No Column Names in the OLEDB Data Source Editortag:ssisblog.replicationanswers.com,2007-11-17:664638Paul Ibison2007-11-17T21:09:13Z2007-11-17T21:09:13Zstrange that this didn't work. At first I thought it might be related to recompilation, so I forced the proc containing the table variable to recompile but it still worked fine for me - no SET FMTONLY OFF and one execution only. Can you email me your proc (aul.Ibison@ReplicationAnswers.Com">Paul.Ibison@ReplicationAnswers.Com) and I'll try to repro. For now you might want to take a look at the comments of Phil and myself which will greatly reduce the # executions of the proc. Cheers, Paul ]]>Comment on Coping with No Column Names in the OLEDB Data Source Editortag:ssisblog.replicationanswers.com,2007-11-16:663001Shawn2007-11-16T21:53:58Z2007-11-16T21:53:58ZComment on Coping with No Column Names in the OLEDB Data Source Editortag:ssisblog.replicationanswers.com,2007-11-16:661123Phil Brammerhttp://www.ssistalk.com2007-11-16T00:02:31Z2007-11-16T00:02:31Z Also, what was the auditing mechanism in the sproc?
Basically, I'm looking for a repro so we can get a solid "best practices" going forward from the guys at Microsoft.]]>