Last edited Oct 30, 2013 at 5:20 PM by ChipL, version 4

Comments

ChipL Jan 23, 2012 at 9:44 PM 
Hi Nbarnard! Glad to hear you're enjoying BIMonitor. I'm sorry for the late reply. Have you fixed your problem yet? If not, are the SSIS packages whose logged data you'd like to monitor writing their log data to the stock SQL 2008 log table, dbo.sysssislog? That's what the Monitor SSIS Log package wants to read. To point the package to that location, you'll need to set two key variables in this package, SSISLogDBServer and SSISLogDB. This is done in the SQL Agent job step - and there's one of those for each environment monitored, if you monitor multiple environments. Are those variables being set correctly in the Agent job step? Have you verified that the dbo.sysssislog resides in that database and that your SSIS packages are logging to it? Please verify those things and if you need more help let me know.

Nbarnard Jan 10, 2012 at 9:14 PM 
Hello! I love love love your product. I was able to get most of the reports working, but I noticed that the logs are are not being populated on in the tables. I had some trouble in that section following the instructions. It would not work with ETL Logging DB, so I enter MSDB and the job was successful but no data is being pull. Can you help me? Let me know what you need to help you see my problem. Thanks!