SQL Server 2000 connectionstrings
Her er en oversikt over ulike connectionstrings til SQL Server
ODBC
Standard sikkerhet
Driver={SQL Server};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Trusted connection
Driver={SQL Server};Server=myServerAddress;Database=myDataBase;Trusted_Connection=Yes;
OLE DB, OLE DB .NET
Standard sikkerhet
Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
Trusted connection
Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;
Tilkobling med IP adresse
Provider=sqloledb;Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;
SqlConnection .NET
Standard sikkerhet
Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
SERVER=databaseserver; Database=databasenavn; UID=brukernavn; Password=passord;
Trusted connection
Server=myServerAddress;Database=myDataBase;User ID=myUsername;Password=myPassword;Trusted_Connection=False;
Sql Server 2005
SQL Native Client ODBC Driver
Standard sikkerhet
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Trusted connection
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;
Kryptere data sent over nettverk
Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;Encrypt=yes;
SqlConnection .NET bruker sammen connectionstring som mot SQL Server 2000
Å bruke en connectionstring med brukernavn/passord har bedre ytelse enn en Trusted Connection, men en Trusted connection
er sikrere fordi man ikke sender brukernavnet og passord i strengen sammen med koblingen.
kilde connectionstrings.com