Comments
Sort by recent activity
Hi All, Sorry for the inconvenience! This should be fixed in version 3.2.3 of SQL Search which was released today. Please let us know if you're still experiencing issues! Thanks, Asha Redgate Software Engineer / comments
Hi All,Sorry for the inconvenience! This should be fixed in version 3.2.3 of SQL Search which was released today. Please let us know if you're still experiencing issues!Thanks,Asha Redgate Software...
Hi @michaelmm22 , The latest SQL Search version (v 3.2.2) released today should now support Azure AD authentication. / comments
Hi @michaelmm22 ,The latest SQL Search version (v 3.2.2) released today should now support Azure AD authentication.
Hi @FleetDZ, @millennia - Sorry to hear you've been having some issues! We have been doing some recent work around this area, which included simplifying how we handle uploads to S3 storage; it seems likely some of these changes may have caused this. I have internally logged this issue as bug SB-5898. We will investigate and get back to you with any progress we make. Thank you for your detailed posts, they will be exceedingly useful in tracking down and replicating the problem! / comments
Hi @FleetDZ, @millennia -Sorry to hear you've been having some issues! We have been doing some recent work around this area, which included simplifying how we handle uploads to S3 storage; it seems...
Hi @dprince, Thank you for reporting this! We are currently looking into this, we expect the fix for this will be released in the next update. Thanks, Asha / comments
Hi @dprince,Thank you for reporting this! We are currently looking into this, we expect the fix for this will be released in the next update.Thanks,Asha
Hi @dnikhil, Thanks for your response! I have spoken with the support team and they are going to create a support ticket and will reach out to you as soon as they can. Please let me know if you haven't had any contact within the next few days. Thanks, Asha / comments
Hi @dnikhil,Thanks for your response! I have spoken with the support team and they are going to create a support ticket and will reach out to you as soon as they can. Please let me know if you have...
Hi @dnikhil, Sorry to hear you're having a problem! Did you click the "Send Error Report" button when you encountered the error? Is it possible for you to expand the error box to see the error message? Thanks, Asha / comments
Hi @dnikhil,Sorry to hear you're having a problem! Did you click the "Send Error Report" button when you encountered the error? Is it possible for you to expand the error box to see the error messa...
Currently the option is working as expected. For anyone who has feedback on this (or opinions on how the option should work instead) I would advise you to log a vote in the uservoice forums I linked to above. We don't make changes without considering use cases. If you've experience working on a commercial product that relies on customer feedback you know that if you make changes to anything there are always going to be people who are unhappy as well as happy, and usually the people who are happy are quiet unless you change it again. You need to try to optimise the situation to maximise the happy people against the unhappy. The last thing you should do is make changes due to the opinions of the outspoken few - this is why we rely on uservoice, it allows us to get a much more general view of consensus. Thanks, Asha / comments
Currently the option is working as expected. For anyone who has feedback on this (or opinions on how the option should work instead) I would advise you to log a vote in the uservoice forums I linke...
Hi @mdullni1, We currently don't have any intention of introducing a "Match Whole String" option. If you want to make a suggestion for a new feature, please add it to our Uservoice panel. https://redgate.uservoice.com/forums/101149-sql-search Thanks, Asha / comments
Hi @mdullni1,We currently don't have any intention of introducing a "Match Whole String" option. If you want to make a suggestion for a new feature, please add it to our Uservoice panel.https://red...
Hi @mdullni1, The reason "lngRcrdSttsID in (" returns nothing in this case is because there isn't a space after the open bracket in your view. If your view was instead "WHERE lngRcrdSttsID in ( 1, 2)" with a space after the open bracket, then the result would be found. This is because the "Match whole words only" only matches whole words. SQL Search considers a word to be any text separated by a whitespace. So in your case, it treats "lngRcrdSttsID" as a word, "IN" as a word, "(1," as a word and "2)" as a word. As you are not searching for a whole word - because "(" isn't considered a whole word - you are not getting a result. This would be an example where ignoring commas in the definition of a word may be useful to you, as we were discussing earlier in the thread. If SQL Search didn't include commas in its definition of a word, then instead of "(1," being defined as a word, "(1" would be defined as a word. Then, searching for "WHERE lngRcrdSttsID in (1" would return your result. If you turned the "Match whole words only" option off you would also see the result. Thanks, Asha / comments
Hi @mdullni1,The reason "lngRcrdSttsID in (" returns nothing in this case is because there isn't a space after the open bracket in your view. If your view was instead"WHERE lngRcrdSttsID in ( 1, 2)...
Hi @mdullni1, I'm still not seeing the behaviour you're describing. For example, I created a stored procedure with four different select statements, each effectively selecting from a table where "ID IN (1)" but with spaces in different areas of the statement. When searching for "ID IN (" I saw two highlighted results - the results where there was a space before the number. This is expected behaviour: [image] When searching for "ID IN (1" I saw one highlighted result - this is the only entry where the statement "ID IN (1" is followed by a space. This is also expected behaviour: [image] Similarly, when searching for "ID IN ( 1" I saw again one highlighted result - this is the only entry where the statement "ID IN ( 1" is followed by a space. This is also expected behaviour: [image] Have you got any scripts of an example of something that you would expect to be showing but isn't? Can you post any screenshots? Thanks, Asha / comments
Hi @mdullni1,I'm still not seeing the behaviour you're describing. For example, I created a stored procedure with four different select statements, each effectively selecting from a table where "ID...