Hello,
I am after a bit of advice about running the Upgrade Advisor tool on a server that has more than 1 SQL Server instance. My particular focus is DTS on each server.
I tried running the tool, setting up an XML file per SQL Server (including named instances). An example of the XML is I used is included below):
<Configuration> <Server>SQL01</Server> <Instance>INSTANCE01</Instance> <Components> <DataTransformationServices /> </Components></Configuration>
When the tool runs, folders get created for the relevant named instances, but the DTS runs against the default instance only. In other words, the default instance DTS.xml file gets overwritten several times.
Does anyone know if the Upgrade Advisor tool can handle multiple SQL instances on the same server, particularly in realtion to DTS?
I had thought this might have been a limitation as the options in the Report Viewer are "Server" then "Instance or Component", when I am really after "Server", "Instance" AND "Component".
I had a server with SQL Server 7.0 I installed a named instance of SQL Server 2000 and then i passed all my DB of the 7.0 instance to the 2000 instance. Then i removed the 7.0 instance, that was the default instance. So at the moment there is only the 2000 version, but it isn't the default instance Can the 2000 instance become the default instance? (So that clients can connect to it simply through computer name, and not creating an alias)
We are performing a SQL 2005 SP1 upgrade from SQL 2000 on our Windows 2003 SP1 Standard Edition.
When we run the upgrade, we got a error "Upgrade Advisor Return -1" as a pop-up window.
When we run the Upgrade Advisor separately, we get this error :
===================================
Common Language Runtime detected an invalid program.
===================================
Common Language Runtime detected an invalid program. (System.Xml)
------------------------------ Program Location:
at System.Xml.Schema.SchemaInfo..ctor() at System.Xml.Schema.XmlSchemaSet..ctor(XmlNameTable nameTable) at System.Xml.XmlReaderSettings.get_Schemas() at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReportController.LoadAndValidateDataFile() at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReport.ValidateDataFile() at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAIssueReport.Refresh() at Microsoft.SqlServer.UpgradeAdvisor.ReportPanel.OpenReport(String reportFile)
We are in a lost for solutions. We do hope to hear from anyone asap...
I have a client whose DBA upgraded their SQL 2000 database to SQL 2005. They still have it running in 8.0 compatibility mode, for various reasons, and would like me to help them develop a migration strategy to get them to full 9.0 compatibility.
My question is: can I run the Upgrade Advisor on a SQL 2005 engine database running in 8.0 compatibility mode and get anything useful? I already know there will be some issues with existing DTS packages but it would be nice to catch any other issues in advance.
I know that the Upgrade Advisor was run before the upgrade took place but to my knowledge the report was not saved and none of the recommendations were followed.
I have a SQL server 2000 in development. it is running as an instance (servernameinstancename) with a TCP port configured. I can not connect to this server thru upgrade advisor wizard as well as by using command line utility. Can some help me understand how can I connect to sql server 2000 name instance and run upgrade advisor on it.
Here are the steps I have taken:
created config.xml as below:
<Configuration> <Server>servername</Server> <Instance>D15</Instance> <Components> <SQLServer> <Databases> <Database>Testdb</Database> </Databases> </SQLServer> </Components> </Configuration> It does not allow me to put port number and can not connect to server.
I get following error:
Unable to connect to server. Reason: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
But it is not a sql server 2005 system and I can connect to this server via SSMS or SQL EM.
I'm trying to migrate/upgrade some databases from 2000 to 2005 and am having a problem. Apparently, the Upgrade Advisor can't analyze a SS2000 database if it is in a named instance. (see below)
This problem occurs because the SQL Server 2005 Upgrade Advisor cannot connect to the named instance of SQL Server 2000.
The SQL Server 2005 Upgrade Advisor uses information that the SQL Server Browser service returns when the SQL Server 2005 Upgrade Advisor tries to connect to an instance of SQL Server 2000. However, the SQL Server Browser service cannot return the correct information about the connection request. Therefore, the connection fails.
http://support.microsoft.com/kb/908454
Doesn't this make the UA tool useless for named instances on SS2000? Are there any plans to correct this issue? Or, is there a workaround available?
I ran Upgrade Advisor on a SQL 2000 server and I received warnings and errors for DTS packages and MetaData Services. Since there are no DTS packages and I don't see anything when I click on Meta Data Services Package, but I get an error when I click on Meta Data...
"An error occurred while trying to access the database information. The msdb database could not be opened."
Why is this error occurring when there are no DTS packages?
Is there any issues to point the Microsoft SQL Server Upgrade Advisor to the SQL2K production environment during normal hours? Any issues that you know of? Or anything that I should to know about this tools?
I'm testing the upgrade from SQL Server 2000 to SQL Server 2005 and first of all I ran the Upgrade Advisor. I received one issue that I cannot understand. The desctiption is:
Unexpected szVal value from parser - expected sp:name but received sp:args-
There is also indicated FTCATALOGNAMERESTRICTION and I suppose this is the "affected object" even if I cannot find it to the DB!
Do you have any hint for me? There is really few documentation on the net about using the Upgrade Advisor.
I'm carrying out an investigation into how much effort will be involved in upgrading our database from SQL Server 7.0 to SQL Server 2005. I've downloaded the Upgrade Advisor and run in against a copy of our production database. Most of the issues are trivial and I understand how to resolve them apart form one (to me) meaningless one:
When to Fix : Before
Description : Class Not Registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
Details : SVCACCTREQ
That's all the information it gives, except for a "This issue is resolved" checkbox. Anyone got any idea what the problem is, or how I go about tracking down the cause?
I'm running the analysis tool from a W2K Professional Client, connecting to SQL Server 7.0 running on an NT4 Server using Windows authentication. The account I'm connecting with is a member of the System Administrator group in SQL Server and is a local admin on the client, and a member of the Users group on the server.
Hi All, when i am migrating pckg dts to ssis before that i am checking that pckg with upgrad advisor. upgrad advisor report shows me following things i need to upgrade. 1. SQL Server 2000 Meta Data Services Packages are not support::Existing meta data services packages should be moved to sql server storage or structured storage files before you upgrade sql server 2005 does not install support for sql server 2000 meta data services therfore package migratio wizar willbe unable to access meta data services packages after upgrade in the absence of the SQL server 2000 client tool.
2.SQL server 2000 DTS designer components are required to edit DTS Packages
Hi all, i am in the process of upgrading my clustered SQL 7 to a new cluster with SQL 2005.
I tried to run Upgrade advisor against the SQL 7 cluster but i am not able to make it work. I checked prerequisites on my client machine, checked if my account has administrator privileges on thew cluster and everything seem fine. I tried to run UA using node name, virtual server name (as suggested in the help), IP address (both node and virtual server ones) and even SQL 7 instance name (!) with no result.
Are there any issue about upgrade advisor against a SQL 7 cluster ? or am I missing something about Upgrade advisor??
Got a question about one of the results on the upgrade advisor report.
When to Fix: Before Description: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Object: SVCACCTREQ
It is looking like some type of permission problem but I cannot find anything about this specific issue.
I am running the advisor from my local machine, on which I am a local administrator, against a remote server where I am just a typical user.
Is this an error that would be corrected if I were to run the upgrade advisor logged into the server as a local administrator? I'm trying to determine whether there is anything that needs to be done with this issue.
I ran the upgrade advisor on a SQL Server 2000 DTS package and received the following:
Upgrade Function: Replace functionality of complex Data Transformation task encapsulated in Execute DTS 2000 Package task after package migration Message: The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate complex Data Transformation tasks in SQL Server 2000 Data Transformation Services (DTS) packages. The migrated package will contain encapsulated DTS functionality that must eventually be removed or redesigned.
When I run the Migration Wizard, it runs successfully, with no encapsulated DTS fuctionality that I can see. As far as I can tell from comparing the two, it looks like it migrated successfully without any help from me! I'm not familiar with the business logic of the DTS package, so am worried that I'm missing something.
Is it possible for the Upgrade advisor to be wrong? Are there any advanced or random screens that I can check for something that might not have migrated correctly?
Thanks for any insight that you can provide! Jessica
I have remote SQL2000 server and have client of it on my system.
As I try to check upgrade issues with SQL2005 Upgrade advisor by writing server name and pressing DETECT button,it gives me error--"Requested registry access is not allowed.(mscorlib)".
Could you tell me what are the access i will need to run Sql 2005 upgrade on remote server.
We installed the SQL Server 2012 GUI tools, including "Upgrade Advisor," on a new virtual machine. We can connect to the old SQL Server 2008 R2 clustered databases just fine over port 1433 using SQL Server Management Studio 2012, but Upgrade Advisor is a mixed bag. Here are the steps we are taking:
- Click on "Start," "All Programs," "Microsoft SQL Server 2012," "SQL Server 2012 Upgrade Advisor"
- Fill in the server name with a valid SQL Server Network Name
- Select "SQL Server" as the only component to be analyzed
- Fill in the instance name with a valid named instance
- Use Windows Authentication (the default)
- The "SQL Server Parameters" window displays valid database names, meaning that we have a successful connection to the desired SQL Server instance at this point
- Leave all of the databased selected (the default)
- Click the "Run" button
- The "Upgrade Advisor Progress" window spins for a while and eventually generates the following error:
TITLE: mscorlib ------------------------------ The network path was not found. ------------------------------ BUTTONS: OK ------------------------------
Why would Upgrade Advisor be able to display the database names after making a successful connection only to fail later saying that it cannot find the network path?
I'm getting a Windows Installer error when attempting to run the Upgrade Advisor setup package (SQLUASetup.exe). The error message reads:
"This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service."
The machine is running Windows 2000 sp4. Both the .net framework v2 and Windows Installer 3.0 have been installed.
Unable to connect to server. Reason: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)
We have a vendor product that can only handle up to 18 characters for the server name and the instance name (we did not know this when we created the named instance) and of course our combined name is 19 characters, so it trys to pass the 18 charater name and then fails with the following error:
[LOG] Unable to read local eventlog (reason: The data area passed to a system call is too small)
So, can i rename the instance, or do i have to create a new named instance?
What are the minimum permissions required by the SQL Server 2005 Upgrade Advisor (UA)? I could not find it in the documentation.
Obviously being a local Administrators Windows group and a member of sysadmin SQL Server role will do the trick.
But will being a member of only the sysadmin SQL Server role be enough? I know that the UA does want to read the registry.
Running it under just sysadmin generates the following type of errors:
Database Server PreUpgrade Requested registry access is not allowed. WINSOCKPROXY
Database Server PreUpgrade Requested registry access is not allowed. FTUNSIGNEDCOMPONENTS
Database Server PreUpgrade Requested registry access is not allowed. NETPROTOCOL
Database Server PreUpgrade Requested registry access is not allowed. FTMULTIPLEINSTANCES
Database Server PreUpgrade Requested registry access is not allowed. INVALIDNAMEDPIPE
Database Server PreUpgrade Requested registry access is not allowed. FTCOMPONENTREG
Database Server PreUpgrade Requested registry access is not allowed. FTACCTPASS
The issue then is whether these are significant or not. If the UA is only reading the registry to determine if SSAS, DTS, etc is installed then that is not important. But if it is affecting the end result because it cannot read critical information from the registry that is another matter.
While connecting remote SQL server through upgrade advisor I am getting the below errors:
Error: Unable to connect to server. Reason: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Pls let me know if anyone has faced this issue and know how to fix.
I am planning to Upgrade from sql server 2008 R2 to SQL 2014.
I ran Upgrade advisor 2014 on the database which i want to upgrade and the result was clean with no issues spotted.
But when i run profiler on 2008 R2 to find events like deprecation final support i see many of those in the DB which are not captured by Upgrade Advisor 2014.
Eg: Deprecation Final support in Profiler trace:SET ROWCOUNT will be removed in a future version of SQL Server.
This was not caught in Ugrade Advisor.If 2014 upgrade Advisor didn't show any issues on a database, Am i good to go with code like SP's, Triggers, Functions etc?
Informatica jobs were erroring out with a sql server driver error while connecting to a named instance in SQL Server. The issue was because in sql server named instance, the port was allocated dynamically and Informatica 7.1.4 (provides 4.21 version of Datadirect odbc drivers for SQL server) which dont have support for named instances with dynamic port allocation. This feature is only present from version 5 of the Datadirect odbc drivers for SQL server To fix this issue, I need to allocate the port for the named instance instead of getting it dynamically. My questions 1) Whats the impact of doing a port allocation for the named instance on the existing environment. 2) Is there any issues which we can foresee in the applications 3) Things which i need to be aware of Thanks in advance sreenath
We are using a system that has uses four instances. On each client to the server we used the ODBC settings to connect to the different instances. We have since reinstalled the server, and now we are unable to find or 'see' any of the databases, except for locally.
E.g. The first database we install is named Foo, with database Bar. It is set up on port 1433. The second named instance is Foo2, with database Bar2. It is set up on a dynamic port.
We now try to connect to the database with ODBC. We connect to SERVERFOO, and then select the BAR db. It works fine. We then try to connect to the database SERVERFoo2, it lets us in, and then all we can select is the BAR db. I don't know what is causing this. We never before had to edit the settings in the client config for the odbc settings (e.g. to set manually to TCP port 1433) and I have checked the sql config manager to ensure that tcpip settings are allowed and will "ListenAll".
What more do we need to do? I think the browser should be installed, but my collegue disagrees.
Any ideas as to why we can only see the database referenced to 1433 port, and why no other port works, when we never had to do that before?
Using VS05 SP1 Pro SQL Express€¦ In converting a program from VS03/MSDE, long ago I installed SQL 2005 Express with Advanced Services and everything was fine. Windows Update has recently been failing to install SQL 2005 Express with Advanced Services SP2. After no answers from the forums, and logs that were of no help, I decided to uninstall SQL 2005 Express with Advanced Services and reinstall SQL 2005 Express (basic version). As a test run, I did it on a desk top, no problems what so ever. However, on my laptop, it has been a nightmare.
Question 1) in control panel, add/remove programs, all of SQL 2005 Express with Advanced Services uninstalled fine except one item - I am unable to uninstall MS SQL 2005 Backward Compatibility, getting the error message A network error occurred while attempting to read from the file c:windowsinstallersqlserver2005_bc.msi That file is not on the hard disk. After installing SQL 2005 Express (the basic version), this problem persists and I cannot uninstall MS SQL 2005 Backward Compatibility for the same reason. How can I get rid of MS SQL 2005 Backward Compatibility?
Question 2) Windows update still is trying to download and install SQL 2005 Express with Advanced Services SP2, even though I have uninstalled it. How to manually get rid of whatever settings are triggering this?
