This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 56.00000000000001%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
Hi,
I need a query that is able to properly test if one version number is higher than another. When I use the where condition:
Version > "8.0.2020.8"
The result is returning versions that are lower than this version. Is it possible to inspect the 3rd section, in this example 2020, and compare that part against another version number?
value1 = 8.0.2020.8
value2 = 8.0.730.0
When these are compared as strings, 8.0.730.0 is appearing in my result.
Thank you!
Rob
A Microsoft extension to the ANSI SQL language that includes procedural programming, local variables, and various support functions.
Hi @Rob M
Is this issue solved now? If you have any questions, please feel free to share with us.
And don't forget to accept the answers if they helped. Your action would be helpful to other users who encounter the same issue and read this thread.
Thanks for your understanding!
Best regards,
LiHong
Using "not like" doesn't filter out the lower versions this way. I was hoping it would work.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
I don't think what you're trying to do is really going to work well in SQL, at least as a series of queries. String parsing is getting better but that isn't SQL strong point. If you must do this in the DB then I think you're going to have to do a series of queries with some programming logic mixed in perhaps with temp tables/variables to store data in between. At that point adding some UDFs would probably help a little bit.