What are those in the Data Collector folder ? I tried to delete some and got the message that it was conflicting with some reference.
SQL Server SSIS – Packages in Data Collector Folder
sql serverssis
Related Solutions
Nope, you don't need SSIS on the server you are collecting data from, bits of SSIS are installed anyway when you install SQL server and this is enough for the data collector to work. All the system data collector sets work out of the box once you have set up the management data warehouse and enabled them.
The actual SSIS packages for data collector are stored within MSDB, rather than SSISDB as with a full SSIS server and they are executed by a process called Dcexec.exe.
The full architecture for how data collector works is detailed here:
Have you looked under Advanced Security Settings?
The arrows point to the modifications I've often had to specifically apply when installing SQL Server on Windows 2012 R2.
For the SQL Server Root Directory, I'll give full control to the SQL Server Process account.
Related official documentation:
Configure File System Permissions for Database Engine Access
Securing Data and Log Files
Related Question
- SSIS Permissions – Restart Services for Folder Permissions Propagation
- Upgrading SSIS Packages – Step-by-Step Guide
- Sql-server – Package sttill used
- SQL Server – Determine PackageFormatVersion for Multiple .DTSX Files
- Sql-server – MDW Data Collector Server Activity collection step 3 suddenly stopped working
Best Answer
Those packages are related to Management Data Warehouse.
If you open SQL Server Management Studio you will find a node 'Data Collection' where you can right click to configure data collection and also have access to some historical reports about server activity.
Have a look at System Data Collection Sets where for example it states:
For more information see Data Collector Architecture and Processing.
I'm not sure how you got to a point where you get 2 versions of each package (where one is appended by (1)). I tried reproducing that by enabling/disabling collection or creating a new MDW but maybe you got into that state by upgrading and then re-enabling data collection or something.