query: What are SQL injection attacks on SQL Server? How can we prevent them?
positive_passages.docid: 29405
positive_passages.text: What is SQL injection?
negative_passages.docid: 6235
negative_passages.text: Is SQL syntax case sensitive?
negative_passages.docid: 62470
negative_passages.text: Understanding the impact/risk of turning off "verify backup integrity" on SQL backup
negative_passages.docid: 134892
negative_passages.text: SQL Server "Suspect" database?
negative_passages.docid: 122816
negative_passages.text: SQL injection with php filtering
negative_passages.docid: 123619
negative_passages.text: Shouldn't mysql_real_escape_string() leave slashes in Database?
negative_passages.docid: 95323
negative_passages.text: Is there an equivalent of PHP's mysql_real_escape_string() for Perl's DBI?
negative_passages.docid: 122381
negative_passages.text: SqlServer: Login failed for user
negative_passages.docid: 141091
negative_passages.text: How can sanitation that escapes single quotes be defeated by SQL injection in SQL Server?
negative_passages.docid: 3843
negative_passages.text: SQL Server compatibility with New TLS Standards
negative_passages.docid: 133877
negative_passages.text: How to Identify the primary key duplication from a SQL Server 2008 error code?
negative_passages.docid: 144268
negative_passages.text: Identity column value suddenly jumps to 1001 in sql server
negative_passages.docid: 38981
negative_passages.text: How can I prove that the following T-SQL is bad for performance?
negative_passages.docid: 94591
negative_passages.text: Recent patches for vulnerability attacks for SQL Server 2014 SP2 version
negative_passages.docid: 77690
negative_passages.text: Who is the person using a SQL login?
negative_passages.docid: 63897
negative_passages.text: How do I return a new IDENTITY column value from an SQLServer SELECT statement?
negative_passages.docid: 71340
negative_passages.text: How can prepared statements protect from SQL injection attacks?