CPU Usage Changed After Upgrading To MS SQL Server 2000 From MS SQL Server 6.5
Feb 1, 2004
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 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.
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
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
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
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.
Hi All,I'm a relatively newbie to SQL Server 2000, having come from a MySQLbackground.I'm creating my first Trigger statement on a table, and I'd like toknow how I go about performing an update on the row that was changedwhen the trigger was fired.To explain, I have 2 columns, one which contains a member number, theother which contains a flag that is supposed to indicate whether ornot the member number in the row has changed since the last time thetable was processed for updates.So, whenever the value in the member number field [memnum] is updated,I want to set the flag [igproc] to true.The best I've been able to do is:CREATE TRIGGER [updateignoreprocflag] ON [dbo].[dd_testtable]FOR UPDATEASdeclare @key as intIF UPDATE (memnum)select @key = recid from insertedUPDATE dd_testtable set igproc=1 where recid=@keyThis seems to work, but I'd like to know if there's a better way ofretrieving the recid value of the changed row to pass to the UPDATEstatement? Also, I read somewhere in passing that using SELECTstatements and variable assignments within triggers can cause problemswhen called from other applications; in this case it will either be aweb site using ASP.or an application developed in FOXPRO. I can't findwhere I read this originally, so it's entirely possible I imagined itor misunderstood it, but I'd very much appreciate it if someone couldconfirm whether or not this is the case?Many, many thanks in advance!Much warmth,Murray
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?
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.
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?
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..
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.
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
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
Good day to all of you I am faced SQL SERVER 2000 Memory usage problem. I am using Windows 2000 Server SP4 and SQL SERVER 2000 SP4. When User running some in-house application software, the memory for sqlservr.exe was increased . But, when user logout from the software. The sqlservr.exe did not decrease the memory. I have around 100 Users in my company. SQL Memory will countinues increase till max memory usage in CPU.
May i know how to order SQL SERVER need to purge memory when USER was log off from the Program? Or my SQL SERVER was corrupted /missing file?
Hi All,I had two Window NT 4.0 Server, say A and B... We recently upgradedfrom MS SQL Server 6.5 to MS SQL Server 2000 on Computer A, and forComputer B, I installed SQL Server 2000 from scratch. These two have asame RAM(512MB) and CPU speed...so the setup for hardware is almostidentical...For server A, there are around 10 connection to this SQL Server...For server B, there are also around 10 connection to this SQLServer...The database for SQL Server B is a copy from SQL Server A.... Irestored the database on SQL Server B from the backup dump of ServerA...We have a store procedure called usp_GetMemo(ID Interger) ... we feedID number to this store procedure and return its return Description...this table has ID column and it's Non-Cluster index, allow theduplicate row... there are 1.7 million records for this table...Here is problem... whenever i execute more than 100 times for thisstore procedure(usp_GetMemo(ID)) continuously, the CPU usage ofComputer A is 3 times bigger than computer B....I did run the command "DBCC DBReindex" , "Update Statistics" for thistable on computer A, but did not make any difference...Keep in mind that Computer A has been upgraded to SQL server 2000while Computer B installed from scratch... would that make differencesomehow?? Before the upgrading, the CPU usage of computer A is thesame as Computer B...Any help will be really appreciated,Thanks alot,Kim,
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
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
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.
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?
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.
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.
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.
we are having the same code base in both the environment but we have different version of SQL Server Version(Env 1 - SQL 2012, Env 2 - SQL 2008). We are getting the expected result in Env - 1 but not in the ENV -2. So we tried to get the SQL trace for the web request we found that Date format getting changed.
2012 - Date Format in the SQL Trace for the request '2015-09-10 00:00:00' which is working as expected. 2008 - Date Format in the SQL Trace for the request 'Sep 10 2015 12:00:00:000AM' which is Not working.
Complete SQL Trace for Request. Evn - 1 - SQL Server 2012 exec dbo.usp_GetWorkQueue @ClientName='CLT',@HasFilter=1,@FacilityName='',@StartDate='2015-09-10 00:00:00',@EndDate='2015-09-18 00:00:00',@OrderDirection='D',@StartIndex=1,@PageSize=20
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?
Hi Due to an impending acquisition the machine names of the SQL Server 2005 boxes are changing. Trying this in the DEV environment it seems that the SQL server instance name stays the same as the old machine name (It was installed using the default of the machine name) -- but the clients now won't connect with the old machine name, or the new machine name -- it only works with the IP address.
I'm guessing there's a sp_change_instance_machine_name or something along those lines but can't seem to find it in BOL. Can someone point me in the right direction?
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?
I have recently installed SQL Server 2005 (Developer Ed) + SP1 onto a VMWare based Windows 2003 + SP1 server. SQL Server works fine when connecting to it using Mangement Studio on Windows XP. However, I have noticed strange CPU usage on the server which seems to be caused by Management Studio (either directly or indirectly). When no-one is connecting to the server using Management Studio, the server happily ticks along with CPU usage around 1-5% range. However, as soon as someone connects to the SQL Server instance using Management Studio the CPU usage begin to go up and down constantly. The CPU usage ranges from 5-50% and it goes up and down (fairly regularly) every few seconds. It does this even when nothing is actually being done in Management Studio. The moment Management Studio is closed, the CPU usage goes back to normal. The processes on the server that appear to be causing the CPU spikes are services.exe and wmiprvse.exe. On a possibly connected note (though possibly not), the Security log in the server's Event Viewer shows that there are logins occuring every minute or so (most of the logins are from my account). Any ideas?
I am using sql server 2005 express. When I created a new database my schema name was dbo and my stored procedures looks like this: dbo.sp_name Now when I am creating new sp:s my schema name has change to DOMAINUsername: DOMAINUsername.sp_name My webb application cant find any sp:s with this schema name and I don't now how to change schema name back to dbo. What has happened, what is this schema name and why has my schema name been changed!? Please help me out!
