"InstanceAPIPath"="C:\\Program Files\\Microsoft SQL Server\\130\\LocalDB\\Binn\\SqlUserInstance.dll"] "InstanceAPIPath"="C:\\Program Files\\Microsoft SQL Server\\130\\LocalDB\\Binn\\SqlUserInstance.dll" The following example shows the registry entries for a computer that has LocalDB versions 11.0 and 13.0 installed: Under each version key there is an InstanceAPIPath name-value pair that defines the full path to the SQLUserInstance.dll file installed with that version. (for example, the key for SQL Server 2014 (12.x) is named 13.0). Each of these keys is named with the LocalDB version number in the format. Under this key there is a list of keys, one for each version of LocalDB installed on the computer. To locate the SQLUserInstance DLL, the client provider uses the following registry key: However, user code always uses the latest available SQLUserInstance DLL on the local computer to connect to LocalDB instances. Multiple LocalDB versions on the same workstation are supported side-by-side. The version for the LocalDB installation is defined in the MSSQLServer\CurrentVersion registry key under the SQL Server instance registry key, for example: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL13E.LOCALDB\ MSSQLServer\CurrentVersion: "CurrentVersion"=".0" This means that if the user specifies only "12.2" as the LocalDB version number, it will be treated as if the user specified "12.2.0.0". The last two numbers in the version string ( build and revision) are optional and default to zero if the user leaves them out. The first two numbers in the version string ( major and minor) are mandatory. The version is specified in the standard version format defined by the. This means that the user has to specify which LocalDB baseline release (that is, major SQL Server version) he or she will be using. These LocalDB versions are maintained and patched independently. The LocalDB installation uses a single set of binaries per major SQL Server version. To use the LocalDB instance API, you must include the sqlncli.h header file in your project. There is no separate header file for the SQL Server Express LocalDB instance API the LocalDB function signatures and error codes are defined in the SQL Server Native Client header file (sqlncli.h).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |