We currently have a stand alone production server SQL 2005 STD + SP2 and plan to upgrade to clustered SQL 2005 Ent + SP2. What's the proper way to upgrade ? I want the existing server instance use Ent engine.
View 1 Replies
We have a server instance on SQL Server 2005 SP2 build 3042. We have a 32 bit x86 server. We attempted to upgrade to SP2 build 3054 KB934458. And we got the following error as stated in the Summary.txt file.
Code Snippet
**********************************************************************************
Product Installation Status
Product : SQL Server Database Services 2005 (MSSQLSERVER)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29538
Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
----------------------------------------------------------------------------------
The client tools and workstation components were successfully installed. The server is still reporting build 3042.
Here is the portions of the HotFix.log file.
Code Snippet
05/12/2008 09:19:09.041 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log
05/12/2008 09:19:09.072 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/12/2008 09:19:09.103 Registry: Cannot read registry key value "Debug"
05/12/2008 09:21:29.382 MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
05/12/2008 09:22:33.678 MSP returned 1603: A fatal error occurred during installation.
05/12/2008 09:22:33.724 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
Any help would be appreciated.
When attemping to install SQL 2005 Express using the following command line arguments
/qb UPGRADE=SQL_Engine INSTANCENAME=MY_INSTANCE
or
/qb UPGRADE=SQL_Engine INSTANCENAME=MY_INSTANCE SECURITYMODE=SQL SAPWD=MY_PASSWORD
the following error occurs.
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.
Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
The following version and editions have been verified.
1. .NET 2.0 installed
2. Windows XP SP2
3. MSDE 8.00.2039(SP4)
4. all MSDE databases are owned by sa
5. Instance and SQLAgent running under user that is member of Administrators
What are the possible reasons this error is occurring?
Hi,
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...
Greatly appreciated for any kind assistance.
Thanks.
Hi,
We are running a test upgrade form sql 2000 standard edition 32 bit to sql 2005 developer edition 32bit. Followed through all the steps and specified the account(SA priveleges and currently used by the 2000 version) and is the local admin on the box for the services and the setup seemed to move fine, except for when it got to the point of installing database services - This is the error message that I got:
MSSQLServer could not be started. Verify you have sufficient priveleges to start system services. The was no choice but to hit cancel and then the set up progressed with a final message of 'SEtup failed'.
Here is a portion of the error log:
Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
Database Mirroring Transport is disabled in the endpoint configuration.
Starting up database 'master'.
Converting database 'master' from version 589 to the current version 611.
Database 'master' running the upgrade step from version 589 to version 590.
Error: 946, Severity: 14, State: 1.
Cannot open database 'master' version 589. Upgrade the database to the latest version.
System Task Aggregate global counters produced an error that was not handled. Major: 9, Minor: 46, Severity:14, State:1
Error: 928, Severity: 20, State: 1.
During upgrade, database raised exception 15151, severity 16, state 1, address 01C4C50B. Use the exception number to determine the cause.
Error: 15151, Severity: 16, State: 1.
Cannot find the endpoint 'TSQL Local Machine', because it does not exist or you do not have permission.
Any help would be greatly appreciated
Thanks KR
Greetings,
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.
Any help would be greatly appreciated.
Cheers,
Lon
I tried creating an alias to the server to get it to connect to analyze the server but it will not recognize the SQL 2000 server as a valid server to analyze. I can use the alias to connect in EM or SSMS. Any ideas? The server is not clustered and is at SP4. I've connected to several others in my environment but this one is causing me grief!
Thanks,
Linda
I upgraded my SQL 2005 Workgroup 2005 to SP2 and subsequently could not get the SQL Server service running. Turns out this was a problem because I had created separate folders for my data and log files. The distmdl.mdf and mssqlsystemresource.mdf files were in my data folder and distmdl.ldf and mssqlsystemresource.ldf were in my log folder. During SP2 upgrade a new distmdl.ldf and mssqlsystemresource.ldf were created in my data folder. I deleted the distmdl.ldf and mssqlsystemresource.ldf files in my log folder and then moved the newly created ones in my data folder into the log folder and all is well now.
Just a heads up!
--Greg
I have upgraded a server with 4 CPU's 1.7 Dual Core AMD opteron.
Running with 16 GB RAM, on windows server 2003 enterprize edition.
and my server has really slowed down ?
An i missing something need urgent help
In our application we use the ADODB.Recordset.
In SQL server 2000
If there was a view that joined 2 tables and I accessed the view the 2 ID fields in the view would still have the AutoIncrement attribute still set to true so that I knew those were Identity fields.
In SQL server 2005
I dont' know why but if you reference a View that has Identiy AutoInc fields in ADO it doesn't keep those properties.
Also for whatever reason we Set the ID field to 0 to let ourselves know its a new Record. SQL 2000 let it happen and assumed it to be null where as By Setting the ID to 0 in SQL 2005 causes it to blow up on me.
Is there some sort of setting in SQL that can make SQL 2005 work like SQL 2000 in these two instances...
Hi,
I am currently in the process of upgrading a server from 6.5 to 7.0 However I am using the sp_dbcmptlevel stored procedure to leave the database in 6.5 compatability mode.
I have a few urgent questions on this:
- Would leaving a database in 6.5 affect database performance,ability to use web based development, datawarehousing?
- If I wanted to upgrade to SQL Server 2000, would I first have to switch compatability to 7.0 and then upgrade to 2000?
I would really appreaciate anyone with knowledge on these issues.
Thanks
hi, can I do the upgrade without installing OLAP services in the upgrade process, and what is the effect if not installing it.
thanks for your help
Ali
Can anybody help.
I am about to upgrade a number of systems from SQL Server 6.5 to 7.0. I have not attempted this procedure before.
I plan to use the upgrade wizard to implement the process.
Is there anything I should be aware of before I start , or should this be a straightforward process?
Is there a microsoft web site where I can get info on the upgrade.
Is there any other sites which provide useful info?
Thanks in anticipation,
PAUL
Currently running SQL Server 6.0 with NT4.0
1]Is it possible to upgrade from 6.0 directly to 7.0? How.
2]I have one database with SQL Server 6.0 on my Production Box & I have another Development box running SQL server 7.0.
I want to upgrade my 6.0 database(ON ONE SERVER A) to 7.0 Database(ON DIFFERENT SERVER B) runnung on development box.(I donot want to run Object transfer as The database are quite big & object transfer takes for ever)
I want to transfer database and also NT Logins & SQL Server Logins/users.
Suggestions
Hi,
I am a Sql server DBA. My new company planning to UPGRADE from AS/400 (DB2) to Sql Server 2000/sql 7.0.
Can any one suggest me how i have to plan the upgradation from as/400 to sql server 2000/sql 7.0.
suggest me some books , white papers or technical papers.
Any suggestions how to convert as400 files to sql server tables.
I appriciate all your answers.
thanks!
kavira
Hi at here i have a question regarding upgrade SQL server 6.5 To 7.0. Currently , i have a production system running in VB 6.0 with 6.5 SQL server. If i plan for running in 7.0 , is it any impact with my VB coding ? Can i move directly ? Thank !
View 1 Replies View RelatedOne of our windows service logged following events
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 1/31/2006
Time: 7:56:04 AM
User: N/A
Computer: blah blah
Description:
17066 :
SQL Server Assertion: File: <rowset.cpp>, line=3260
Failed Assertion = 'm_cILockBytesOpen == 0'
==================================================================
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 1/31/2006
Time: 7:56:04 AM
User: N/A
Computer: blah blah
Description:
18052 :
Error: 1203, Severity: 20, State: 1
Process ID 53 attempting to unlock unowned resource KEY: 11:2041058307:1 (8e02b4254032)
=================================================================
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 1/31/2006
Time: 7:56:04 AM
User: N/A
Computer: blah blah
Description:
Error: 1203, Severity: 20, State: 1
Process ID 53 attempting to unlock unowned resource KEY: 11:2041058307:1 (8e02b4254032)
=================================================================
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 1/31/2006
Time: 7:56:09 AM
User: N/A
Computer: blah blah
Description:
17066 :
SQL Server Assertion: File: <proc.c>, line=1576
Failed Assertion = 'm_activeSdesList.Head () == NULL'.
=================================================================
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 1/31/2006
Time: 7:56:09 AM
User: N/A
Computer: blah blah
Description:
17310 :
SqlDumpExceptionHandler: Process 692 generated fatal exception c000001d EXCEPTION_ILLEGAL_INSTRUCTION.
SQL Server is terminating this process.
=================================================================
I upgraded my SQL 2K instance with SP4 ( previously it was SP 3a) and the problem was resolved.
After few days one of over client's encountered the same problem. I ran SP4 on our client DB server too and problem got resolved.
This problem is not consistant and our other client are not facing this problem (they have SP 3a). Please help me what is the issue.
Thanks in advance
Hi,
I have question about orphan users - I currently have all my database files in the SAN and I am going to replace my server with a new server. My question is if I switch the databases to the new server and keep the same server name as the old one would I get orphan user in my database?
Below is what I am planning to do
1) Detached all databases from SQL server
2) Shut down the old server
3) Rename the new server with the same name as the old server
4) Attached all the databases to the new server.
I am assuming since all my database users are in sysusers (I am still using SQL 2000) then I should be ok. Is this true?
- I can't verify on my own, because I don;t have hardware to try out, :-(, but could some one let me know if you done things like this before?
Thanks in advance
Hi,
I am currently running a the Free version of SQL Server - however I know that in the future I will need to upgrade to the full SQL Server 2005 Licenced verision.
Is it possible to upgrade from one to the other?
Are there any known issues? For example will it keep any current databases as they are etc...
Thanks Andrew
We have 3 MSDE databases (3 seperate servers) which we need to make into one Sql 2000 server (new server). How is this done? Can't find anything clear about this.
Thanks
Hi.
We are going to upgrade one of our SQL Server 2000/Win200 instance to SQL Server 2005/Win2003. Currently, the SQL Server 2000 which contains about 30 database. This is my plan:
Install SQL Server 2005/Win2003 on a new instance
Backup SQL Server 2000 database instance (how do I back all 30 database at the same time?)
Then do a Restore from the SQL Server 2005 instanceIs this a good method or using the "Copy Database Wizard" is better method?
I'm new to this so please advice? Thanks!
Hi I run Upgrade Advisor and i get this error
===================================
Upgrade Advisor could not detect SQL Server components on the server.
===================================
The network path was not found.
(mscorlib)
------------------------------
Program Location:
at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
at Microsoft.SqlServer.UpgradeAdvisor.SqlDetection.GetClusterInfo()
at Microsoft.SqlServer.UpgradeAdvisor.SqlDetection.DetectComponents()
at Microsoft.SqlServer.UpgradeAdvisor.FormDetectComponents.Detect()
Server
Windows 2000 SP4
SQL 2000 Standard
.Net 1 & .Net 2 installed
All windows updated installed
Anyone with any ideas
Thanks in advanced
Nick
Hi All,
A client of mine was using SQL Express and soon realised this doesn't meet his needs performance or database size wise. He also realised that SQL Server 2005 Workgroup came free with his R2 version of SBS.
So in essence, I have been trying to find the Microsoft recommended way to upgrade from Express to Workgroup. I have not been able to find a step-by-step guide and to add to my confusion, when I run the work-group installer it tells me to run the installer with a switch which I have gone ahead and done but when selecting components it has all of them defaulted to blanked out.
Surely the process for an in-place upgrade should not be so technical as I am finding it ? To my mind, the natural progression would be to upgrade express to a better capable version of 2005 and should be as easy as pie.
Anyway, I am basically looking for a step-by-step guide on how to upgrade to get it done right the first time as opposed to upgrading and than realised some remenants of Express are still larking about causing trouble.
Regards,
QS
Hi all,
We are currently using VWD and Sql Server Express 2005. There is now SSE SP1 available (as well as another version with additional software). So, I have some questions:
1) Is the only difference between SSE and SSE SP1 just the addition of Management Studio Express?
2) Can I just upgrade to SSE SP1 separately, (It installed automatically when I installed VWD), and will VWD still work correctly with all the databases I have already created?
3) We are considering upgrading to full Sql Server in the near future. I have heard that there are problems if we have Management Studio Express installed and then try to install full Sql Server. Is this true?
Thanks for your help,
Claude.
I'm currently running SQL Server 6.5 on an old NT box. I just got a shiny new server with SQL Server 7 on it, so I'm itching to switch over to the
new server, but I'm going to need to shut down my website while the upgrade occurs, and I need to know how long it's going to take. I have
about 40GB of data in 200 tables in 15 databases. Can anyone estimate how long the upgrade wizard will take to complete its operations?
Thanks,
Steve Renaker
I am planning to upgrade our SQL Server 2000 box from Win NT to Windows 2000. Have anyone done the same thing and has encounter problems? Thank you.
View 2 Replies View Relatedthe first 2 parts install but the installation fails on the MSDE installation.
It gves me an error like about invalid installation media or something?
I have sql server enterprise.
plz help
I have some sql server 6.5 bases that i want to upgrade to sql server 2000. the problem is i cannot locate the upgrade wizard. where do i find it.??
View 2 Replies View RelatedI'm running the SQL 2000 upgrade wizard and this error came up in the final phases of the upgrade to SQL 2000. The phase is doing the Export Import of the Table data:
Error: Couldn't connect to the ADMIN$ share on the export machine. Verify that the MSSQLServer Service uses a NT Domain account that is part of the Administrator's group of the export machine and that both machines are in the same domain.
I've checked and service account are in the local admin group and both are in the same resource domain. The service account is in the accounts domain.
I have SQL server 6.5 with service pack 5a. Another machine with W2k and SQL server 2000 with SP3 and disables cnv6x70.dll.
Thanks
Hello,
We've some of the boxes are SQL Server 7.0 with 65 compatability and SQL Server 7.0 with 70 compatability. Now we are planing to upgrade to SQL 2000 with 80 compatability.
My question, how much complicated it is?
Is there any code changes to do in Stored Procs or Triggers or other? and what are the differences?
If lot of code changes, is there any tool to scan stored procedures?
(As we've more 5000 Stored Procedures)
If my question is not clear, let me know.
Thanks!
Hi
We currently have a Server:
Dual Intel Xeon 3.0 GHz
4 GB ram
(C) 2x18 GB SCSI disks RAID 1 for OS
(D) 4x72 GB SCSI disks RAID 5 for Data
The server is running:
Windows 2003 + IIS (Single web application)
Tomcat (Single web application) (Is about to be outfased)
MS SQL 2005 (In simple recovery mode)
The C-driver is currently only used for OS and applications
The D-driver is holding all data + SQL Data files and SQL Transaction files...
E.g.
- SQL Data files = 7 GB
- SQL Transaction files = 20 GB
- Image liberary = 100 GB
- Other = 15 GB
The IIS uses around 768 MB ram for cashing and execution of the web application
The Tomcat uses around 350 MB ram
The SQL is the to use a max of 2.2 GB ram (and 1024 MB pr. query)
(Leaving around 512 MB ram left)
There is only one database installed on the SQL, but it is very large (+15 mill records)
We are currently doing Free-Text searches in one table (~3.5 mill records), and it is to slow.
So the question is what is the best way to gain performance...
- Increase to 8 GB ram?
- Purchase a new server as webserver, so the curr. server can be dedicated as SQL?
- Attach a NAS to split the SQL files into several groups, and seperate transaction logs from data?
(6 disks are max in curr. server)
Economy has to be considered :)
Thanx!
hi All .
I use Micorosft SQL 2005 upgrade advisor to upgrade from sql 2000 to sql 2005, but I got problem .
here is my problem .
On my machine I have Sql 2000 Developer without server pack, and Sql server 20045 express edition .
Please help me to overcome this problem .
Many thanks in advance .
regards,
QuachNguyen
Hi all,This might be a very stupid question: To do an upgrade of the SQL Serverdriver, would it be sufficient to just copy the latest version of theSQLSRV32.dll to the C:Windowssystem32 directory (overwriting the existentone). Or would I need to do more?Thanks in advance,BoB
View 1 Replies View Related