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
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
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 -----------------------------------------------
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
When I proposed start to use SQL Server 2005 for new VS 2005 web sites, one of my co-workers responded that
we will update the old SQL Server 2000 databases to SQL Server 2005 when we are ready to use 2005 SQL Server.
Questions:
1. Any expected problems to upgrade old 2000 databases to new 2005 SQL Server?
2. I have installed both 2005/Management Studio Express and 2000/Enterprise Manager in my PC. Any expected
problems when running both 2000 and 2005 SQL Server at the same database server?
3. What is the best configuration for running SQL Server 2005 when we have old 2000 databases? Upgade or not upgrade?
TIA,
Jeffrey
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.
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
I am planning on upgrading one of my SQL 7 servers to SQL 2000. This server is currently and will continue to replicate with a SQL 7 server.
I want to view our current replication jobs & schedules in plan text so I can check when I recreate the replication that I haven't missed anything. Does anyone know if this is possible?
Jon
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Thoughts?
Friends -
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
Please advise me and correct my steps.
Cheers
VSH
Since Upgrading from SQL Standard Edition to SQL Server EE we have been unable to re-attach the database files that we detached before the upgrade, to SQL Server Management studio. We get an error message that reads:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
CREATE FILE encountered operating system error 5(error not found) while attempting to open or create the physical file
Any help with this matter would be truly appreciated. Thank you.
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 RelatedI am upgrading from SQL 7.0 to 2005 and was wondering what the best method for doing this was. I tried simply backing the 7.0 database up to a file and restoring it back to the 2005 database. It seems to have worked because I can see all the database objects. The problem is that it also restored the users and I now have permission issues when accessing the data. I am not so shure it completely converted the database to SQL 2005. What is this compatability layer? Is there a prescribed method for upgrading the data, what's a good source for explaining how to do it.
View 1 Replies View RelatedHi 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,
Does anybody know of a way to rollback SQL Server 2005
databases back to SQL Server 2000? Is there a way of doing it without
resorting to Copy Database Wizard? I love to find a way of attaching a SS 2005 database
to a SS 2000 instance without any issues.
I recently upgraded to SS 2005 and I am very unhappy with the SS 2005 and I
want to rollback to SS 2000, which was a lot more stable. I am having
several major issues that are affecting my whole company's day-to-day
operations and the managers are not happy. Some of the issues include
night time batch running very sluggish for no apparent reason. This is a
biggest problem because it only occurs once or so a week and causes a disturbance
with the daily activities when the night time processing isn€™t completed on
time. The rest of the time, the batch processing runs great, even a little better then on SS 2000. I
don't believe it is a matter of my application needing to be retuned because if
that was the case, then why isn't it running sluggish every night? Also,
it's never the same day that the sluggish behavior occurs. If it was occurring
on the same night, then I would have something to investigate within our
application, but it doesn't. Another issue that I am having involves a
night time job that restores a copy of the production database to the Data
Warehouse server to be used for updating the data warehouse. Again, most
of the time it runs great (~2 1/2 hours), but once or twice a week, it goes
stupid and takes 6 1/2 hours for no apparent reason. Again, it is not happening
the same day either, which could give me something to invesigate. On SS 2000, this same job ran flawlessly. Never I did I run into situation that the
database restoration took that long to run. Even another issue involves a SQL Server Agent Job that was put into suspended
state. What's a suspended state and how can I get it out of suspended
state? I can find no information about suspended state in BOL. I
did a Google and nothing came up. If this suspended state was put
in for security reasons, great, but then tell me how I can remove the suspended
state. I am also not happy with the
fact that I can't get accurate information about the queries that are actively
running at that particular moment. In SS 2000, when I noticed high CPU
usage on the server, I would run the sp_who2 active stored proc and it would
show me all the active thread and how much CPU it was consuming. I would
then find the running threads with the highest CPU numbers and investigate the
query and see if we could improve it. Now in SS 2005, I get in the same
situation and run the sp_who2 stored proc, and there is no smoking gun.
All of the active threads are showing very little CPU usage, which I am very
suspect of. What the heck happen to sp_who2? I looked at some of
the other ways of looking at running processes (i.e... sys.sysprocesses) and
they don't appear to be giving the information that I need.
I am very unhappy and I just want to roll back to SS 2000 and wait a couple of
years before I upgrade to SS 2005.
Dave Brown
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
How do I upgrade Sql Server 2005 Express to SP2 if I also have SQL Server 2005 Enterprise SP2 already on the same box? I installed Sql Server 2005 Enterprise first, then applied SP2, then installed Visual Studio 2008 (which installed SQL Server 2005 Express).
When I try to upgrade Sql Server 2005 Express to SP2 using the special Express edition of SP2, I get an error message that says "None of the selected features can be installed". I end up having to cancel the install of SP2.
I'm left with SQL Server 2005 at level 9.0.3054 and SQL Server 2005 Express at 9.0.3042. How can I bring SQL Server Express 2005 to the same level as SQL Server 2005 Entperprise?
Hello!! How can I upgrade from SQL Server 2005 Express Edition to SQL Server 2005 Enterprise Edition? I see allot of example of upgrading from SQL Server 2000 to SQL Server 2005, but no example on upgrading from SQL Server 2005 Express to SQL Server 2005 Enterprise or Standard. Is this possible?
View 6 Replies View RelatedI first tried installing the DVD and of course it told me I must use the command prompt installation method to include the line SKUUPGRADE=1. I found good references to this in the following links:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2208593&SiteID=1
http://msdn2.microsoft.com/en-us/library/ms144259.aspx
Below is the command I issued at the command prompt:
start /wait d:serverssetupsetup.exe ADDLOCAL=ALL INSTANCENAME=URHCS63SQL2005DSS UPGRADE=SQL_Engine SKUUPGRADE=1 /qb
My servername is URHCS63 and my instance is SQL2005DSS.
When I execute this command, a installation dialog box opens briefly and then disappears and nothing else happens. Here are the results of the bootstrap log file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Time : Thu Oct 25 16:17:48 2007
URHCS63 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
SQL Server Setup was interrupted. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Thu Oct 25 16:20:08 2007
Any ideas on why this is not working for me?
Friends -
Could any one of you provide steps for upgrading SQL Server 2000 cluster to SQL server 2005 cluster.
My environment is Windows 2003 server.
Appreciate your support.
Cheers
VSH
Has 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.
Hello,
at the moment I have the following problem:
We have installed a version of the MSDE 2000 Sp3 with our software since 2005. Now we install SQL Server Express 2005 in order to use the latest version and to be compatible with Vista.
We have never had any problems with the MSDE, so it was no problem that we installed the german version (by mistake) because there never was any output at installation time.
When we now upgrade the existing MSDE installing the new version of our software, there are often problems and there are error messages, unfortunately in german, which cannot be read by most of our international users.
The problem is, that there seems to be no possibility to upgrade the existing (german) MSDE with the english version of SQL Server Express 2005.
My question is, if it is possible to upgrade the german MSDE to the english SQL Server 2005 to enable our international users to read the error messages at installation time in english?
Thanks in advance.
Best regards,
Peter
I have attached the SAN, configured the Windows Clustering and I'm ready for SQL. SQL Server 2005 was already on this machine as a stand alone. I removed all of the software and I'm reinstalling SQL. The cluster option is not enabled. Any ideas why?
View 1 Replies View RelatedWe 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 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 RelatedOk 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 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 Related