|
|||
|
|
|
| Home |
| About |
| Hobbies |
| Software |
| Hardware |
| ICT Hotlist |
| Purpose |
React:
ICT-Hotlist Topic
Back to the ICT-Hotlist...Add System DSN
The registry file below creates an ODBC System DSN to the MS-SQL database server "DBServer1". The ODBC connector is formatted as "ODBC_<DatabaseType>_<DatabaseServer>" that results in "ODBC_SQL2005_DBServer1"Warning:This solution modifies the Windows registry. Back up the registry before you modify it. Then, you can restore the registry if a problem occurs.
Windows Registry Editor Version 5.00
;*********************************************************************
;* This file creates the File DSN ODBC entries for a MS-SQL database.
;* Just doubleclick it and select "Yes" and "Ok" or run it silent as:
;* regedit.exe /s Add_System_DSN.reg
;*
;* (C)Copyright 2009-2024 Johan van Soest http://www.vansoest.it/
;*********************************************************************
; *** Just setting the correct node
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI]
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
; *** Define the new DataSourceName
"ODBC_SQL2005_DBServer1"="SQL Server"
; *** Defining the actual ODBC Connection
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC_SQL2005_DBServer1]
; *** Specify the full path to the SQL server Driver
; *** Attention: change to M: for Citrix farm servers
"Driver"="C:\\WINDOWS\\system32\\SQLSRV32.dll"
; *** Give a human readable description for use in ODBC control, Excel etc.
"Description"="ODBC_SQL2005_DBServer1"
; *** Use ServerName\InstanceName to connect to the instance otherwise
; *** ServerName of the database server is sufficient
"Server"="DBServer1"
; *** Using Windows account to log on to the database (permissions
; *** must be set in database!)
"Trusted_Connection"="Yes"
;*********************************************************************
;* This file creates the File DSN ODBC entries for a MS-SQL database.
;* Just doubleclick it and select "Yes" and "Ok" or run it silent as:
;* regedit.exe /s Add_System_DSN.reg
;*
;* (C)Copyright 2009-2024 Johan van Soest http://www.vansoest.it/
;*********************************************************************
; *** Just setting the correct node
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI]
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
; *** Define the new DataSourceName
"ODBC_SQL2005_DBServer1"="SQL Server"
; *** Defining the actual ODBC Connection
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC_SQL2005_DBServer1]
; *** Specify the full path to the SQL server Driver
; *** Attention: change to M: for Citrix farm servers
"Driver"="C:\\WINDOWS\\system32\\SQLSRV32.dll"
; *** Give a human readable description for use in ODBC control, Excel etc.
"Description"="ODBC_SQL2005_DBServer1"
; *** Use ServerName\InstanceName to connect to the instance otherwise
; *** ServerName of the database server is sufficient
"Server"="DBServer1"
; *** Using Windows account to log on to the database (permissions
; *** must be set in database!)
"Trusted_Connection"="Yes"
You may vote your opinion about this article:
Scripts and programming examples disclaimer
Unless stated otherwise, the script sources and programming examples provided are copyrighted freeware. You may modify them, as long as a reference to the original code and hyperlink to the source page is included in the modified code and documentation. However, it is not allowed to publish (copies of) scripts and programming examples on your own site, blog, vlog, or distribute them on paper or any other medium, without prior written consent.Many of the techniques used in these scripts, including but not limited to modifying the registry or system files and settings, impose a risk of rendering the Operating System inoperable and loss of data. Make sure you have verified full backups and the associated restore software available before running any script or programming example. Use these scripts and programming examples entirely at your own risk. All liability claims against the author in relation to material or non-material losses caused by the use, misuse or non-use of the information provided, or the use of incorrect or incomplete information, are excluded. All content is subject to change and provided without obligation.
