Viewing 15 posts - 31 through 45 (of 50 total)
February 22, 2017 at 9:20 am
I checked the data in sysssislog and there are still a lot of Data Collections rows which the script from MDSN support does not address. Looks like we will...
February 22, 2017 at 9:17 am
The script provided by MSDN Community Support below targets the rows in sysssislog generated by Data Collections:
USE msdb;
DELETE FROM dbo.sysssislogWHERE source...
February 22, 2017 at 9:06 am
There are no packages deployed to the SSISDB database.
February 22, 2017 at 8:15 am
Thanks for the suggestion - I have logged this issue with MS Connect - please vote it up here: https://connect.microsoft.com/SQLServer/feedback/details/3116261
In the meantime we will do a manual cleanup...
December 13, 2016 at 7:34 am
The issue is not the MDW - it is that the rows in MSDB are not cleared up by any of the History Cleanup tasks.
December 13, 2016 at 6:44 am
There is no SSISDB catalog - and no SSIS activity other than the Data Collections. Its clear that the MDW is generating the millions of rows - the values for...
December 13, 2016 at 6:34 am
TDE is Enterprise only: https://msdn.microsoft.com/en-us/library/cc645993.aspx
Can I get my point for answering correctly?
December 9, 2016 at 8:39 am
Thanks for posting this - it is a great database monitoring solution. We have it in production on all versions of SQL up to SQL 2016. Note that in SQL...
December 9, 2016 at 8:28 am
Ok - found a Connect item for this - please vote it up: https://connect.microsoft.com/SQLServer/feedback/details/2887824/data-collector-does-not-collect-performance-counter
October 27, 2016 at 11:14 am
Thanks for the script - could also add "@notify_level_eventlog=2," to set the Write to Windows Application Event Log option.
October 6, 2016 at 8:29 am
We had the same issue - just restarted the Report Server service after deploying the charts to resolve.
Thanks!
March 24, 2014 at 10:26 am
We were getting the same issue loading a sharepoint list which had been running without problems "Error: System.TimeoutException: The request channel timed out while waiting for a reply". Changing the...
December 12, 2012 at 6:02 pm
Hi,
The SCD method requires a "business key" to match the records in the source and destination - as long as they have this then you should be able to use...
March 18, 2010 at 8:18 pm
Ok - got this - it was caused by leaving the TargetDataSourceFolder blank (had always done this in RS2005 to deploy datasources to same location as reports etc).
June 29, 2009 at 7:52 pm
Viewing 15 posts - 31 through 45 (of 50 total)