Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to bulk update vRA Data collection interval and Enable/Disable data collection (53119)

Last Updated: 5/18/2018Categories: How toTotal Views: 2981Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This KB article provides a process to bulk update the data collection interval using a stored procedure against the IaaS SQL database. Use this procedure if you want to update the data collection frequency in vRA for large number of compute resources.

Impact / Risks

When directly modifying the database, there is always a chance for data loss. Ensure to take a backup of the IaaS SQL database before making any modifications.

Resolution

To bulk update the data collection interval:

Download the attached stored procedure, 53119_vRA_bulk_update_collection.sql.

Launch SQL Management Studio and connect to the vRA IaaS database

Open 53119_vRA_bulk_update_collection.sql and execute to create the stored procedure, vmware_utility_vRA_bulk_update_collection_frequency.

Execute the stored procedure with the below query and options.

exec [dbo].[vmware_utility_vRA_bulk_update_collection_frequency]

Run this without any options to display help for the stored procedure.

Additional arguments

@ComputeResourceLike - Use this input parameter to specify the compute resources you wish to change the collection frequency for. You can use SQL wildcards used with LIKE where clause

Example: @ComputeResourceLike = '%abc%' --will update all compute resources with abc somewhere in the name.

@ComputeResourceLike = 'abc%'  --will update all compute resources that start with abc in the name.

@ComputeResourceLike = 'abc' --will update all compute resources named exactly abc.

@DataCollectionType = '<type>' --must be one of these three types: Inventory, State, or Performance.

@FrequencyMinutes = '<frequency_in_minutes>' --frequency in minutes. Note that for Inventory and Performance collection types this must be in multiples of 60. 60 = 1 hour, 120 = 2 hours, and so on.

Note: To set the Frequency to the Default value pass -1 as <frequency_in_minutes>. Set to NULL or do not pass the parameter to not change and leave collection frequency as currently set.

@CommitChanges = '<value>' --set this value to 1 to actually make the changes. For any other value the changes will not be made, but rather the procedure will output the "Current" values

Note: Only change this value to '1' after a dry run has been performed and updated values have been confirmed.

@EnableDisableCollection - Set this value to 1 to Enable, 0 to Disable. Set to NULL or do not pass the parameter to not change and leave collection enable/disable as currently set.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

53119_vRA_bulk_update_collection_V2.sql

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 7.x

Take Our Survey

Support Assistant