![]() ![]() These issue have been painful to diagnose and have cost me a lot of time.Īs such, what I would like to do is publish my package to the SSIS server, start the server instance from BIDS and monitor the project as it runs. Historically, my problem has been that not all problems will occur in BIDS, but they will, consistently on the server. ![]() This is useful because it's been my experience that any error generated from within BIDS are much more useful than anything I've found from within SQL Server/Package Execution History or the servers event logs. ![]() To troubleshoot this process, I fire up BIDS on my workstation and restart which ever process fails. In short, I have a series of SSIS packages that are scheduled to run on a nightly basis, on our SQL Server machine.ĭue to various updates that happen in the ether of my corporate-IT, some times these exports brake and the process will stop working, in the middle of the job. Although my title states my current goal, I am open to alternative solutions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |