Hi,
I'm planning an upgrade of SQL 7.0 on NT 4.0 to SQL 2000 and of course I will attempt to upgrade the OS to Windows 2000 first.
Can anyone tell me of any issues I may run across during this upgrade?
Can I assume that SQL 7.0 will run ok on Windows 2000?
thanks much,
Robert
I am currently running SQL Server 2000 Standard on my production system, and I am looking to upgrade the system to Windows 2000 Adv. Server. I would also like to upgrade SQL Server 2000 Standard to SQL Server 2000 Enterprise to utilize more than 2GB of memory. Can anyone tell me what is the best way to upgrade the system, and please provide some feedback on your experiences with the upgrade. Thanks in advance.
View 2 Replies View RelatedHas anybody had any experience of this??We have over 2000 stored procs to convert from Watcom SQL to SQLServer 2000. Any automated tools would be much appreciated!!Also any known issues.
View 1 Replies View Related
We have 2 SQL servers in a failover cluster environment. SQL1 and SQL2. Currently SQL1 is the primary in the cluster, and we need to upgrade from Service Pack 3 to Service Pack 4.
Our setup:
Both servers are Windows 2003 Server Enterprise Edition.
Both servers have SQL Server 2000 Service Pack 3.
My question is:
Which upgrade plan do I take? Do I:
1. Upgrade the backup (offline) server in the cluster (SQL2) first, reboot, then failover from SQL1 to SQL2? Then do the other server?
2. Upgrade the primary (online) server in the cluster (SQL1) first and see if it replicates to the backup?
Any advice or tips would be most appreciated.
Thanks.
I restored a 2000 database back up in to my 2005 database and it works fine. THe only problem is that I cannot create diagrams.
I get the following message:
Database diagram support objects cannot be installed because this database does not have a valid owner. To continue, first use the Files page of the Database Properties dialog box or the ALTER AUTHORIZATION statement to set the database owner to a valid login, then add the database diagram support objects.
I have checked the db_owner and that is a valid owner.
I changed a few times to different owners and still could not install the diagrams..
Any ideas?
thanks
I have to upgrade and move SQL Server 2000 databases from a platform using Server 2000 to one running SQL Server 2005. The server nameinstances will need to be the same so that a number of third party applications and front end systems that connect, and are outside of my control, will not need any data source changes. The servers will be on the same network and can't co-exist with the same name so I guess that I have to go "big bang".
Does anyone have any suggestions for a strategy that I can use?
Does anyone know of any issues that I should be aware of?
I have run the SQL Server 2005 Upgrade Advisor and it tells me the databases should upgrade OK with a few minor issues that can be fixed after.
Thanks,
Hello all,
I'm finding the documentation online to upgrading from 2000 to 2005 fairly poor.
What are the upgrading options and which one is the best option for a web server database.
Also what are best practices pre-upgrade, during upgrade and post-upgrade.
Cannot find much online.
Also since this question will be asked often might as well make it a sticky.
Thanks
Hello
I'm trying to upgrade a Microsoft SQL 2000 (8.00.760 SP3) server to SQL 2005.
It€™s a standard install, std version, not very big databases, default instance, plenty of memory etc. OS is a 2003 server recently upgraded from 2000. All patches etc are installed.
Upgrade was going fine and had got approx 90% through, had started the 2005 db service and converted the databases before it got the following error:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Invalid connection string attribute Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
The 'For help' link returned the helpful... €˜We are sorry but we can€™t help€™...
Worked through http://msdn2.microsoft.com/en-us/library/ms143698.aspx but not 100% applicable and didn€™t resolve.
Partially rolled back, rebooted and resumed install but failed in the same place. Ended going back to a backup snapshot so is now back running as SQL 2000.
Excerpt from install log is below...
Thanks in advance for any assistance.
<Finished SQL statement: Wed Oct 10 21:25:21 2007>
<Started SQL statement: Wed Oct 10 21:25:21 2007> BEGIN DECLARE @GroupName AS nvarchar(4000) SET @GroupName = QUOTENAME(N'PROPMAN-DATASQLServer2005MSFTEUser$PROPMAN-DATA$MSSQLSERVER') EXECUTE(N'grant execute on sp_fulltext_getdata to ' + @GroupName) END
<Finished SQL statement: Wed Oct 10 21:25:22 2007>
Service MSSQLSERVER is being stopped at Wed Oct 10 21:25:22 2007
Service MSSQLSERVER with parameters '' is being started at Wed Oct 10 21:25:34 2007
Attempt to start service when it is already running
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Service MSSQLSERVER started at Wed Oct 10 21:25:40 2007
<EndServerDowntime Wed Oct 10 21:25:40 2007>
Loaded DLL:
C:WINNTsystem32Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=01S00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Invalid connection string attribute
Error Code: 0x8007ea62 (60002)
Windows Error Text: Source File Name: libodbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@upgradeconnect
Source Line Number: 148
---- Context -----------------------------------------------
sqls:equenceInstaller::launchAction
Staring action SqlScript
SqlUpgradeScriptHlpr
Connecting to SQL Server
ExecuteUpgradeSqlCommands
sqlConnect
Originial error was 8007ea62 (60002)
Error Code: 60002
MSI (s) (5C!20) [21:26:20:164]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Invalid connection string attribute Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.'.
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Invalid connection string attribute Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Loaded DLL:
C:WINNTsystem32Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=01S00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Invalid connection string attribute
Error Code: 0x8007ea62 (60002)
Windows Error Text: Source File Name: libodbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@upgradeconnect
Source Line Number: 148
---- Context -----------------------------------------------
We shall be taking a bunch of 7.0 instances and moving/upgrading to a SQL 2000 cluster server. I was thinking of creating new named instances on the 2000 cluster and upgrading each 7.0 server to it's respective named instance. Also thought of using the 2000 copy database wizard; I was told this didn't always work. Anyone hear of problems with this?
Thanks
I recently upgraded from SQL Server 2000 to SQL Server 2005. I have Oracle databases I need to share data with. I was using the Heterogeneous Services (hsodbc) from Oracle and connected to SS 2000 fine. Since I've upgraded, I can't use hsodbc to connect to my SS 2005 database. I get the following error:
ORACLE GENERIC GATEWAY Log File Started at 2006-09-06T09:40:07
hoainit (3): ; hoainit Exited with retcode = 0.
hoalgon (7): ; hoalgon Entered. name = edw.
DB_ODBC_INTERFACE (2085): ; [Microsoft][SQL Native Client][SQL Server]Login
failed for user 'edw'. (SQL State: 28000; SQL Code: 18456)
DRV_InitTdp: DB_ODBC_INTERFACE (2085): ; [Microsoft][SQL Native Client][SQL
Server]Login failed for user 'edw'. (SQL State: 28000; SQL Code: 18456)
nvRETURN (F:WorkConnect_4_6_3srcdrvDRV_BIND.C 356): -2220
nvRETURN (F:WorkConnect_4_6_3srcavNAV_BIND.C 293): -2220
hoalgon (7): ; hoalgon Exited with retcode = 28500.
My upgrade of SQL Server 2000 to SQL Server 2005 is being blocked as follows:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding
FTCATALOGPATH
DEPRECATEDSP
FTCATALOGNAMERESTRICTION
FTNONPERSISTEDCOMPCOL
Many thanks
JMX
Hi,
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403)
Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
2)
Command attempted:
{call sp_MSensure_single_instance (N'Merge Agent Name', 4)}
Error messages:
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368)
Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036)
Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @retcode = -1 and thus cannot obtain exclusive lock on resource
EXEC @retcode = sys.sp_getapplock @Resource = 'Merge Agent Name',
@LockMode = 'Exclusive',
@LockOwner = 'Session',
@LockTimeout = 0,
@DbPrincipal = 'MSmerge_PAL_role'
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
can anyone help?
Thanks
Hi All,
I had two Window NT 4.0 Server, say A and B... We recently upgraded from MS SQL Server 6.5 to MS SQL Server 2000 on Computer A, and for Computer B, I installed SQL Server 2000 from scratch. These two have a same RAM(512MB) and CPU speed...so the setup for hardware is almost identical...
For server A, there are around 10 connection to this SQL Server...
For server B, there are also around 10 connection to this SQL Server...
The database for SQL Server B is a copy from SQL Server A.... I restored the database on SQL Server B from the backup dump of Server A...
We have a store procedure called usp_GetMemo(ID Interger) ... we feed ID number to this store procedure and return its return Description... this table has ID column and it's Non-Cluster index, allow the duplicate row... there are 1.7 million records for this table...
Here is problem... whenever i execute more than 100 times for this store procedure(usp_GetMemo(ID)) continuously, the CPU usage of Computer A is 3 times bigger than computer B....
I did run the command "DBCC DBReindex" , "Update Statistics" for this table on computer A, but did not make any difference...
Keep in mind that Computer A has been upgraded to SQL server 2000 while Computer B installed from scratch... would that make difference somehow?? Before the upgrading, the CPU usage of computer A is the same as Computer B...
Any help will be really appreciated,
Thanks alot,
Kim,
I don't have any idea about upgrading databases.I am been given this task.
It would be great if you let me know what are all the things to be considered upgrading the sql server 2000 databases to sql server 2005.
Please let me know
Thanks
Is it just me, or are features missing in Management Studio? I mean, where is the "Export Objects" option when exporting data? Why is it so difficult to register a remote server? Why do the object views suck? And most important, why is the documentation the worst software documentation I have EVER SEEN?!
Things that were easy in Enterprise Manager with Client Network Utility and Query Analyzer seem impossible, difficult, or maybe just hidden in Management Studio. If it is there, the documentation sure doesnt tell you how to find it.
Please someone tell me that it's just me. Tell me that the features are there but Im not doing something right. I feel like putting my head in between my door opening and banging the door against it.
I am trying to run the SQL Server 2000-Switch application to upgrade my 6.5 database to SQL2000. The error I am recieving is error 8344, which on Microsoft website, states : Insufficient access rights to perform the operation. I have checked all of the rights on the servers. Microsoft states that each SQL Server service account must have a domain account logon, and it does, and the service account on the box must be a local admin on the box, and that it is. What happens is I select the export and import server and then it stops and starts services, and then returns to the exact login page.
Any suggestions????
Thanks
Hi, I am working on upgrading SQL Server 6.5 databases to SQL Server 2000 to a new server. I was not able to find details documents on that. Can anyone give me some ideas?
View 1 Replies View Related
Hi,
I would like to find out if there is any way to upgrade SQL Server 2000 (Ent) to 2005 (STD)
The Instance has many logins and jobs etc and I dont want to loose those
A document or some advice on how to go about it would help
Thanks
How do SQL 2000 service packs play a role in upgrading? That is, can SQL 2000 Standard with no Service Packs(SP) be upgraded to SQL 2005 Standard, or does SQL 2000 Standard have to have a certain service pack??
View 1 Replies View RelatedHas anyone attempted an upgrade from sql7 to 2000? is it a difficult process? what happens to the users. Is there a good site i can go to to get this info ?
Thanks in advance
Anyone know of any issues I should be aware of when upgrading from sql 7.0 to 2000? Is it a problematic proccess?
liz
We are currently still running SQL6.0 on NT4 server, and we want to upgrade to SQL2000. My question: how easy is it to upgrade from SQL6.0 to SQL2000?
View 3 Replies View RelatedCurrently running SQL Server 7, and have databases. I want to upgrade to SQL Server 2000. How can achieve it without delete or losing my databases. This is NOT a production server, BUT I still want to keep my databases. Ideally I would like to uninstall and reinstall so that there are no SQL Server 7 files lying around when I have SQL 2000 running. Thanks.
View 1 Replies View RelatedHi,
We are trying to upgrade from SQL Server v7.0 to SQL Server 2000. Here's our set up,
Current Server: Win NT, SQL Server v7.0
New Server : Win 2000, SQL Server 2000
Client (my PC): Win XP, SQL Server 2000
The New Server is designated SQL Server machine -- company-wide. That is, all the apps/projects uses this machine as the SQL Server. It only has one instance of SQL Server running.
Different project are assigned a dedicated 'Drive' (logical only) and allocated certain disk size as the work space. We (my team) will be the new entry for this server.
Q: When doing the Copy Wizard (from my PC) to upgrade/copy the existing v7.0 db (from Current Server) to New SQL Server 2000, do I need to specify the physicall 'Data' folder? Or, can I copy the database to the selected path -- which is my dedicated drive?
Thanks in Advance.
_msd_
Have an old PII server running Windows 2000 and SQL 7.0.
We just got a new box, Windows 2003 and SQL 2000.
Is there some kind of upgrade advisor or anything for me to read so I can prepare for this upgrade?
I'm most curious about how to properly transfer my data from the old box to the new.
I am currently running an active/passive cluster NT4 with SQL7 clustered. I am trying to upgrade SQL to a clustered 2000 version. I have a san disk area allocated as a Z: drive. These are the following steps I have taken:
1. Used cluster wizard to uncluster the SQL 7 instance.
2. Using the SQL 2000 Enterprise cd created a new virtual server (with the same IP address and name as the previous SQL 7 server) I have left the install as a default instance.
3. Part way through the install I am asked to browse to the data area. The data area is Z:mssql7data.
On completion of the install I now have the following data path Z:mssql7datamssqldata and all the databases are still SQL7 databases.
My questions are:
How can I get the install to update/convert the databases to SQL 2000 as it doesnt seem to recognise them?
Will the install always suffix the data path with mssqldata
Any assistance appreciated.
Ok another "I Don't crap about SQL and should read the book" question:
I am purchasing new servers for a company that currently runs SQL 2000 in a Windows 2k3 environment. Not sure why, but they want to upgrade to SQL 2005. The have 4 SQL 2000 Standard editions. Three with 1 processor licensing and 1 with per device licensing. The new servers will have 2 x Quad core processors. Since I know licensing is per "Physical Processor" I need to purchase an additional license for a second processor on each machine that has two. How do I purchase a second one? Can do this online? Whats the cost? Another question I have is: Do I need to buy SQL 2005 Standard (Full Standard Version) install on the new machine and migrate by databases from SQL 2000 over to the new ones? Or is there like an upgrade kit where I install SQL 2000 on the new ones then buy a update to SQL 2005 disc? Please don't laugh at my questions, I am by no means a SQL GURU. Thanks in advance.
I have a backup of SQL Server 6.5 database, but can no longer locatemy 6.5 server software. I would like to upgrade this backup to SQLServer 7 or 2000 ( i do have this software!) , does anyone know ifthis is posisble without the 6.5 software?If the answer is no, does anyone know where i could find/buy SQLServer 6.5, so that i can do this ?Thanks for any help.Rob
View 1 Replies View RelatedHello
After installing Sql server 2000 STD Sp1 on a server with Windows 2003 server, i have upgrade my Sql server to Sp4.
All the setup has been terminated without errors, but if i execute on Q.Analyser : "Select @@version" on the end of line of my query result , i have ....(Service Pack 1)
I don´t know , if effectively the upgrade has been terminated with sucess.I try to restart my server several time , but the result of my query is always the same "....(Service Pack 1)"
Also, on my firewall server , i ´am create an UDP port 1434, because my ODBC client machine was enable to connect to my server.
Could you give me an explanation about, this question, and if i really done the upgrade to my sqlserver.
Many Thanks
Luis
I was with online chat with Microsoft, and the guy said there is no upgrade option between SQL versions like there is from Windows XP home to Pro, or 2000 to XP. Is this true? Has anyone else done this before? I'm wanting to upgrade from SQL 2000 to SQL 2005. I was hoping there was a 32-bit to 64-bit upgrade as well within the versions, but that doesn't seem available either. I will settle for SQL 2005 32-bit if I can upgrade, but if I have to buy a whole other license for it, I might as well get x64. If anyone has done this or has experience in this, any information would be much appreciated!
View 1 Replies View RelatedAny expert in the house willing to show me how to upgrade from SQL2000 to SQL2005?
Thanks!
Hi everyone,
I want to upgrade SQL server 2000 to SQL server2005, what are the issues which I have to look at during my upgrading process, what sort of problems might be faced during the upgrading?
Lot of thanx
Please recommend best learning material for quickly upgrading skill sets from SQL 2000 to SQL 2005