SQL_Tutorial

SQL injection is a web security vulnerability that replaces the OWASP (Open Web Application Security Project) Top 10 every year. In shortly, SQL injection is caused by the fact that the data from the user is directly included in the SQL query.

In the example below, there is a simple login page written in asp language.

         FUsername = Request.Form("username")
         FPassword = Request.Form("password")

               Set RsLogin = SQLConn.Execute("SELECT * FROM Members WHERE username =      '" & FUsername & "' AND Password = '" & FPassword & "'")

         If RsLogin.EOF AND RsLogin.BOF Then
                Response.Redirect "/error.asp"

         Else
               Session("login") = RsLogin("user_id")
             Response.Redirect "../"

         End If

Let’s examine this code.

Welcome to one of the thousands of articles on SQL Server installation. In this article, I will explain the installation of SQL Server 2017 and I will discuss a few trick points.

The first thing you need to know is that SQL Server 2017 is separated from the Management Studio and SQL Server. When you install SQL Server, SSMS (SQL Server Management Studio) does not come with this nice feature, because when SSMS bug comes out, it is not necessary to update it with SQL server. We’re moving quickly to setup.