|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
testing 2000 to 2005 update
I think I remember hearing about something that could test a SQL 2000 db
after it's been attached to SQL 2005 server to be sure there are no funny things in the db that will cause problems in 2005 (especially coding issues in procedures and triggers). Is there such thing out there? If so what? I'm moving a client's 2000 db over to their new 2005 installation. I already did this on my test system and it seems fine. I need to do some more testing via the front end but wondering about something that could be used to test the entire db. Thanks, Keith You're looking for "SQL Server Upgrade Advisor". There are both 2005
and 2008 versions, so be careful to download the right version. It is downloadable from MS (and also should be on 2005 CD). -- Show quoteHide quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Keith G Hicks" <k**@comcast.net> wrote in message news:uvxE0Y6XJHA.2280@TK2MSFTNGP06.phx.gbl... >I think I remember hearing about something that could test a SQL 2000 >db > after it's been attached to SQL 2005 server to be sure there are no > funny > things in the db that will cause problems in 2005 (especially coding > issues > in procedures and triggers). Is there such thing out there? If so > what? I'm moving a client's 2000 db over to their new 2005 > installation. I already did this on my test system and it seems > fine. I need to do some more testing via the front end but wondering > about something that could be used to test the entire db. > > Thanks, > > Keith > > > Thanks. :)
Show quoteHide quote "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> wrote in message news:eogxFf6XJHA.1528@TK2MSFTNGP03.phx.gbl... > You're looking for "SQL Server Upgrade Advisor". There are both 2005 and > 2008 versions, so be careful to download the right version. It is > downloadable from MS (and also should be on 2005 CD). > > -- > Tibor Karaszi, SQL Server MVP > http://www.karaszi.com/sqlserver/default.asp > http://sqlblog.com/blogs/tibor_karaszi > > I installed and tried to run the 2005 SQL Server Upgrade Advisor. I chose to
test SQL Server. I clicked "next". The Server Name is correct. The instance name is "MSSQLSERVER" which as far as I can tell is correct (it's the only choice in the dropdown). I tried both Windows Authentication and SQL Authentication. I am able to connect to my SQL 2000 databases through ODBC, Access, VB, etc. Not a problem with any of those. But when I try to use the upgrade advisor I get this error: Unable to connect to server. Reason: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) SQL 2000 is running. What could be the possible reasons for this? Keith Show quoteHide quote "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> wrote in message news:eogxFf6XJHA.1528@TK2MSFTNGP03.phx.gbl... > You're looking for "SQL Server Upgrade Advisor". There are both 2005 and > 2008 versions, so be careful to download the right version. It is > downloadable from MS (and also should be on 2005 CD). > > -- > Tibor Karaszi, SQL Server MVP > http://www.karaszi.com/sqlserver/default.asp > http://sqlblog.com/blogs/tibor_karaszi > > > "Keith G Hicks" <k**@comcast.net> wrote in message > news:uvxE0Y6XJHA.2280@TK2MSFTNGP06.phx.gbl... >>I think I remember hearing about something that could test a SQL 2000 db >> after it's been attached to SQL 2005 server to be sure there are no funny >> things in the db that will cause problems in 2005 (especially coding >> issues >> in procedures and triggers). Is there such thing out there? If so what? >> I'm moving a client's 2000 db over to their new 2005 installation. I >> already did this on my test system and it seems fine. I need to do some >> more testing via the front end but wondering about something that could >> be used to test the entire db. >> >> Thanks, >> >> Keith >> >> >> > > Should have mentioned that "alllow remote connections" is checked.
Show quoteHide quote "Keith G Hicks" <k**@comcast.net> wrote in message news:ugbkO%23EYJHA.652@TK2MSFTNGP04.phx.gbl... >I installed and tried to run the 2005 SQL Server Upgrade Advisor. I chose >to test SQL Server. I clicked "next". The Server Name is correct. The >instance name is "MSSQLSERVER" which as far as I can tell is correct (it's >the only choice in the dropdown). I tried both Windows Authentication and >SQL Authentication. I am able to connect to my SQL 2000 databases through >ODBC, Access, VB, etc. Not a problem with any of those. But when I try to >use the upgrade advisor I get this error: > > Unable to connect to server. Reason: A network-related or > instance-specific error occurred while establishing a connection to SQL > Server. The server was not found or was not accessible. Verify that the > instance name is correct and that SQL Server is configured to allow remote > connections. (provider: TCP Provider, error: 0 - No connection could be > made because the target machine actively refused it.) > > SQL 2000 is running. What could be the possible reasons for this? > > Keith > > "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> wrote > in message news:eogxFf6XJHA.1528@TK2MSFTNGP03.phx.gbl... >> You're looking for "SQL Server Upgrade Advisor". There are both 2005 and >> 2008 versions, so be careful to download the right version. It is >> downloadable from MS (and also should be on 2005 CD). >> >> -- >> Tibor Karaszi, SQL Server MVP >> http://www.karaszi.com/sqlserver/default.asp >> http://sqlblog.com/blogs/tibor_karaszi >> >> >> "Keith G Hicks" <k**@comcast.net> wrote in message >> news:uvxE0Y6XJHA.2280@TK2MSFTNGP06.phx.gbl... >>>I think I remember hearing about something that could test a SQL 2000 db >>> after it's been attached to SQL 2005 server to be sure there are no >>> funny >>> things in the db that will cause problems in 2005 (especially coding >>> issues >>> in procedures and triggers). Is there such thing out there? If so what? >>> I'm moving a client's 2000 db over to their new 2005 installation. I >>> already did this on my test system and it seems fine. I need to do some >>> more testing via the front end but wondering about something that could >>> be used to test the entire db. >>> >>> Thanks, >>> >>> Keith >>> >>> >>> >> >> > > > The instance name is "MSSQLSERVER" which as far as I can tell is I never trust any type of drop-down boxes. I always type the machine > correct (it's the only choice in the dropdown). and possibly instance names. I suggest you first make 100% positive what the machine and instance name you connect to is correct. And then verify using some type of SQL Server tool (connecting from the same client machine) - be it QA, SSMS, OSQL.EXE or SQLCMD.EXE. Also, it can be worth checking the errorlog of there is any details about the failed login. -- Show quoteHide quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Keith G Hicks" <k**@comcast.net> wrote in message news:ugbkO%23EYJHA.652@TK2MSFTNGP04.phx.gbl... >I installed and tried to run the 2005 SQL Server Upgrade Advisor. I >chose to test SQL Server. I clicked "next". The Server Name is >correct. The instance name is "MSSQLSERVER" which as far as I can >tell is correct (it's the only choice in the dropdown). I tried both >Windows Authentication and SQL Authentication. I am able to connect >to my SQL 2000 databases through ODBC, Access, VB, etc. Not a problem >with any of those. But when I try to use the upgrade advisor I get >this error: > > Unable to connect to server. Reason: A network-related or > instance-specific error occurred while establishing a connection to > SQL Server. The server was not found or was not accessible. Verify > that the instance name is correct and that SQL Server is configured > to allow remote connections. (provider: TCP Provider, error: 0 - No > connection could be made because the target machine actively refused > it.) > > SQL 2000 is running. What could be the possible reasons for this? > > Keith > > "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> > wrote in message news:eogxFf6XJHA.1528@TK2MSFTNGP03.phx.gbl... >> You're looking for "SQL Server Upgrade Advisor". There are both >> 2005 and 2008 versions, so be careful to download the right >> version. It is downloadable from MS (and also should be on 2005 >> CD). >> >> -- >> Tibor Karaszi, SQL Server MVP >> http://www.karaszi.com/sqlserver/default.asp >> http://sqlblog.com/blogs/tibor_karaszi >> >> >> "Keith G Hicks" <k**@comcast.net> wrote in message >> news:uvxE0Y6XJHA.2280@TK2MSFTNGP06.phx.gbl... >>>I think I remember hearing about something that could test a SQL >>>2000 db >>> after it's been attached to SQL 2005 server to be sure there are >>> no funny >>> things in the db that will cause problems in 2005 (especially >>> coding issues >>> in procedures and triggers). Is there such thing out there? If so >>> what? I'm moving a client's 2000 db over to their new 2005 >>> installation. I already did this on my test system and it seems >>> fine. I need to do some more testing via the front end but >>> wondering about something that could be used to test the entire >>> db. >>> >>> Thanks, >>> >>> Keith >>> >>> >>> >> >> > > I agree (about the dropdown). I've tried all that. I know my server name and
instance name are correct (default instance). I've confirmed that. I should also mention that I tried this with my firewall turned off. Running all this on XP pro SP3 and SQL 2000 is on SP4. WHen I click the "detect" button it does detect that I have SLQ Server and DTS. So something's workign right. Which error log and where? I also do *not* have SQL set to the defualt port (1433 I think) if that matters. Show quoteHide quote "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> wrote in message news:OqYPqRFYJHA.5388@TK2MSFTNGP05.phx.gbl... >> The instance name is "MSSQLSERVER" which as far as I can tell is correct >> (it's the only choice in the dropdown). > > I never trust any type of drop-down boxes. I always type the machine and > possibly instance names. I suggest you first make 100% positive what the > machine and instance name you connect to is correct. And then verify using > some type of SQL Server tool (connecting from the same client machine) - > be it QA, SSMS, OSQL.EXE or SQLCMD.EXE. Also, it can be worth checking the > errorlog of there is any details about the failed login. > > -- > Tibor Karaszi, SQL Server MVP > http://www.karaszi.com/sqlserver/default.asp > http://sqlblog.com/blogs/tibor_karaszi > > > "Keith G Hicks" <k**@comcast.net> wrote in message > news:ugbkO%23EYJHA.652@TK2MSFTNGP04.phx.gbl... >>I installed and tried to run the 2005 SQL Server Upgrade Advisor. I chose >>to test SQL Server. I clicked "next". The Server Name is correct. The >>instance name is "MSSQLSERVER" which as far as I can tell is correct (it's >>the only choice in the dropdown). I tried both Windows Authentication and >>SQL Authentication. I am able to connect to my SQL 2000 databases through >>ODBC, Access, VB, etc. Not a problem with any of those. But when I try to >>use the upgrade advisor I get this error: >> >> Unable to connect to server. Reason: A network-related or >> instance-specific error occurred while establishing a connection to SQL >> Server. The server was not found or was not accessible. Verify that the >> instance name is correct and that SQL Server is configured to allow >> remote connections. (provider: TCP Provider, error: 0 - No connection >> could be made because the target machine actively refused it.) >> >> SQL 2000 is running. What could be the possible reasons for this? >> >> Keith >> >> "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> wrote >> in message news:eogxFf6XJHA.1528@TK2MSFTNGP03.phx.gbl... >>> You're looking for "SQL Server Upgrade Advisor". There are both 2005 and >>> 2008 versions, so be careful to download the right version. It is >>> downloadable from MS (and also should be on 2005 CD). >>> >>> -- >>> Tibor Karaszi, SQL Server MVP >>> http://www.karaszi.com/sqlserver/default.asp >>> http://sqlblog.com/blogs/tibor_karaszi >>> >>> >>> "Keith G Hicks" <k**@comcast.net> wrote in message >>> news:uvxE0Y6XJHA.2280@TK2MSFTNGP06.phx.gbl... >>>>I think I remember hearing about something that could test a SQL 2000 db >>>> after it's been attached to SQL 2005 server to be sure there are no >>>> funny >>>> things in the db that will cause problems in 2005 (especially coding >>>> issues >>>> in procedures and triggers). Is there such thing out there? If so what? >>>> I'm moving a client's 2000 db over to their new 2005 installation. I >>>> already did this on my test system and it seems fine. I need to do some >>>> more testing via the front end but wondering about something that could >>>> be used to test the entire db. >>>> >>>> Thanks, >>>> >>>> Keith >>>> >>>> >>>> >>> >>> >> >> > > I'm running SQL 8.00.2039 which is SP4. I just tried running the tool on my
client's server and it worked. It turns out that they're running 8.00.2050 which must include some newer updates. Not sure if that's causing the problem. But since I can run it on their system I'm not really concerned about running it on mine now although it would be nice if I could solve this. If not, no biggie for now. Show quoteHide quote "Keith G Hicks" <k**@comcast.net> wrote in message news:%23r7wnrFYJHA.4852@TK2MSFTNGP04.phx.gbl... >I agree (about the dropdown). I've tried all that. I know my server name >and instance name are correct (default instance). I've confirmed that. I >should also mention that I tried this with my firewall turned off. Running >all this on XP pro SP3 and SQL 2000 is on SP4. WHen I click the "detect" >button it does detect that I have SLQ Server and DTS. So something's >workign right. Which error log and where? I also do *not* have SQL set to >the defualt port (1433 I think) if that matters. > > > "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> wrote > in message news:OqYPqRFYJHA.5388@TK2MSFTNGP05.phx.gbl... >>> The instance name is "MSSQLSERVER" which as far as I can tell is correct >>> (it's the only choice in the dropdown). >> >> I never trust any type of drop-down boxes. I always type the machine and >> possibly instance names. I suggest you first make 100% positive what the >> machine and instance name you connect to is correct. And then verify >> using some type of SQL Server tool (connecting from the same client >> machine) - be it QA, SSMS, OSQL.EXE or SQLCMD.EXE. Also, it can be worth >> checking the errorlog of there is any details about the failed login. >> >> -- >> Tibor Karaszi, SQL Server MVP >> http://www.karaszi.com/sqlserver/default.asp >> http://sqlblog.com/blogs/tibor_karaszi >> >> >> "Keith G Hicks" <k**@comcast.net> wrote in message >> news:ugbkO%23EYJHA.652@TK2MSFTNGP04.phx.gbl... >>>I installed and tried to run the 2005 SQL Server Upgrade Advisor. I chose >>>to test SQL Server. I clicked "next". The Server Name is correct. The >>>instance name is "MSSQLSERVER" which as far as I can tell is correct >>>(it's the only choice in the dropdown). I tried both Windows >>>Authentication and SQL Authentication. I am able to connect to my SQL >>>2000 databases through ODBC, Access, VB, etc. Not a problem with any of >>>those. But when I try to use the upgrade advisor I get this error: >>> >>> Unable to connect to server. Reason: A network-related or >>> instance-specific error occurred while establishing a connection to SQL >>> Server. The server was not found or was not accessible. Verify that the >>> instance name is correct and that SQL Server is configured to allow >>> remote connections. (provider: TCP Provider, error: 0 - No connection >>> could be made because the target machine actively refused it.) >>> >>> SQL 2000 is running. What could be the possible reasons for this? >>> >>> Keith >>> >>> "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> wrote >>> in message news:eogxFf6XJHA.1528@TK2MSFTNGP03.phx.gbl... >>>> You're looking for "SQL Server Upgrade Advisor". There are both 2005 >>>> and 2008 versions, so be careful to download the right version. It is >>>> downloadable from MS (and also should be on 2005 CD). >>>> >>>> -- >>>> Tibor Karaszi, SQL Server MVP >>>> http://www.karaszi.com/sqlserver/default.asp >>>> http://sqlblog.com/blogs/tibor_karaszi >>>> >>>> >>>> "Keith G Hicks" <k**@comcast.net> wrote in message >>>> news:uvxE0Y6XJHA.2280@TK2MSFTNGP06.phx.gbl... >>>>>I think I remember hearing about something that could test a SQL 2000 >>>>>db >>>>> after it's been attached to SQL 2005 server to be sure there are no >>>>> funny >>>>> things in the db that will cause problems in 2005 (especially coding >>>>> issues >>>>> in procedures and triggers). Is there such thing out there? If so >>>>> what? I'm moving a client's 2000 db over to their new 2005 >>>>> installation. I already did this on my test system and it seems fine. >>>>> I need to do some more testing via the front end but wondering about >>>>> something that could be used to test the entire db. >>>>> >>>>> Thanks, >>>>> >>>>> Keith >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > Well I updated my SQL 2000 installation to 8.00.2187 and still can't run the
Upgrade Advisor tool on my development system. Show quoteHide quote "Keith G Hicks" <k**@comcast.net> wrote in message news:%23pGk0PIYJHA.4852@TK2MSFTNGP04.phx.gbl... > I'm running SQL 8.00.2039 which is SP4. I just tried running the tool on > my client's server and it worked. It turns out that they're running > 8.00.2050 which must include some newer updates. Not sure if that's > causing the problem. But since I can run it on their system I'm not really > concerned about running it on mine now although it would be nice if I > could solve this. If not, no biggie for now. > > > "Keith G Hicks" <k**@comcast.net> wrote in message > news:%23r7wnrFYJHA.4852@TK2MSFTNGP04.phx.gbl... >>I agree (about the dropdown). I've tried all that. I know my server name >>and instance name are correct (default instance). I've confirmed that. I >>should also mention that I tried this with my firewall turned off. Running >>all this on XP pro SP3 and SQL 2000 is on SP4. WHen I click the "detect" >>button it does detect that I have SLQ Server and DTS. So something's >>workign right. Which error log and where? I also do *not* have SQL set to >>the defualt port (1433 I think) if that matters. >> >> >> "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> wrote >> in message news:OqYPqRFYJHA.5388@TK2MSFTNGP05.phx.gbl... >>>> The instance name is "MSSQLSERVER" which as far as I can tell is >>>> correct (it's the only choice in the dropdown). >>> >>> I never trust any type of drop-down boxes. I always type the machine and >>> possibly instance names. I suggest you first make 100% positive what the >>> machine and instance name you connect to is correct. And then verify >>> using some type of SQL Server tool (connecting from the same client >>> machine) - be it QA, SSMS, OSQL.EXE or SQLCMD.EXE. Also, it can be worth >>> checking the errorlog of there is any details about the failed login. >>> >>> -- >>> Tibor Karaszi, SQL Server MVP >>> http://www.karaszi.com/sqlserver/default.asp >>> http://sqlblog.com/blogs/tibor_karaszi >>> >>> >>> "Keith G Hicks" <k**@comcast.net> wrote in message >>> news:ugbkO%23EYJHA.652@TK2MSFTNGP04.phx.gbl... >>>>I installed and tried to run the 2005 SQL Server Upgrade Advisor. I >>>>chose to test SQL Server. I clicked "next". The Server Name is correct. >>>>The instance name is "MSSQLSERVER" which as far as I can tell is correct >>>>(it's the only choice in the dropdown). I tried both Windows >>>>Authentication and SQL Authentication. I am able to connect to my SQL >>>>2000 databases through ODBC, Access, VB, etc. Not a problem with any of >>>>those. But when I try to use the upgrade advisor I get this error: >>>> >>>> Unable to connect to server. Reason: A network-related or >>>> instance-specific error occurred while establishing a connection to SQL >>>> Server. The server was not found or was not accessible. Verify that the >>>> instance name is correct and that SQL Server is configured to allow >>>> remote connections. (provider: TCP Provider, error: 0 - No connection >>>> could be made because the target machine actively refused it.) >>>> >>>> SQL 2000 is running. What could be the possible reasons for this? >>>> >>>> Keith >>>> >>>> "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> >>>> wrote in message news:eogxFf6XJHA.1528@TK2MSFTNGP03.phx.gbl... >>>>> You're looking for "SQL Server Upgrade Advisor". There are both 2005 >>>>> and 2008 versions, so be careful to download the right version. It is >>>>> downloadable from MS (and also should be on 2005 CD). >>>>> >>>>> -- >>>>> Tibor Karaszi, SQL Server MVP >>>>> http://www.karaszi.com/sqlserver/default.asp >>>>> http://sqlblog.com/blogs/tibor_karaszi >>>>> >>>>> >>>>> "Keith G Hicks" <k**@comcast.net> wrote in message >>>>> news:uvxE0Y6XJHA.2280@TK2MSFTNGP06.phx.gbl... >>>>>>I think I remember hearing about something that could test a SQL 2000 >>>>>>db >>>>>> after it's been attached to SQL 2005 server to be sure there are no >>>>>> funny >>>>>> things in the db that will cause problems in 2005 (especially coding >>>>>> issues >>>>>> in procedures and triggers). Is there such thing out there? If so >>>>>> what? I'm moving a client's 2000 db over to their new 2005 >>>>>> installation. I already did this on my test system and it seems fine. >>>>>> I need to do some more testing via the front end but wondering about >>>>>> something that could be used to test the entire db. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Keith >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > OK. I changed my SQL port to 1433 and could get to the 2nd page of the
Advisor. But when I try to run it (when I click the actual "Run" button) I get an error that wants to be sent to Microsoft. I went ahead and let it do that. Then I ran it again and decided to see what would happen if I let it go to VS 2008 debugger. Here's the error that I got: Could not load file or assembly 'BPAClient, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. Here's the answer I found: http://social.msdn.microsoft.com/forums/en-US/sqlsetupandupgrade/thread/2a5f460b-8684-4510-8fcb-1e9d9786baff/ I did what the person suggested and it seems to work now. Yeah, thanks for making that easy Microsoft!!!!! LOL. What a joke. So there's nothing in the help about port having to be 1433 either. Give me a break. Show quoteHide quote "Keith G Hicks" <k**@comcast.net> wrote in message news:ucHg6QLYJHA.4072@TK2MSFTNGP02.phx.gbl... > Well I updated my SQL 2000 installation to 8.00.2187 and still can't run > the Upgrade Advisor tool on my development system. > > > "Keith G Hicks" <k**@comcast.net> wrote in message > news:%23pGk0PIYJHA.4852@TK2MSFTNGP04.phx.gbl... >> I'm running SQL 8.00.2039 which is SP4. I just tried running the tool on >> my client's server and it worked. It turns out that they're running >> 8.00.2050 which must include some newer updates. Not sure if that's >> causing the problem. But since I can run it on their system I'm not >> really concerned about running it on mine now although it would be nice >> if I could solve this. If not, no biggie for now. >> >> >> "Keith G Hicks" <k**@comcast.net> wrote in message >> news:%23r7wnrFYJHA.4852@TK2MSFTNGP04.phx.gbl... >>>I agree (about the dropdown). I've tried all that. I know my server name >>>and instance name are correct (default instance). I've confirmed that. I >>>should also mention that I tried this with my firewall turned off. >>>Running all this on XP pro SP3 and SQL 2000 is on SP4. WHen I click the >>>"detect" button it does detect that I have SLQ Server and DTS. So >>>something's workign right. Which error log and where? I also do *not* >>>have SQL set to the defualt port (1433 I think) if that matters. >>> >>> >>> "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> wrote >>> in message news:OqYPqRFYJHA.5388@TK2MSFTNGP05.phx.gbl... >>>>> The instance name is "MSSQLSERVER" which as far as I can tell is >>>>> correct (it's the only choice in the dropdown). >>>> >>>> I never trust any type of drop-down boxes. I always type the machine >>>> and possibly instance names. I suggest you first make 100% positive >>>> what the machine and instance name you connect to is correct. And then >>>> verify using some type of SQL Server tool (connecting from the same >>>> client machine) - be it QA, SSMS, OSQL.EXE or SQLCMD.EXE. Also, it can >>>> be worth checking the errorlog of there is any details about the failed >>>> login. >>>> >>>> -- >>>> Tibor Karaszi, SQL Server MVP >>>> http://www.karaszi.com/sqlserver/default.asp >>>> http://sqlblog.com/blogs/tibor_karaszi >>>> >>>> >>>> "Keith G Hicks" <k**@comcast.net> wrote in message >>>> news:ugbkO%23EYJHA.652@TK2MSFTNGP04.phx.gbl... >>>>>I installed and tried to run the 2005 SQL Server Upgrade Advisor. I >>>>>chose to test SQL Server. I clicked "next". The Server Name is correct. >>>>>The instance name is "MSSQLSERVER" which as far as I can tell is >>>>>correct (it's the only choice in the dropdown). I tried both Windows >>>>>Authentication and SQL Authentication. I am able to connect to my SQL >>>>>2000 databases through ODBC, Access, VB, etc. Not a problem with any of >>>>>those. But when I try to use the upgrade advisor I get this error: >>>>> >>>>> Unable to connect to server. Reason: A network-related or >>>>> instance-specific error occurred while establishing a connection to >>>>> SQL Server. The server was not found or was not accessible. Verify >>>>> that the instance name is correct and that SQL Server is configured to >>>>> allow remote connections. (provider: TCP Provider, error: 0 - No >>>>> connection could be made because the target machine actively refused >>>>> it.) >>>>> >>>>> SQL 2000 is running. What could be the possible reasons for this? >>>>> >>>>> Keith >>>>> >>>>> "Tibor Karaszi" <tibor_please.no.email_kara***@hotmail.nomail.com> >>>>> wrote in message news:eogxFf6XJHA.1528@TK2MSFTNGP03.phx.gbl... >>>>>> You're looking for "SQL Server Upgrade Advisor". There are both 2005 >>>>>> and 2008 versions, so be careful to download the right version. It is >>>>>> downloadable from MS (and also should be on 2005 CD). >>>>>> >>>>>> -- >>>>>> Tibor Karaszi, SQL Server MVP >>>>>> http://www.karaszi.com/sqlserver/default.asp >>>>>> http://sqlblog.com/blogs/tibor_karaszi >>>>>> >>>>>> >>>>>> "Keith G Hicks" <k**@comcast.net> wrote in message >>>>>> news:uvxE0Y6XJHA.2280@TK2MSFTNGP06.phx.gbl... >>>>>>>I think I remember hearing about something that could test a SQL 2000 >>>>>>>db >>>>>>> after it's been attached to SQL 2005 server to be sure there are no >>>>>>> funny >>>>>>> things in the db that will cause problems in 2005 (especially coding >>>>>>> issues >>>>>>> in procedures and triggers). Is there such thing out there? If so >>>>>>> what? I'm moving a client's 2000 db over to their new 2005 >>>>>>> installation. I already did this on my test system and it seems >>>>>>> fine. I need to do some more testing via the front end but wondering >>>>>>> about something that could be used to test the entire db. >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Keith >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >  
Other interesting topics
Problems with NOEXPAND
Partial restore without restoring PRIMARY FG Transaction Log Backups Using xp_delete_file to delete rar files selective application of condition in an SQL querry NVARCHAR Limit sql2005 log file is full Lost product key sql server 2005 different sql server 2000 I don't want my DML queries to wait until lock is released, insteadd I want my DML to abort |
|||||||||||||||||||||||
