I have been using the SSIS Log Provider for SQL Server quite a lot this year with little to no problems. Recently however as I edit or create packages the logging seems to keep going to the master.dbo.sysdtslog90 table as opposed to the [db].dbo.sysdtslog90 as setup in the package. I tried totally deleting the connection from the package and recreating and still had the problem.
Is there some setting on the SQL server itself that can cause this? Our "dba" likes to make changes without letting anyone know about them.
Any ideas?
I've been doing some testing and I went ahead and tried to send the logging to a different db (used existing connection from another project) and lo and behold it works fine - went to existing db from another project. So my question is why would logging go to the master db on a connection that performs everything fine (on the correct db) for all tasks in the package? Smells like a bug to me but I can't put my finger on exactly why it's behaving that way.
No comments:
Post a Comment