Let’s just see an example of this situation.įor this demo, I launched multiple query editors within the SQL Server Management Studio, connected to the same instance of SQL Server. Not only is this bad from a security standpoint, it is also not recommended from an auditing and troubleshooting perspective also. The request could have come from almost anywhere and it would have honoured the request provided the details were correct. To the SQL Server, the originator of the request is essentially unknown. What it does not have is the information about the calling application. the credentials for a successful SQL authenticationĪll of the above constitute required information, and includes all the essential information about the SQL Server instance.the database to use by default once the connection has been established and,.
If we try to highlight the different parts of the connection string, we see that we know the following: Provider=SQLNCLI10 Data Source=WINDOWS8RPSQL2K12 Initial Catalog=AdventureWorks2012 User ID=someuser Password=userpassword To most developers, a simple ADO connecting string would be something like: Connecting Strings have the power to influence: The connection string serves a purpose much greater than simply connecting the two together.
The glue that holds the connection between an application and a SQL Server instance is just a simple string, called the “connection string”.
0 kommentar(er)
