Currently the profiler selects all data from the source table for profiling. While this is OK for most use cases, there are some cases in which a user may want to limit the amount of data being profiled. This could be done via a where clause that would allow the user to segregate the profiling as they choose.
Currently the profiler selects all data from the source table for profiling. While this is OK for most use cases, there are some cases in which a user may want to limit the amount of data being profiled. This could be done via a where clause that would allow the user to segregate the profiling as they choose.