Tests fail due to collisions in view names

Due to the usage of the selection of a random number from a range in instances when a large number of tests are being run I will occasionally run into view name collisions which cause the test to fail.

Added potential fix to generate a more unique view name using the test SQL itself