Is It Possible To Upgrade To SP1 For My Existing SQL 2005 Express Edition?
Oct 8, 2006
I just downloaded the "SQL Server 2005 Express SP1", but I found that there is no upgrade option, it will just install a new instance of SQL 2005 Express. So, I just curious to know, how do I upgrade to SP1 smoothly?
Current set-up: three node cluster running Windows Server 2003 Enterprise Edition SP2 with two instances of SQL Server 2005 Standard Edition SP2.
Virtual node 1: Standard Edition, default instance, Database Engine only
Virtual node 2: Standard Edition, named instance, Database Engine, Analysis Services and Integration Services
Physical node A: Prefered node for virtual node 1
Physical node B: Failover node for both virtual node 1 and 2 (thus having two installations of Standard Edition)
Physical node C: Prefered node for virtual node 2
We started off with this set-up because there was no need for Enterprise features, and SQL 2005 supports failover clustering with two nodes in Standard Edition. Saved a bundle of cash, so everybody's happy. Now we need to run a solution on virtual node 2 that requires Enterprise features in Analysis and Integration Services, so an edition upgrade is required on virtual node 2. I have done some research and found several edition upgrade examples, but none that match the above scenario. We are running production on these machines, so I can't risk experimenting with command line options, I have to be right the first time.
Is it possible to mix two editions of SQL Server 2005 in one cluster? Can I upgrade virtual node 2 to Enterprise but leave virtual node 1 at Standard? What procedure do I have to follow to upgrade all three components of virtual node 2 to Enterprise Edition on both physical node B and C?
SQL Server Database ServicesConfiguring Components:
The installed has encountered an unexpected error. The error code is 2259. Database: Table(s) update failed
Attached is the section of the SQL setup log where the error occurs:
MSI (s) (70!C4) [10:50:00:107]: PROPERTY CHANGE: Deleting SQLACCOUNT property. Its current value is 'NT AUTHORITYNETWORK SERVICE'. <Func Name='updateFeatureSellection'> Attempt to start service when it is already running SQL service MSSQL$SQLEXPRESS started successfully waiting for SQL service to accept client connections SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'. sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english.
Setting status of unmanaged components and removing unmanaged resources Failed to modify installer view 1: 2259 2: 3: 4:
Error Code: 1627 MSI (s) (70!C4) [10:52:33:376]: Product: Microsoft SQL Server 2005 Express Edition -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed <Func Name='SetCAContext'> <EndFunc Name='SetCAContext' Return='T' GetLastError='203'> Doing Action: ValidateUpgrade PerfTime Start: ValidateUpgrade : Mon Mar 12 10:52:33 2007 <Func Name='ValidateUpgrade'> <Func Name='updateFeatureSellection'> <Func Name='SqlComponentUpgrade'> <Func Name='SetCAContext'> <EndFunc Name='SetCAContext' Return='T' GetLastError='111'> <Func Name='ProcessHeaderTable'> <Func Name='ProcessScriptTable'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='ProcessScriptTable'> <Func Name='GetFileTargetPath'> MSI (s) (70!C4) [10:52:33:506]: Note: 1: 2205 2: 3: _sqlSqlUpgradeInstallSequence MSI (s) (70!C4) [10:52:33:506]: Note: 1: 2228 2: 3: _sqlSqlUpgradeInstallSequence 4: CREATE TABLE `_sqlSqlUpgradeInstallSequence` (`Action` CHAR(255) NOT NULL, `Sequence` INT NOT NULL, `Param` CHAR(0), `Retryable` INT NOT NULL, `Fatal` INT NOT NULL PRIMARY KEY `Action`, `Sequence`) MSI (s) (70!C4) [10:52:33:506]: Note: 1: 2262 2: _sqlSqlUpgradeInstallSequence 3: -2147287038 <Func Name='GetFileTargetPath'> MSI (s) (70!C4) [10:52:33:516]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '310719000'. Its new value: '325719000'. MSI (s) (70!C4) [10:52:33:516]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '325719000'. Its new value: '325759000'. MSI (s) (70!C4) [10:52:33:516]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '325759000'. Its new value: '325769000'. MSI (s) (70!C4) [10:52:33:516]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '325769000'. Its new value: '395769000'. MSI (s) (70!C4) [10:52:33:526]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '395769000'. Its new value: '576338000'. MSI (s) (70!C4) [10:52:33:526]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '576338000'. Its new value: '591338000'. MSI (s) (70!C4) [10:52:33:526]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '591338000'. Its new value: '621338000'. MSI (s) (70!C4) [10:52:33:526]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '621338000'. Its new value: '621438000'. Couldn't find SQL Agent service SQLAgent$SQLEXPRESS. Skipping service stop
Having some problems Upgrading from SQL Express 2005 SP2 to SQL 2005 Standard. I'm getting the following:
Name: Microsoft SQL Server 2005 Express Edition
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Build version check:
Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.
Pretty sure that I have to have SQL 2005 Std w/SP2 but I don't have a CD with it on. Is there a way that I can create one so that I can upgrade the SQL Instance In-Place.
I am trying to upgrade MSDE 2000 to MS SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) using a silent install. MSDE on our systems is installed as a standalone product. There is only a single default instance (MSSQLSERVER) running on the system. SQL Authentication mode is being used. When I try and upgrade MSDE 2000 directly to MS SQL Server 2005 Express Edition SP2, the install fails with an error:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I try to upgrade the default instance of MSDE to SQL Server 2005 Express Edition SP2 selecting Windows authentication (logging in as a domain/local administrator to the server), the install fails with an error:
"Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>"
However, MSDE 2000 upgrade to an earlier version of MS SQL Server 2005 Express Edition (Build 9.00.1399.6) using SA Authentication works successfully without any errors.
So I tried to upgrade our MSDE installation to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) as a 2 step process. First by upgrading MSDE to SQL Server 2005 (Build 9.00.1399.6) using SA Authentication which works successfully as mentioned earlier.
However, when I try and upgrade SQL Server 2005 (Build 9.00.1399.6) to SQL Server 2005 SP2 (Build 9.00.3042.0) using SA Authentication, I receive the same error as before:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I upgrade using Windows Authentication, the setup displays the following error:
"[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again"
The log file content for the error is: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SQL_ERROR (-1) in OdbcStatement::execute_batch sqlstate=01000, level=0, state=1, native_error=0, msg=[Microsoft][SQL Native Client][SQL Server]Signing sps ... sqlstate=42000, level=16, state=1, native_error=15119, msg=[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL. sqlstate=HY000, level=0, state=0, native_error=0, msg=[Microsoft][SQL Native Client]Unspecified error occurred on SQL Server. Connection may have been terminated by the server. sqlstate=42000, level=16, state=2, native_error=2745, msg=[Microsoft][SQL Native Client][SQL Server]Process ID 51 has raised user error 50000, severity 20. SQL Server is terminating this process. sqlstate=HY000, level=20, state=127, native_error=50000, msg=[Microsoft][SQL Native Client][SQL Server]Cannot create ##MS_AgentSigningCertificate## in msdb. INSTMSDB.SQL terminating. Error Code: 15119 MSI (s) (08!80) [10:56:13:133]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.'. SQL Server Setup has encountered the following problem: Failed to execute the Transact-SQL statement: /**************************************************************/ /* Sign agent sps and ... Script file: sqlagent90_msdb_upgrade.sql The error was: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again. SQL_ERROR (-1) in OdbcHandle::release sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error SQL_ERROR (-1) in OdbcHandle::release sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error SQL_ERROR (-1) in OdbcHandle::release sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error Error Code: 0x80073b0f (15119) Windows Error Text: Source File Name: libodbc_statement.h Compiler Timestamp: Wed Jun 14 16:28:15 2006 Function Name: OdbcStatement::execute_batch@sqlagent90_msdb_upgrade.sql@967 Source Line Number: 91 -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The registry entries suggest that the version now is 9.00.3042.0. However, I am not sure if the upgrade was successful. I can connect to the database using the old SA user ID and password.
If anyone else has faced similar issues, please let me know the workaround for the same.
I am planning an upgrade from MSDE to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) for our 2000/2K3 Servers. The MSDE installation on our servers is a standalone installation (default instance) and uses Mixed Mode Authentication. When I execute the setup program for upgrade and choose SQL Server Authentication (and enter the corresponding SA user Id password), the setup program displays an error "SQL Server Setup cannot upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade". However, when I select Windows Authentication for the upgrade, the setup program displays an error €œ[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again€? (Error Code 15119).
I even tried changing the Authentication mode from Mixed Mode to Windows Authentication (by changing the LoginMode registry key value to 1) and running the upgrade using Windows Authentication, but I receive the same error.
1) Is the password policy for SQL Server 2005 Express Edition SP2 different from MSDE or SQL Server 2005 Express Edition (Initial Version), since upgrade from MSDE to SQL Server 2005 Express Edition (Initial Version) worked successfully without any issues. 2) When I am using Windows Authentication for the upgrade, the installer does not prompt me for any password. What password is the installer validating against the password filter DLL? Is there a way to find it out? Also, is it possible to find out what was the reason for the password validation to fail?
I would really appreciate if I could get some answers to all the problems I am facing.
I have a Windows Server 2000/Windows Server 2003 Environments with MSDE installed (default instance) and SecurityMode is SQL. I want to upgrade from MSDE to SQL Server 2005 Express Edition using a silent install since the number of servers is huge.
I downloaded the latest SQL Server 2005 Express Edition SP2 Version 9.0.3042.0 from http://msdn2.microsoft.com/en-us/express/bb410792.aspx
I am having the following problems: - When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting SQL authentication, the install fails with an error "SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade". - When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting Windows authentication, the install fails with an error "Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>
I had earlier tested upgrading the MSDE installation to SQL Server 2005 Express Edition Version 9.00.1399.6 downloaded from http://www.microsoft.com/downloads/details.aspx?familyid=220549b5-0b07-4448-8848-dcc397514b41&displaylang=en and the upgrade worked successfully using SQL Authentication (SA User and corresponding password), but for some reason it doesn't work when I use the latest version 9.0.3042.0.
Has anyone else faced similar issues. Any tips on how I can upgrade from MSDE to SQL Server 2005 Express Edition SP2 are welcome.
I tried to upgrade an Express edition 2005 to Standard Edition 2005. I did remember to use the command prompt setup parameter to allow the upgrade but still the option to upgrade is disabled. Can upgrade from express to standard?
Just bought the SQL server 2005 standard edition software to replace the express edition that I have been running for the last 6 months.
The setup works fine until I ask it to install the management studio.
At this stage it seems to think that I have a newer version already installed and tells me that it won't upgrade it.
I then wend through the add/remove sotware function in control panel and removed everything to do with SQL server and tried again. The same thing happened.
If I search for updates with Microsoft or Windows Update it notifies me to upgrade SQL Server Express to SP2. After the download the installation fails. The reason seems to be that Microsoft Update downloads SP2 with the wrong language:
Summary.txt
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Datenbankdienste für Express (SQLEXPRESS) DEU SP1 2005.090.2047.00 x86 EXPRESS Datenbankdienste für Express (SQLExpress) ENU SP2 x86 EXPRESS
********************************************************************************** Products Disqualified & Reason Product Reason Datenbankdienste für Express (SQLExpress) Für dieses Update ist die Sprache DEU erforderlich (required/me). Bei der Produktinstanz SQLExpress wird die Sprache ENU verwendet. Downloaden (download/me) Sie das Update für ENU.
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 1627
I'd like to upgrade from my current SQL Server version: 09.00.3042 (Workgroup edition that comes with SBS upgrade) to the standard edition that I've just purchased. I've attempted to run setup.exe SKUUPGRADE=1 from the command prompt and it just tells me that there's nothing new to install.
I don't really want to uninstall the current installation just to do something that shouldn't be complicated to do, upgrading software versions should not be a difficult process.
because we installed the SQL Server 2005-64Bit Developer Edition on a 2003 Server R2-64Bit with 10GB RAM an 2 Xeon. Now we have huge performance problems wich should be better using the Stadard Edition...
I don't know if it is easily possible to upgrade by only inserting the DVD and start the Setup...
I've installed Visual Basic 2005 express edition & tried to connect to SQL Server 2005 express edition. I noticed that VB2005 Express Edition doesn't have any OLEDB provider for SQL Server. The only OLEDB Provider is for M.Access. Is this correct? if so, what should i do if i want to connect SQL Server 2005 express edition with VB2005 express edition by using OLEDB connection type?
I really appreciate any respond from you guys.. Thank's and waiting for the good news..
Hi there. I am new to the SQL Express. I just finished installing the SQL Express 2005 with Advanced Services on a Windows XP SP2 computer. The first thing I noticed was the service manager (used to be on the taskbar) was being removed on the Express Edition. How do I get this feature back if it's even possible? I know you can find out the server status from the Configuration Manager but it's handy if the status is showned on the taskbar after logging in.
1- when install SQL Server it give a warning mesage that the IIS is not installed in server. I have a web application in a server and the SQLServer is installed in another server. Should I install the IIS in SQL Server (server) (even the web application in another server) or not??? Is it highly recomended or required to install the IIS?
2- How can I upgrade the Express Edition to another edition? And what the editions that I can upgrade Express to edition?
Hello. I want to Upgrade my database that is in SQL server Express Edition to SQL server 2005 standard.
I am using Report server. So my question is, is there something I should do before I make the upgrade? or it is a clean upgrade? (meaning: only following wizard instructions).
Hello, I have been using the express edition for months, and just upgraded to the pro edition (after uninstalling completely the express). So far everything is working perfectly, including my connection to the database. But when I look at the connection string in the web config I can see that the datasource is still SQLEXPRESS... Does it mean a sql server express version is still running ? How should I "upgrade" my database to the full edition version? Thanks in advance for your help.
Can I migrate from SQL Exp. Edition 2005 to the Standard version, can that be done? If not, what do I need to know? If yes, what should I be looked out for?
I need to create the script to upgrade the current named instance of sql 2000 desktop engine to sql server 2005 express edition. I am having difficulty preparing the template.ini and would appreciate help.
I get an error that this file is invalid..Any clues? I am trying to upgrade existing instance of msde 2k to sql express 2005 and uses sql authentication
Hello!M a newbie.. I just want to know, that wots the difference b/w SQL Server Standard Edition and Express Edition.?And can I use Visual Studio 2005 (Professional Edition) with SQL Server Express Edition.?
I got a problem in my development phase. I'm developing a web-application system that running merge database technology which is centralized database and distributed database. This is because my customer want a highly optimum system standby.
My centralized database running SQL Server 2005 Standard Edition and the distributed database running SQL Server 2005 Express Edition (because it is free). Each of these database, the users can change the data on its database. So, every database must have the same data. from my understanding, each server must act as Publisher and Subscriber. Can SQL Server 2005 Express Edition be a Publisher?
If not, what the solution you all may suggest, because cost is the first factor. If my architecture is not correct, so what you all suggest to me to resolve the problem.
Thanks so much. Any suggestion and opinion is highly appreciate and I'm highly thanks to you all.
I have downloaded SQLServer2005SP2-KB921896-x86-ENU.exe and attempted to update to SP2 with no success.
SQL Server 2005 Developers Edition is installed on my computer as part of a Visual Studio 2005 installation.
When I try to run this package under my admin account, I get through the Feature Selection (selecting everything) to Authentication.
When I press the Test button or the Next button, I get "Your account information could not be verified. Press Ok to return to Authentication Mode screen to determine the reason for failure. For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator."
The Authentication screen shows "Database Services, MSSQLSERVER, Windows, domainusername, Service Failed to Start"
I am a novice SQL Server user, Clearly I am floundering! Any observations, advice, or suggestions would be greatly appreciated.
Has anyone tried an in-place upgrade from SQL Server 2005 Developer to Standard Edition?
It apears to be a valid upgrade path according to this: http://msdn2.microsoft.com/en-us/library/ms143393.aspx
Is it just a case of changing the registered licensing info? (I presume all the functionality for Standard exists in the Developer Edition) Or is it a reinstall job?
I want to use a dev license for development on the server, then once its finished, just leave it in place on the box and upgrade the licensing to standard edition. (The client doesn't yet have a Standard License, but does have a Dev License - and wants me to start right away!)
If its going to boil down to having to do a full re-installation then I should get a Standard license from the start, if its just a minor license key change, then I can use a Dev license straight away!
I did run upgrade advisior to check the existed sql 2005 standard edition to upgrade to enterprise editon. I got the following error message:
SQL Server version: 09.00.1399 is not supported by this release of Upgrade Advisor
Is it means the upgrade advisor can only work on from 7.0, 2000 to 2005? If I need check from standard to enterjprise in 2005, what kind of tool I can use?
Hi. I'm trying to get full-text search working on my SQL 2005 Express with Advanced Services and am having problems. I thought that I installed it correctly, and when I look in the services running, I see it SQL Server Fulltext Search(MSSQLSERVER). Also note that I have SQL Server 2005 Standard installed on this same laptop. I don't know if that Full text Search applies to the Standard, Express or both.
What I do see is that if I connect to the database engine named <mylaptop>, I can see the version is 9.0.1399 and I can see the check box to enable full-text indexing in a particular databases properties. When I run SELECT FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'), I get a 1.
However, when I connect to the engine name <mylaptop>SQLExpress, I se the version is 9.0.3042, and I don't see the same check-box to enable full-text indexing. When I run SELECT FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'), I get a 0.
I've never tried this before so I know I'm probably missing something basic. But, I have searched quite a bit and not found my answer. So, I'm looking to you for help.
Hi, I currently have a license for SQL Server Standard 2005 that I would like to implement, but do not have the media. Is there a way to upgrade the developer edition and apply the license to it, thus creating a valid, licensed, Standard 2005 copy? Thanks!
I am having a problem when trying to add the Client Components to an existing installation of SQL 2005 Standard Edition SP1 running on Windows 2003 Standard. The server was originally built with SQL 2005 Standard Edition and had SP1 installed at a later date. I am using the CD that SQL was originally installed with which is not a service packed copy of SQL. The reason given when clicking the details button is as follows:
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Build version check:
Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.
I have clients that have the MSDE version installed and we need to upgrade there program to the MSSQL 2005. Is there an easy way to convert the data? Should or Could I uninstall MSDE and than install MSSQL2005 WorkGrp? Will there data be affected? Any tips would be appreciated.Thanks!
I have been unable to create a replication from an SQL Server 2005 standard edition database to remote SQL Server 2005 Express Edition. The remote express edition is on a Virtual Private Server we are leasing from a hosting company. The name of the remote DB is similar to vs572.si-vs572.com. I can connect to this with SQL server authentication through Management Studio and also with SSIS. But, I have been unable to create a push subscription (I have tried a test push subscription with the same publication to a local SQL Express server here in our office and this works fine).
Here is the error message: SQL Server Replication requires the actual server name to make a connection to the server. Connections through server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'VS572SQLEXPRESS'.
The hosting company had originally installed a shared SQL server which would not support replication. They then installed SQL Express edition and I was hoping this would allow us to run a replication.
I tried to connect to VS572SQLEXPRESS with out any luck. I check the remote connections, made sure replication was installed, etc., but no luck.