We have Sqlsvr 6.5 under NT4. We want to upgrade the database to
Sqlsvr 2000 under windows 2K. Is there any way we can do this by
copying the database to the win2K computer?? At any rate would
someone explain how to go about updating this. I know nothing about
sqlsvr anyversion but do need to know.
TIA
I would like to upgrade my database from 7 to 2000, are there any white papers or guide i can read. Or dose anyone have advise they can give?
Thanks
i am upgrading sql server 2000 database to sql server 2005 database.
I am using backup and restore method to upgrade.
i have an issues transferring the logins..
what is the best why to upgrade?????any info is appreciated..
Dear All..
I have a few databases running a sql2000 and the time as come to move them onto sql2005. Which would be the best route to take.
If I can think back to older version it was just a simply job of doing a backup in it's current version then restore in the new version? and upgrade was taken while restoring.. I could be wrong but any help !!
Thanks
Martin.
I just upgraded a large SQL 2000 database server to SQL 2005, and I have 2 databases that won't attach to the 2005 Server. They are both very small, about 90MB in size, and when I attach them to 2005, the process alternates between running and spinloop status. It can sit forever, and will never complete. I restored backups before the upgrade to a SQL 2000 Server, and reran DBCC CheckDB on both, and got no consistency errors, Updated Stats and indexes, then detached and moved the data files to 2005, and same thing.
View 3 Replies View RelatedSQL 2000 to SQL 2005 Upgrade Error - Database Down - Help Appreciated
I am upgrading a SQL 2000 standard database server to SQL 2005 standard on a windows 2003 server
I am logged in as domain admin and started the upgrade as 'sa'
The upgrade stops with the error:
Service MSSQLSERVICE can not be started. Verify you have sufficient privilages to start system services. The error code is (17185)
The error log shows:
2007-01-04 15:59:38.77 Server Authentication mode is MIXED.
2007-01-04 15:59:38.79 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-01-04 15:59:38.79 Server (c) 2005 Microsoft Corporation.
2007-01-04 15:59:38.79 Server All rights reserved.
2007-01-04 15:59:38.79 Server Server process ID is 4188.
2007-01-04 15:59:38.79 Server Logging SQL Server messages in file 'F:SQLDataMSSQLlogERRORLOG'.
2007-01-04 15:59:38.79 Server This instance of SQL Server last reported using a process ID of 2980 at 1/4/2007 3:56:58 PM (local) 1/4/2007 2:56:58 AM (UTC). This is an informational message only; no user action is required.
2007-01-04 15:59:38.79 Server Registry startup parameters:
2007-01-04 15:59:38.79 Server -d F:SQLDataMSSQLdatamaster.mdf
2007-01-04 15:59:38.79 Server -e F:SQLDataMSSQLlogERRORLOG
2007-01-04 15:59:38.79 Server -l F:SQLDataMSSQLdatamastlog.ldf
2007-01-04 15:59:38.79 Server Command Line Startup Parameters:
2007-01-04 15:59:38.79 Server -s MSSQLSERVER
2007-01-04 15:59:38.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-01-04 15:59:38.79 Server Detected 4 CPUs. This is an informational message; no user action is required.
2007-01-04 15:59:38.83 Server Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
2007-01-04 15:59:39.02 Server Using the static lock allocation specified in the locks configuration option. Allocated 20000 Lock blocks and 20000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-01-04 15:59:39.02 Server Multinode configuration: node 0: CPU mask: 0x0000000a Active CPU mask: 0x0000000a. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2007-01-04 15:59:39.04 Server Multinode configuration: node 1: CPU mask: 0x00000005 Active CPU mask: 0x00000005. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2007-01-04 15:59:39.04 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-01-04 15:59:41.04 Server 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.
2007-01-04 15:59:41.04 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-01-04 15:59:41.04 spid7s Starting up database 'master'.
2007-01-04 15:59:41.05 spid7s 1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2007-01-04 15:59:41.07 spid7s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2007-01-04 15:59:41.07 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2007-01-04 15:59:41.08 spid7s SQL Trace ID 1 was started by login "sa".
2007-01-04 15:59:41.08 spid7s Starting up database 'mssqlsystemresource'.
2007-01-04 15:59:41.11 spid7s Using 'dbghelp.dll' version '4.0.5'
2007-01-04 15:59:41.11 spid7s ***Stack Dump being sent to F:SQLDataMSSQLLOGSQLDump0035.txt
2007-01-04 15:59:41.11 spid7s SqlDumpExceptionHandler: Process 7 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2007-01-04 15:59:41.11 spid7s * *******************************************************************************
2007-01-04 15:59:41.11 spid7s *
2007-01-04 15:59:41.11 spid7s * BEGIN STACK DUMP:
2007-01-04 15:59:41.11 spid7s * 01/04/07 15:59:41 spid 7
2007-01-04 15:59:41.11 spid7s *
2007-01-04 15:59:41.11 spid7s *
2007-01-04 15:59:41.11 spid7s * Exception Address = 78144D3A Module(MSVCR80+00014D3A)
2007-01-04 15:59:41.11 spid7s * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
2007-01-04 15:59:41.11 spid7s * Access Violation occurred reading address 0000001E
2007-01-04 15:59:41.11 spid7s *
2007-01-04 15:59:41.11 spid7s *
2007-01-04 15:59:41.11 spid7s * MODULE BASE END SIZE
2007-01-04 15:59:41.11 spid7s * sqlservr 01000000 02BA7FFF 01ba8000
2007-01-04 15:59:41.11 spid7s * ntdll 7C800000 7C8BFFFF 000c0000
2007-01-04 15:59:41.11 spid7s * kernel32 77E40000 77F41FFF 00102000
2007-01-04 15:59:41.11 spid7s * MSVCR80 78130000 781CAFFF 0009b000
2007-01-04 15:59:41.11 spid7s * msvcrt 77BA0000 77BF9FFF 0005a000
2007-01-04 15:59:41.11 spid7s * MSVCP80 7C420000 7C4A6FFF 00087000
2007-01-04 15:59:41.11 spid7s * ADVAPI32 77F50000 77FEBFFF 0009c000
2007-01-04 15:59:41.11 spid7s * RPCRT4 77C50000 77CEEFFF 0009f000
2007-01-04 15:59:41.11 spid7s * USER32 77380000 77411FFF 00092000
2007-01-04 15:59:41.11 spid7s * GDI32 77C00000 77C47FFF 00048000
2007-01-04 15:59:41.11 spid7s * CRYPT32 761B0000 76242FFF 00093000
2007-01-04 15:59:41.11 spid7s * MSASN1 76190000 761A1FFF 00012000
2007-01-04 15:59:41.11 spid7s * Secur32 76F50000 76F62FFF 00013000
2007-01-04 15:59:41.11 spid7s * MSWSOCK 71B20000 71B60FFF 00041000
2007-01-04 15:59:41.11 spid7s * WS2_32 71C00000 71C16FFF 00017000
2007-01-04 15:59:41.11 spid7s * WS2HELP 71BF0000 71BF7FFF 00008000
2007-01-04 15:59:41.11 spid7s * USERENV 76920000 769E3FFF 000c4000
2007-01-04 15:59:41.11 spid7s * opends60 333E0000 333E6FFF 00007000
2007-01-04 15:59:41.11 spid7s * NETAPI32 71C40000 71C97FFF 00058000
2007-01-04 15:59:41.11 spid7s * SHELL32 7C8D0000 7D0D2FFF 00803000
2007-01-04 15:59:41.11 spid7s * SHLWAPI 77DA0000 77DF1FFF 00052000
2007-01-04 15:59:41.11 spid7s * comctl32 77420000 77522FFF 00103000
2007-01-04 15:59:41.11 spid7s * psapi 76B70000 76B7AFFF 0000b000
2007-01-04 15:59:41.11 spid7s * instapi 48060000 48069FFF 0000a000
2007-01-04 15:59:41.11 spid7s * sqlevn70 4F610000 4F7A0FFF 00191000
2007-01-04 15:59:41.11 spid7s * SQLOS 344D0000 344D4FFF 00005000
2007-01-04 15:59:41.11 spid7s * rsaenh 68000000 6802EFFF 0002f000
2007-01-04 15:59:41.11 spid7s * AUTHZ 76C40000 76C53FFF 00014000
2007-01-04 15:59:41.11 spid7s * MSCOREE 61FB0000 61FF4FFF 00045000
2007-01-04 15:59:41.11 spid7s * ole32 77670000 777A3FFF 00134000
2007-01-04 15:59:41.11 spid7s * msv1_0 76C90000 76CB6FFF 00027000
2007-01-04 15:59:41.11 spid7s * iphlpapi 76CF0000 76D09FFF 0001a000
2007-01-04 15:59:41.11 spid7s * kerberos 62220000 62277FFF 00058000
2007-01-04 15:59:41.11 spid7s * cryptdll 766E0000 766EBFFF 0000c000
2007-01-04 15:59:41.11 spid7s * schannel 76750000 76776FFF 00027000
2007-01-04 15:59:41.11 spid7s * COMRES 77010000 770D5FFF 000c6000
2007-01-04 15:59:41.11 spid7s * XOLEHLP 622E0000 622E5FFF 00006000
2007-01-04 15:59:41.11 spid7s * MSDTCPRX 622F0000 62367FFF 00078000
2007-01-04 15:59:41.11 spid7s * msvcp60 780C0000 78120FFF 00061000
2007-01-04 15:59:41.11 spid7s * MTXCLU 62370000 62388FFF 00019000
2007-01-04 15:59:41.11 spid7s * VERSION 77B90000 77B97FFF 00008000
2007-01-04 15:59:41.11 spid7s * WSOCK32 71BB0000 71BB8FFF 00009000
2007-01-04 15:59:41.11 spid7s * OLEAUT32 77D00000 77D8BFFF 0008c000
2007-01-04 15:59:41.11 spid7s * CLUSAPI 62390000 623A1FFF 00012000
2007-01-04 15:59:41.11 spid7s * RESUTILS 623B0000 623C2FFF 00013000
2007-01-04 15:59:41.11 spid7s * DNSAPI 76ED0000 76EF8FFF 00029000
2007-01-04 15:59:41.11 spid7s * winrnr 76F70000 76F76FFF 00007000
2007-01-04 15:59:41.11 spid7s * WLDAP32 76F10000 76F3DFFF 0002e000
2007-01-04 15:59:41.11 spid7s * rasadhlp 76F80000 76F84FFF 00005000
2007-01-04 15:59:41.11 spid7s * security 62800000 62803FFF 00004000
2007-01-04 15:59:41.11 spid7s * dbghelp 671B0000 672C7FFF 00118000
2007-01-04 15:59:41.11 spid7s *
2007-01-04 15:59:41.11 spid7s * Edi: 62FA0040: 62FA0028 671AFFF0 00000000 00000000 00000000 00000000
2007-01-04 15:59:41.11 spid7s * Esi: 0000001E:
2007-01-04 15:59:41.11 spid7s * Eax: 0416C05E: C0400096 C0400416 00000416 000062FA 00000000 00000000
2007-01-04 15:59:41.11 spid7s * Ebx: 0416C040: 0105F270 00002000 00000005 00000000 3368C1E0 00000000
2007-01-04 15:59:41.11 spid7s * Ecx: 0105B010: 458B0046 01F88348 00D3850F 458B0000 89C23B50 0F342444
2007-01-04 15:59:41.11 spid7s * Edx: 00000000:
2007-01-04 15:59:41.11 spid7s * Eip: 78144D3A: 24FFA5F3 144E5495 C78B9078 000003BA 04E98300 E0830C72
2007-01-04 15:59:41.11 spid7s * Ebp: 33D6E770: 33D6E790 01C65B97 62FA0040 0000001E 0416C040 0416C6DC
2007-01-04 15:59:41.11 spid7s * SegCs: 0000001B:
2007-01-04 15:59:41.11 spid7s * EFlags: 00010212: 0020006D 00690046 0065006C 005C0073 006F0043 006D006D
2007-01-04 15:59:41.11 spid7s * Esp: 33D6E768: 62FA0040 33D6E7A4 33D6E790 01C65B97 62FA0040 0000001E
2007-01-04 15:59:41.11 spid7s * SegSs: 00000023:
2007-01-04 15:59:41.11 spid7s * *******************************************************************************
2007-01-04 15:59:41.11 spid7s * -------------------------------------------------------------------------------
2007-01-04 15:59:41.11 spid7s * Short Stack Dump
2007-01-04 15:59:41.13 spid7s 78144D3A Module(MSVCR80+00014D3A)
2007-01-04 15:59:41.13 spid7s 01C65B97 Module(sqlservr+00C65B97)
2007-01-04 15:59:41.13 spid7s 01CA43B5 Module(sqlservr+00CA43B5)
2007-01-04 15:59:41.13 spid7s 01CA452E Module(sqlservr+00CA452E)
2007-01-04 15:59:41.13 spid7s 0217D3BD Module(sqlservr+0117D3BD)
2007-01-04 15:59:41.13 spid7s 0217B896 Module(sqlservr+0117B896)
2007-01-04 15:59:41.13 spid7s 0100889F Module(sqlservr+0000889F)
2007-01-04 15:59:41.13 spid7s 010089C5 Module(sqlservr+000089C5)
2007-01-04 15:59:41.13 spid7s 010086E7 Module(sqlservr+000086E7)
2007-01-04 15:59:41.13 spid7s 010D764A Module(sqlservr+000D764A)
2007-01-04 15:59:41.13 spid7s 010D7B71 Module(sqlservr+000D7B71)
2007-01-04 15:59:41.13 spid7s 010D746E Module(sqlservr+000D746E)
2007-01-04 15:59:41.13 spid7s 010D83F0 Module(sqlservr+000D83F0)
2007-01-04 15:59:41.13 spid7s 781329AA Module(MSVCR80+000029AA)
2007-01-04 15:59:41.13 spid7s 78132A36 Module(MSVCR80+00002A36)
2007-01-04 15:59:41.13 spid7s Stack Signature for the dump is 0x2BEDE9E0
2007-01-04 15:59:41.27 spid7s External dump process return code 0x20000001.
External dump process returned no errors.
2007-01-04 15:59:41.27 spid7s Error: 17185, Severity: 16, State: 1.
2007-01-04 15:59:41.27 spid7s Unable to update password policy.
2007-01-04 15:59:41.27 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Any clues?
Cheers
Paul
Hi All,
I have just migrated couple of test databases
from SQL Server 2000 to 2005 (side by side).
I also migrated the server level logins using SSIS transfer logins task, available on SSIS 'Transfer logins', I selected all the databases that I have migrated so that I have all database users account in server logins (to avoid orphaned users); but I don't have all the database users in server logins, also the sys.sysusers doesn't have the database users, that I have moved to SQL 2005. Can anybody help?
Also do I need to back up the SQL Server 2000 database and restore it on SQL 2005? What impact this operation can have?
Thanks for your time..
Bidyut
Hello!I would like to change the SQL server 2000 from Standard version toDevelopment edition. I have two database running on this server, bothreplicated, with few jobs, etc ... Can you recommend the easiest way to dothis? I heard, it would be as easy as, detaching the databases, deletingcurrent SQL software, installing different one, and attaching the olddatabases back. I doubt that is true, so that's why I'm asking here for anyreal-life instructions.Thanks for your input!Kind regards,Dejan--
View 1 Replies View RelatedI don't need 2005
obulay@hotmail.com
Hi
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
Thanks
Priyanka
There must be many various ways to upgrade a dual processor server from SQL 7 to SQL 2000.
Do you think I am better off to simply run the upgrade CDs?
Would it be better to de-install SQL 7 and then install SQL 2000?
Better still to Rebuild from scratch? (OS & setup)?
This particular server has seen little use actually.
Who has experience and suggestions?
Thanks,
Mark Blackburn
CA Dept of Parks
Hi.
I have two scenerio.
One:
Two servers (SQL 7.0), transaction replication
Two:
Four servers (SQL 7.0), transactional replication one publisher, one distributor and 2 subsribers.
I need to upgrade these two scenerio to 2000.
Please advice me with suggestions and your experience.
-MAK
I am planning on upgrading my existing SQL Server 7 to 2000. I plan on starting out just upgrading the SQL first, then upgrading to Win2k Server later on.
I have read some posts here with some of you having issues, etc. Based on your experiences, do you suggest, I do both upgrades together? I think it would be best to do this on a new server, and keeping everything live on the other server until I feel comfortable in moving over the data.
What files besides the database files, should I restore, if any? Are there any significant application performance issues or bugs? Should I wait to apply the first sql patch that was just released last week? What about any code that needs to be rewritten?I will do it as a test first, but any advice would be great.
I have several SQL 7.0 SQL servers that I need to upgrade to SQL 2000.
I have been tasked with finding out what the risks are in upgrading and where I may run into problems when upgrading.
So far I have'nt been able to find any info of how to prepare for the upgrade.
Does anyone know of potential problems I should look for or documents/kb articles on the web that I can refer to plan correctly.
Thanks.
We are trying to do an upgrade in place and are getting errors that it can't activate model database files. We believe it's because we move all log files to another drive and think Microsoft failed once again to recognize this in their upgrades. They made this mistake in 7.0 SP2 (the SP failed if you moved log files to alternate location) but they fixed it in SP3.
Has anyeone experieinced this problem? Is there a workaround (other than the obvious.)
Replies are appreciated!
Colleen:confused:
We are about do an upgrade from 6.5 to 2000. Does anyone know of any material that would be of assistance to me. If you have any pointers that would also be appreciated.
View 1 Replies View RelatedTry to upgrade SQL 7 on a NT4 system to SQL 2000. Also like to upgrade NT4 to Win2K. Anyone know what's the best sequence for doing so? Thanks on advance.
View 1 Replies View RelatedWhat is the best way of brining a SQL Server 6.5 database to a Consolidated SQL Server 2000 environment? I tried using the SQL Server 2K upgrade wizard and it failed to import some data, which made me uncomfortable in using this tool?
Is this a safe approach:
Create a database on SQL 2K and script out all the objects like tables, Indexes, views and run it against SQL 2K.
Then run the DTS to populate all the tables and you are done?
Hi,
I'm looking to upgrade our old 6.5 server (running NT4) to 2000 and go to Windows Server 2003 at the same time. There are 10 or so small to medium sized DBs on here.
Can anyone provide some decent links to blogs, FAQs or documentation relating to this?
Many thanks,
Matt
Hi,I am trying to use the Upgrade Wizard in SQL 2000 to upgrade a SQL 6.5 db to2000. I am only choosing to update a single database, not system objects.The Upgrade wizard connects to SQL 6.5, checks the db, creates the db on SQL2000 with all tables and imports users from SQL 6.5. The problem comes whenit tries to bring over the actual data. I get an error:"Couldn't connection to the export machine!" in the out log file.The in log file reports login failed.Both SQL services were running at this point, the login via SA must beworking since it copies over the 6.5 db structure and users.The SQL 6.5 machine is NT 4. The 2000 machine is Windows Server 2003. Iwas logged in as domain admin when running this. I tried playing with the"SQLUpgrade" DSN that was created on the SQL 2000 machine to use SA orwindows authentication, both fail.Any ideas?Thanks.
View 1 Replies View RelatedHi! If doing online version upgrade from SQL 7.0 to SQl 2000, (1) do Ineed to shut down server? (2) after upgrading, is all login and dbuser, group information, scheduled Jobs, maintenance paln... stillthere? or I have to save the info before upgrading and recreate afterupgrading? (3) any other tips I need to know? I'm doign that for thefirst time.Thanks!Saiyou
View 2 Replies View Related
This is want happen. We have upgraded from sql 2000 sp3 to sql 2000 sp4 on an window 2003 server with sp1. Now we are getting this error. ERROR: 17805, SEVERITY: 20, STATE: 3 INVALID BUFFER RECEIVED FROM CLIENT..
Any ideas.
Mark
Hello,
I have a project where I have to upgrade SQL 2000 to 2005. When we are upgrading we are going to move to new server so server name will change. Most of our applications have a hard coded connection string. Applications are developed with Classic ASP, .NET 1.1 and 2.0 as well.
Now the question is what is the best way to do this? Changing all the connection string will be a very painful task as we have many applications.
Can anyone suggest a way where we can achieve this without changing all the connection strings?
Thanks in advance.
Tareq
Do I have to upgrade to 7.0 before installing the beta SQL 2000 or can I go straight from 6.5?
View 1 Replies View RelatedI am upgrading a SQL7 std to SQL2000 std
The upgrade process fails in the upgrade.sql step. With no meaningful error messages. All services that may use the db are stopped, the net is disabled so this server is stand alone, nothing can be accessing the db !
I cannot find any log output, from the upgrade so I dont know whats causing this. Has anyone any ideas ?
Thanks
Tom
Hi all:-
How do I upgrade my local sql server 7 to sql 2000 ? Do I just put in the sql server 2000 CD and run it or is there an upgrade CD ? I have lots of stuff on my sql 7 and don't want to lose it.
Thanks in advance!
Hi,
We have a VB application, which extracts data from SQL Server 6.5 database. Recently we upgraded our database from 6.5 to 2000.
One of the report which used to give results in Sorted order in 6.5 database, is not producing the same report in sorted order. We didn't do any change at database/application level.
As we have not made any changes at application level, I am presuming that the problem is at database level, due to this upgradation.
Can any one guide me how to rectify this problem.
As I don't have source code for this application; Is it possible for me to extract the query running for this report from database?
Thanks.
Hi guys.
I have two scenerio.
One:
Two servers (SQL 7.0), transaction replication
Two:
Four servers (SQL 7.0), transactional replication one publisher, one distributor and 2 subsribers.
I need to upgrade these two scenerio to 2000.
Please advice me with suggestions and your experience.
Is Online replication possible?
-MAK
Hello List,
I've couple of questions about Sql Server 2000 and would greatly appreciate, If somebody out there, please answer to it.
Questions:
I've a SQL 7 server dump file and I was wondering, If I can directly load this file into SQL Server 2000? If yes, Would this call a Upgrade of sql 7.0 database to SQl Server 2000? Or this is just a backward compatability support in 2000?
Well the main objective of this is, We are planning to upgrade one of our production SQL 7.0 server and I was wondering, If we can just take the SQL 7.0 dump file and load it into the SQL 2000 Server? If yes, What are the downgrades of this and if no, Should we upgrade the sql 7.0 server itself and along with it all the databases sitting on it? Please shed some light here.
Many thanks.
I started with a SQL 7.0 installation and installed an instance of SQL 2000. The default instance is SQL 7.0 as expected and both run fine. However, now I'd like to upgrade the SQL 7.0 instance to SQL 2000, but the setup procedure on the install CD only allows you to upgrade/modify the SQL 2000 instance. It seems as though once you've chosen to install SQL 2000 as an instance, you do not have the opportunity again to upgrade the SQL 7.0 instance in place. I tried to remove the SQL 2000 instance and reinstall 2000, but the procedure does not give you the opportunity to upgrade the SQL 7.0 instance -- only to modify the programs installed. Any suggestions?
(I could use the Copy Database Wizard to move all databases along with associated stored procedures, logins, etc., but then I'd have to mess with DTS packages, etc.)
the 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 tried several SQL 2000 upgrades from SQL 7.0 SP3 , NT 4.0 SP6a and numerous hotfixes.I have not had one go through the first time without a problem. These are inplace upgrades, not an install of a new instance.
Number one was the upgrade failed with "The ordinal 105 could not be located in dynamic link lib opends60.dll. To work around this I had to back out our two hotfixes (MS01-032, a security hotfix and the SQL profiler hotfix).
Number two was that MSSQLSERVER would not start before running MESSSAGES.SQL causing setup to hang. To work around this M$ told me to invoke SETUPSQL in debug mode and step through the upgrade and manually start MSSQLSERVER before MESSAGES.SQL was run. This worked and I was able to complete the upgrade successfully.
Number 3 occurred when SETUP could not find MASTLOG.LDF and died. When I first started running 7.0 I decided to move all logs to our separate log device even if they were truncate log on checkpoint. I know, it sounds stupid. I have since stopped this practice. I was able to move MASTLOG.LDF back to the same device and directory as MASTER.MDF and things worked fine. I feel setup ought to look for the logfile in the location specified on the MSSQLSERVER service startup parameter and not assume it's location.
Fortunately all of these upgrades were on test boxes or non-essential servers. However, I am very worried that new problems are going to crop up at each upgrade. I always ghost all volumes before an upgrade and also have good backups, so falling back is not a problem. Has anyone else had these kinds of problems with upgrades? Remember, I am talking about an upgrade not a detach all dbs, uninstall 7.0, install a new instance and reattach all dbs. Though this is something I can fall back on. Detaching and reattaching all DBs would be allot of work with saving logins and all.
I would appreciate any help or suggestions?
Steve Rinehart
Battelle Memorial Institute
Information Management
Technology Group, Network Computing Systems
(614) 424-6543
I'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