February 16, 2012 at 4:03 pm
cw.izatt (2/16/2012)
Jeff Moden (2/16/2012)
cw.izatt (2/16/2012)
Why not? SQL is perfectly capable of handling it and if it is a dedicated SQL Server it is probably the best tool to use.
After thinking about it either is valid, but for me i would rather handle that with powershell and push it into the DB instead of the other way around, but that might be the sys admin talking in me.
Understood. Let me ask... how are you scheduling the PS job to run?
Just like this.
http://www.sysadminsblog.com/microsoft/scheduling-powershell-scripts/
Thank you for the link.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 17, 2012 at 7:22 am
Thanks, all. Turns out it was a result of applying sp3 which reset the DCOM permissions for the SQL Agent account. I set the remote access, launch and activation permissions on MsDtsServer100 and viola! It works again:-D It would have helped to get some type of error but there was nothing in the SSIS logs, nor any of the system logs. I later found http://support.microsoft.com/kb/2000474 which points to the same solution. Happy Friday!
February 17, 2012 at 9:04 am
Always a great feeling. hahaha
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply