Our current program use ADO to connect oto SQL2000 and run fine.
We are planning to migrate to SQL2005.
When we clean install the SQL2005, create the database, set compatibility
level to 80 and generate the db structure, and migrate data.
When everything is done, we try to use our program to connect to SQL2005
database and find the connection fail.
Even when we use sa as login user and still fail to connect.
Is there any different in connection for SQL2000 & SQL2005?
I remember I have tried upgrade SQL2000 to SQL2005 before and the connection
had no problem to sql2005.
Is there something I forgot to set?
KanAm Tue, 29 Aug 2006 17:38:51 +0800 schrieb Ivan:
> Our current program use ADO to connect oto SQL2000 and run fine.
> We are planning to migrate to SQL2005.
> When we clean install the SQL2005, create the database, set compatibility
> level to 80 and generate the db structure, and migrate data.
> When everything is done, we try to use our program to connect to SQL2005
> database and find the connection fail.
> Even when we use sa as login user and still fail to connect.
> Is there any different in connection for SQL2000 & SQL2005?
> I remember I have tried upgrade SQL2000 to SQL2005 before and the connecti
on
> had no problem to sql2005.
> Is there something I forgot to set?
> Kan
If you did a standard installation then SQL2005 uses the named instance
SQLExpress wich you have to use in your connect string.
If your SQL2005 runs on the same machine as your SQL2000 then maybe SQL2005
listen on another port than the standard port.
And have you allowed remote access in SQL2005?
bye, Helmut|||No, MDAC will work fine with the SQL Server 2005 instance. Although you
can=B4t use some of the new cool features its compatible. Which error do
you get ? Is the SQL Server 2k5 located on the same machine as the 2k
instance ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment