Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Problem with MSSQL 2008 and Windows & 64 bit.
- Thread starter SBTBILL
- Start date
Olaf Doschke
Programmer
What did you install?
SQL2008 or SQL2008R2?
An Instance or just the Installation Center?
Since 2008 you first install a "SQL Server Installation Center", not SQL Server itself. From that Installation Center you choose what to Install. If you Install an SQL Server instance, and don't just want to run your database instance on that Windows Server, but also IIS as a SQL Server Client application, you have to add "Client Tools Connectivity" form the "Shared Features" to install the ODBC drivers. A Server instance doesn't need ODBC driver, it is running the SQL Instance, which waits for ODBC connections. It does not install ODBC drivers for applications inclulding IIS to connect to it.
Besides that you also have to allow client connections. Since 2005 or even earlier, a new SQL Server instance installs pretty much shut down to only allow local connections via shared memory.
Find a decent installation howto, the problem is most probably not related to VFP at all. For example this should guide you through it:
See what you missed. If it turns out you don't learn anything new from this guide, then perhaps try to connect from SQL Server Management Studio, before trying to connect from VFP or VB or IIS. Management Studio is a best first check to do, as it also shows the inner meta data about system and user databases of the instance you connect to, so it's a best first client anyway, no matter what you use for further development.
Bye, Olaf.
SQL2008 or SQL2008R2?
An Instance or just the Installation Center?
Since 2008 you first install a "SQL Server Installation Center", not SQL Server itself. From that Installation Center you choose what to Install. If you Install an SQL Server instance, and don't just want to run your database instance on that Windows Server, but also IIS as a SQL Server Client application, you have to add "Client Tools Connectivity" form the "Shared Features" to install the ODBC drivers. A Server instance doesn't need ODBC driver, it is running the SQL Instance, which waits for ODBC connections. It does not install ODBC drivers for applications inclulding IIS to connect to it.
Besides that you also have to allow client connections. Since 2005 or even earlier, a new SQL Server instance installs pretty much shut down to only allow local connections via shared memory.
Find a decent installation howto, the problem is most probably not related to VFP at all. For example this should guide you through it:
See what you missed. If it turns out you don't learn anything new from this guide, then perhaps try to connect from SQL Server Management Studio, before trying to connect from VFP or VB or IIS. Management Studio is a best first check to do, as it also shows the inner meta data about system and user databases of the instance you connect to, so it's a best first client anyway, no matter what you use for further development.
Bye, Olaf.
- Thread starter
- #3
Dan Freeman
Programmer
What have you tried and what error message(s) do you get?
ADO and ODBC are very different animals and not in any way connected to each other. However, Microsoft has announced they are deprecating OLEDB (the technology underlying ADO) in favor or ODBC. So, you should be looking at using ODBC if possible.
Craig Berntson
MCSD, Visual C# MVP,
Craig Berntson
MCSD, Visual C# MVP,
- Status
Similar threads
