Skip to main content

Limiting search results by site

Experts Exchange has the irritating marketing tactic of posting a discussion article that often seems to match exactly what I'm looking for, but the response to the question requires registration.  Since the answer to most any question is likely somewhere else on the Internet as well it's possible to restrict search results from even showing anything from this site.

Here's how to do it.  At least Bing, Duck Duck Go, Google, and Yahoo have the ability to specify a "sites" argument in a search.  It can be used to either force results from a specific site to be included or excluded.  The real nice part is that the syntax is the same for all of them, so including the following snippet into a search string can eliminate search results from Experts Exchange:

-site:experts-exchange.com

NOTE:  Whether pages are included or excluded depends on the (-) operator preceding the limiter.

The following example could be used to search for how to use the SQL TOP command with SQL Server.


-site:experts-exchange.com +"sql server" +"top"


This ensures that only non-Experts Exchange results are returned.  Conversely, if the excellent Stack Overflow should be only place to get results from, the search query could have been as follows (notice there is no minus operator in front of the sites limiter).

site:stackoverflow.com +"sql server" +"top"

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more