How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.
Solved
SQL2005 Ugrade Advisor will not Run
Posted on 2009-04-14
I have SQL2000 SP4 running on a single server and I would like to upgrade to SQL2005.
I have installed the SQL 2005 Upgrade Advisor on the server. It quits when it tries to analyze the SQL DB and says it cannot connect to the database.
It appears all the SQL Services are running, I have reinstalled the App., restarted the server but I cannot get the tool to run.
I have installed the SQL 2005 Upgrade Advisor on the server. It quits when it tries to analyze the SQL DB and says it cannot connect to the database.
It appears all the SQL Services are running, I have reinstalled the App., restarted the server but I cannot get the tool to run.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3 Comments
Active 3 days ago
Does it happen to be a named instance instead of the default? I have seen some discussion like this one at SQLServerCentral, http://www.sqlservercentral.com/Forums/Topic525884-146-1.aspx, which points to this one on msdn.blogs, http://www.sqlservercentral.com/Forums/Topic525884-146-1.aspx. The latter specifically had a comment that it was an "Absolutely useful post. Solved my porblem of connecting to SQL server 2000 through upgrade advisor." It looks like named instances can cause a problem possibly because of the switch to SQL Server Browser in 2005. Some possible solutions/work-arounds are to use the IP address or pretend it is the default instance and supply MSSQLSERVER as the instance name.
If this is not the answer, maybe give some more details of your setup and specific error messages and someone can key in on the problem.
If this is not the answer, maybe give some more details of your setup and specific error messages and someone can key in on the problem.
I am running the App. locally so I don't think Remote Access is going to come into play but yes Remote Access is enabled and I have tried it from another machine with the same results
It is running on the default instance (MSSQLSERVER). I can go thru all of the steps in the wizard and as soon as the tool runs it cannot connect to the DB
It is running on the default instance (MSSQLSERVER). I can go thru all of the steps in the wizard and as soon as the tool runs it cannot connect to the DB
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Why is this different from all of the other step by step guides? Because I make a living as a DBA and not as a writer and I lived through this experience.
Defining the name:
When I talk to people they say different names on this subject stuff l…
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Viewers will learn how the fundamental information of how to create a table.
Suggested Courses
Course of the Month7 days, 10 hours left to enroll
715 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.