October 17, 2014 at 5:59 am
Has anyone else encountered an issue with Google short-circuiting searches on SQL Server errors?
I've encountered this issue on and off for the past two weeks. I plug in something like "sql 2008 sp_update_schedule The specified '@active_end_date' is invalid (valid values are: 19900101..99991231)" and suddenly Google redirects my webpage to https://www.google.com/sorry/misc/ and the following error:
Our systems have detected unusual traffic from your computer network. Please try your request again later. Why did this happen?
It's starting to drive me nuts. How am I supposed to research problems if Google's going to assume I'm trying to hack (that's my best guess) rather than looking for forums and websites?
October 17, 2014 at 7:26 am
Haven't seen it myself, but plugging your search into google does give me the 'we're sorry...' page
Played about with the search term & it's the nnnnnnnn..nnnnnnnnnn bit that google seems to be objecting to.
October 17, 2014 at 7:54 am
I think you're right that it's the SQL injection checker that's firing and dropping you out. While certainly not ideal - have you tried removing the @symbol (and maybe even the single quotes?)
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 17, 2014 at 9:05 am
Bing worked, but only returned a single hit.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 17, 2014 at 10:54 am
Looks like google is having a problem with "19900101..99991231". If you remove that the search works. Don't know why, but that seems to be the issue.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
October 17, 2014 at 12:26 pm
The odd thing is that I've gotten this response when researching BIDS / Visual Studio errors too. This was last week and I don't recall anything that had variable names in it.
But then, it's been a pretty hectic week.
And as a bonus, we now know what database engine Google uses on its back end, don't we? EDIT: Well, at least we know it's SQLish, not Oracle...
October 18, 2014 at 1:34 pm
Google doesn't like nnnnn..nnnnnn, try searching any set of numbers and the G guy will tell you he's sorry. Probably an effort to stop certain type of searches like ip addresses, mac addresses, phone numbers or other "hackable" results.
😎
October 20, 2014 at 7:48 am
Brandie Tarvin (10/17/2014)
And as a bonus, we now know what database engine Google uses on its back end, don't we? EDIT: Well, at least we know it's SQLish, not Oracle...
Well I wouldn't reach that conclusion, Google would surely have programmers available that could prevent injection attacks, even if they did have SQL servers in their basic search job stream. Its a standard task to accept SQL text in a post and escape the offending characters that could produce an SQL injection.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply