Migration SQL2000 to SQL2005

[Lorenzo Soncini]

For some customer we plan a Sql Server Migration but in our test all the
application build with .NET 1.1 don't access the new SQL Server 2005.
We have tested the creation in a VS2003 a new connection to the SQL server
2005 database but allso this connection fail.
From the same machine if we use VS2005 all work fine.

The applicazion using SQLServer of the .NET 1.1 framework is compatible with
the new server SQL Server 2005 as backend database?
Any other have this problem or an idea for solution ?

Lorenzo Soncini

 

[David Browne]

For some customer we plan a Sql Server Migration but in our test all the
application build with .NET 1.1 don't access the new SQL Server 2005.
We have tested the creation in a VS2003 a new connection to the SQL server
2005 database but allso this connection fail.
From the same machine if we use VS2005 all work fine.

The applicazion using SQLServer of the .NET 1.1 framework is compatible
with the new server SQL Server 2005 as backend database?
Any other have this problem or an idea for solution ?

It should work fine. Check your SQL Server 2005 install to make sure that
network access is enabled (some editions have it off by default).

David

 

[Cowboy \(Gregory A. Beamer\)]

The SQL Browser is turned off by default. Make sure it is on. That should
have also bombed out VS 2005, I believe, but that is step 1.

Make sure you have the proper network protocols setup for legacy access. By
default, I think you are only using native client in VS 2005 (you can check
this), so the access method is a bit different.

Once you have those set up, you should be fine. (great, another document to
add to my migration docs *sigh*)

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************