May 19, 2009 at 1:32 pm
Hi All,
We have a couple SSIS packages that were working fine while pointing at a client's SQL Server 2000 instance. They're in the process of migrating to SQL Server 2005. We ran a test to make sure that everything worked the same when pointing at their 2005 DB instance as it does against their 2000 DB instance.
First, we ran the integration against the 2000 DB instance to get a baseline. Everything worked as planned and the SYSDTSLOG90 table was updated as expected.
Then, we ran the integration against the 2005 DB instance. Comparing the two DBs shows that the data was transferred over as expected. However, the SYSDTSLOG90 table wasn't updated at all. We've checked master.dbo.sysdtslog90 and even run the profiler to see if we can figure out where the information is getting logged to, but can't seem to figure it out.
Any suggestions on what to check?
Thanks,
Jared
May 20, 2009 at 11:08 am
Quick follow up - we deleted the packages, reimported them, and everything worked just fine.
I still don't know exactly what caused the data to not get written, but at least we know the fix...
May 31, 2009 at 8:52 pm
I'm trying to implement SQL Server logging for the first time. My table sysdtslog90 was created but nothing is written to it. I have not deployed the package to SQL Server (2005)yet. Would you be able to give me some guidance? Thanks.
May 31, 2009 at 10:08 pm
Have you tuned any logging options on for any of the executables?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
June 1, 2009 at 7:55 am
Thank you for responding. Yes, I have turned on logging options at the package level and then defaulted each task to have the same logging options as the package. So the logging mode for each of my tasks shows UseParentSetting and for the Package it shows enabled. Then in the Detail I selected OnError, OnFailedTask, etc. When I create a log provider for Text files, it logs everything. Any other suggestions?
June 1, 2009 at 10:47 am
Hmm, best guess I have is that something may be wrong with the connection manager. What kind are you using?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
June 2, 2009 at 7:29 am
OLEDB
I will try deleting it and redoing it. I followed instructions from a book I bought SQL Server 2005 Integration Services (Step by Step). It seem to be pretty good. If you can think of anything else, please let me know.
Thanks
June 2, 2009 at 10:46 am
I believe that when you change the Logging provider (in Logging setup) you have to redo the Logging setting/options too.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
June 2, 2009 at 12:37 pm
I found my problem. The way our DBA gave me access to the database where I'm logging eveyrthing, caused my package to create the table setting the owner to my username. The stored proc that populates the entries to sysdtslog90 was looking for the owner to be dbo, so therefore it wasn't finding the table to log the entries.
Thanks for your responses.
June 2, 2009 at 3:07 pm
Glad it you found it, and thanks for letting us know. 🙂
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
January 20, 2010 at 12:21 am
Hi,
I ran into same problem today morning. My package was logging everything configured to text file and suddenly it stopped logging. I tried everything, redoing the connection, task but no success.
I then configured to log errors to SQL Server db and gave the proper connection. But nothing was logged into the table. Forget that i could not even see sysdtslog90 table.
Do i have to create it manually again and again.
I have sa rights on that server.
What is that i'm missing.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply