https://community.splunk.com/t5/Splunk-Search/Why-dedup-when-we-have-stats-values-function/m-p/474620#M133465 <P>@gcusello @woodcock @richgalloway <BR /> Why do we need two functions for the same functionality?<BR /> 'dedup' displays unique values while 'stats values' do the same, is there any difference other than 'stats' is transforming command and 'dedup' is not?</P> Fri, 03 Jan 2020 16:59:28 GMT palisetty 2020-01-03T16:59:28Z https://community.splunk.com/t5/Splunk-Search/Why-dedup-when-we-have-stats-values-function/m-p/474620#M133465 <P>@gcusello @woodcock @richgalloway <BR /> Why do we need two functions for the same functionality?<BR /> 'dedup' displays unique values while 'stats values' do the same, is there any difference other than 'stats' is transforming command and 'dedup' is not?</P> Fri, 03 Jan 2020 16:59:28 GMT https://community.splunk.com/t5/Splunk-Search/Why-dedup-when-we-have-stats-values-function/m-p/474620#M133465 palisetty 2020-01-03T16:59:28Z https://community.splunk.com/t5/Splunk-Search/Why-dedup-when-we-have-stats-values-function/m-p/474621#M133466 <P>Because there are times you want to dedup without using stats. So both commands are valid. If you are going to stats then you would be redundant to also use dedup.</P> Fri, 03 Jan 2020 17:06:56 GMT https://community.splunk.com/t5/Splunk-Search/Why-dedup-when-we-have-stats-values-function/m-p/474621#M133466 starcher 2020-01-03T17:06:56Z https://community.splunk.com/t5/Splunk-Search/Why-dedup-when-we-have-stats-values-function/m-p/474622#M133467 <P><CODE>stats</CODE> transforms, so your original fields are no longer accessible. <CODE>dedup</CODE> is a great way to limit the number of rows to be used further down the line, and still have full access to the fields and their values.</P> Fri, 03 Jan 2020 17:09:33 GMT https://community.splunk.com/t5/Splunk-Search/Why-dedup-when-we-have-stats-values-function/m-p/474622#M133467 jpolvino 2020-01-03T17:09:33Z