A few days ago, a strange phenomenon occurred while installing SQL Server. When I installed the end of a sudden flash on nothing, I am happy to think that the installation is complete, but to the Start menu at all there is no SQL shadow, so I want to reinstall, but familiar with the SQL should know, If the installation is not finished properly, uninstalling is a very troublesome thing to reinstall.
So I started to reload, delete registry-delete file, after a bitter fight finally finished the above operation, restart after the installation, but the new problems appear again, installation prompts the wrong, is related to ODBC, I open ODBC a look inside SQL Server ODBC no longer exist, I went back to the latest version of the MDAC installation, but the problem remains, in fact, because my MDAC version is already up to date, the reload MDAC simply shows the installation complete, but in fact nothing has been done.
At that time searched KB also did not find the installation of ODBC driver related content, almost the operating system reinstall.
In fact, we just need to use Odbcconf.exe to re-register the ODBC driver.
There are several script files under the Windows/system32 directory that can be used to complete the registration of the driver:
odbcconf.exe/s/lv odbcconf.log/f%SYSTEMROOT%/SYSTEM32/MDACCORE.RSP
odbcconf.exe/s/lv odbcconf.log/f%SYSTEMROOT%/SYSTEM32/SQLCLNT.RSP
odbcconf.exe/s/lv odbcconf.log/f%SYSTEMROOT%/SYSTEM32/ODBCCONF.RSP
odbcconf.exe/s/lv odbcconf.log/f%SYSTEMROOT%/SYSTEM32/REDIST.RSP
This problem arises because some programs that use ODBC data sources remove the ODBC driver information when they uninstall. ODBC is OK, but again the same problem occurs with the first time you reload SQL, I started a little discouraged, and then I put the installation disk into the look, I found that there is an advanced option to install, I point to see the Rebuild registry options, so I backed up a copy of the registry, Select this option and do it again, and this time my SQL can be used. Happy for several days.
This problem is estimated to have previously been installed in SQL, but the uninstall is not clean, the registry has some options to affect the normal installation of SQL.