dmbaker (10/9/2007)
Not sure what you mean by "lose your package layout"...I don't think I've lost any layout in the packages I've migrated to structured sotrage files and I'm using embedded packages in a number of packages. Can you expand more on that?
Hm, thanks for that hint. Its not storing the package as structured storage file which makes you loose the layout. It happens only when you load and save a package using the DTS Object model.
http://www.sqldts.com/204.aspx
I agree that it's convenient to look at the logs right in SQL Server, but you can store those logs in files too (dynamically configuring the package to write the log file to a particular location). That can make it "easier" for support folks as they don't have to connect to the server to look at the logs -- although with very large log files that can become quite difficult or impossible. But then, you're not cluttering up your SQL Server with all that data either.
Well as a developer I have my issues with that. Because you will probably want to log to local disk. And thats where a developer has usually no access to. Makes support difficult. Btw, you can dynamically establish the name of the log file at run-time and add a timestamp for example. (Unfortunately this doesnt work with logging to SQL Server)
Best Regards,
Chris Büttner