We are running a two-node cluster for SQL Server 2000 Enterprise on Windows Server 2003. Each node has four processors and 4GB RAM. Our application is hosted on a seperate IIS server with 150-200 connections accessing the database via ADO.NET (ASP.NET 1.1). Our processor utilization has been high, averaging around 80% and out context switches/sec counter averages around 15,000. We are not using NT Fibers and our performance seems to be sluggish when the context switches/sec counter is high - over 10,000. In peak periods we se this counter hit 30-50,000. I have read articles that state NT Fibers have better performance in machines with 8 or more processors. Is this something that would also help in a four processor machine? The SQL Server is dedicated to SQL, i.e. there are no other applications running. I am also considering using the "Priority Boost" option... do these options really improve performance? I'm trying to squeeze as much performance out of these machines while waiting for new hardware to arrive. Thanks.
I am looking for some recommendations for memory sizing and options for a SQL 2000 Cluster. This is a two node cluster built on Windows 2003 ENT SP1 (x86). Both the nodes have the following hardware:
- 4 x Dual Core AMD Processors - 16 GB Memory - EMC Shared Disk
We are running six SQL 2000 instances and don't expect each of these instances to use more than 1.7 GB of memory. All these instances are going to support BizTalk 2004 Databases. I already have /PAE enabled on the nodes. I am looking for the following answers:
- Do I need to enable AWE on all the instances even if the instances ? Currently, we don't have that enabled and we have seen some issues regarding excessive paging even when there is physical memory available. The DBAs think that we don't need to enable AWE. I am bit confused on this one.
- We normally run 3 instances on each node and would like size the cluster in such a way that it can take six instances in case of a node failure
I have two Windows 2000 servers (Advance Edition) to form a Windows Cluster. I also install MS SQL 2000 Enterprise Edition on the cluster to form a MS SQL cluster. Now, I want to upgrade the hardware and OS (but keep on using SQL 2000), so I install Windows 2003 server Enterprise Edition on two new servers to form a new Windows Cluster. I am planing to install MS SQL 2000 Enterprise Edition on the new cluster, so the old SQL cluster and new SQL cluster are side by side. I would like to know how to setup a new SQL cluster (I know it has problem to rename SQL Cluster name, so how to fix this problem)? And how to transfer everything (such as system databases, users database, sql user account, password and maintenance plan jobs etc) from old SQL cluster to new SQL cluster? And how to switch over from old SQL cluster to new SQL cluster?
I see that UPGRADE may only have a value of 'SQL_Engine', so I'm assuming everything relies on the version of the engine. I also see that every cluster install requires certain options that are not specified in my command - which is why I'm a little confused - you can see that info a little below this link - "Parameters Required for Cluster Installations". But I'm thinking this isn't a install, but an upgrade.
When upgrading servicepack for SQL Server 7 in a Windows 2000 cluster, do I need to uncluster the servers before installing SP? Install on Node 1 first?
Current set-up: three node cluster running Windows Server 2003 Enterprise Edition SP2 with two instances of SQL Server 2005 Standard Edition SP2.
Virtual node 1: Standard Edition, default instance, Database Engine only
Virtual node 2: Standard Edition, named instance, Database Engine, Analysis Services and Integration Services
Physical node A: Prefered node for virtual node 1
Physical node B: Failover node for both virtual node 1 and 2 (thus having two installations of Standard Edition)
Physical node C: Prefered node for virtual node 2
We started off with this set-up because there was no need for Enterprise features, and SQL 2005 supports failover clustering with two nodes in Standard Edition. Saved a bundle of cash, so everybody's happy. Now we need to run a solution on virtual node 2 that requires Enterprise features in Analysis and Integration Services, so an edition upgrade is required on virtual node 2. I have done some research and found several edition upgrade examples, but none that match the above scenario. We are running production on these machines, so I can't risk experimenting with command line options, I have to be right the first time.
Is it possible to mix two editions of SQL Server 2005 in one cluster? Can I upgrade virtual node 2 to Enterprise but leave virtual node 1 at Standard? What procedure do I have to follow to upgrade all three components of virtual node 2 to Enterprise Edition on both physical node B and C?
I have problem when installing SQL 2005 Enterprise to my Windows 2003 R2 cluster. I install the SQL instance on the first node in my cluster, it analyses the cluster and comes up with no errors or warnings, i answer all the installation questions and proceed with the installation. When installing the SQL engine I see the status changing as the instance is started and then stopped again etc, finally the status changes to "removing backup files" when it get an error that reports:
"The setup has encountered an unexpected error while Completing Commit. The error is: The specified module could not be found."
Unfortunately there isnt any more information to go on. Any help would be appreciated.
When the setup program tries to start the database service (the last step of installation), it indicates an error 29503.
The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (17058)
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?
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 migration few database from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server)
Problem :
- The performance difference observer was not much (Just 15-18%)
- The CPU Utilization goes to 100% immediately, when the software login screen appears and it sustains in between 90% to 100%
- Multi-User Access (3 or more concurrent users), the sql performance is tremendously slow.
Steps followed for Migration:
- We have used the backup and restore method to migrate the data from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server).
- We ran the DBCC DBREINDEX for each affected tables
- We executed the sp_updatestats procedure for all the tables
- Upgraded the DB compatibility version to 90
- Installed the SQL 2005 Enterprise Server (64 bit-Itanium Server) Service pack 2.
One thing that we observed, was the memory usage, on SQL 2000 the sqlservr.exe uses around 1.5 GB where as on the SQL 2005 its just 120 MB.
A normal select query on 2000 Server took 11-12 sec, having 10 lac records, and the same query on 2005 took 1 min (3-5 sec CPU process taken by sqlservr and rest by the Sever Management Studio.
The only differance noted was that on 2000 the entire data was displayed at one go where as in 2005 the data was displayed at the 1st sec, and was filling the rest in the buffer, and to finally display entire data it took 1 min.
Also
when we run this query
select * from sys.dm_os_sys_info
one column os_priority_class shows a value = 32 ? what does this means.
In the MSSQLSERVER SERVICES, properties, there is a parameter displaying value
Advanced > Running Under 64 bit OS = No ? what does this means.
Could anyone pls suggest as to how to increase the sqlservr.exe memory area, and also how the enhance the performance.
I have the cluster configuration on Windows2000 Advance Server. Is it’s possible to install Active–Passive configuration for SQL 7.0 Enterprise edition AND Active–Active configuration for SQL Server 2000 Enterprise edition on the SAME Cluster server? If it's will be work together?
I have heard there were problems whne applying sql sp4 to clusters on sql 2000, has anyone encountered this? problem is we are getting Error: 17883, Severity: 1, State: 0 which the cure is to apply this service pack sql 4 for sql 2000
If I have SQL Server 2000 ENT edition on a cluster active/passive. Do I need to apply the service pack on the active instance, and then bring up other instance and reapply? While I am at it, I believe I still have to apply the hotfix for the awe memory problem also?
i am using "sql server 2000 enterprise evaluation edition".i am running windows xp.i want to upgrade to "sql server 2005".so please suggest me a sql 2005 edition which provides functionality similar to sql 2000 enterprise evaluation edition and must be compatible on xp.please reply soon...coz i am working on my project.
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
Hey there I am an SQL noob, our bank has no real SQL Admin, we had onw that left but never had a good knowledge transfer. We have 2 SQL servers clustered. IBSQL1 and IBSQL2 they make up cluster IBSQL. We have 2 other servers IBIIS1 ans IBIIS2 and we noticed when installing apps on them that they could not see the database. Yet it can ping IBSQL. The problem is on IBSQL1 and 2 port 1433 is not listening or open. Thus on IBSQL it isn't either of course. I have read of all kinds of people having this issue and most have said you need to manually add a connection string "Provider=sqloledb;Data Source=machineName,1433;Initial Catalog=xx;User ID=xx;Password=xx" Problem is I do not know how to add a connection string.
I need step by step instructions since im new to this. Start/programs/etc..... Apparently it is not enough to open the properties of tcp/ip in the config util and say 1433. You need to reenforce it by adding that string.
As it stands I cannot "telnet ibsql 1433" it tells me to take a hike basically.
So is the connection string the likely cause? or could it be something simpler? Thanks in advance.
Hi,I need manuals, tecnical papres, instalation guide, etc abouthow to install one cluster sql server 2000 64 bits withwindows server 2003.It`s posible a need one document step by step about thisThanks,RaulGZ.
We wish to upgrade our hardware of two sql boxes onto a single cluster. One of our databases will not run on sql 2005 and so I wanted to know if it is possible to run an instance of sql2000 and an instance of sql 2005 on the same cluster.
This is possible or would it cause as a lot of problems?
Hi there Our ISP hosts our data on SQL Server Enterprise, but I also going to host the databases on my local machine. As it's just local would Standard edition do? If I migrate the databases over, will it work? Thanks in advance.
Is there anything significantly better in Enterprise Manager 2000 vs. the old EM from SQL Server 7.0?
If so I'd be willing to pay the $50 for the SQL Server 2000 Developer Edition to get it... if not it seems dumb to pay for anything when MSDE 2000 is free and I already have the old EM. (Although I have installed MSDE 2000 as a new instance and can't figure out how to get at it via EM.)
I have just discovered something with EM 2000. In the old days (SQL Server 7), you could right click on a table, choose OPEN TABLE -> SELECT ALL ROWS and get a nice little grid with the select results. The same is true in SQL Server 2000. One thing you cannot do is update a value in that result set, which WAS something you could do in SQL Server 7. If you try it in EM 2000, you get the error message "TRANSACTION CANNOT BE STARTED WHILE IN FIREHOSE MODE". ??????? Am I just missing something, or was Microsoft so worked up about putting XML into their product, they overlooked some of the simple things that were really appreciated (and sorely missed). If anyone can provide some insight, it would be appreciated.
Can the SQL 2000 Enterprise Manager be successfully installed and utilised on a pc that currently has SQL 7 and is used to administer other SQL 7 servers? Can the SQL 2000 Enterprise Manager be used to administer SQL 7?
is there any kind of problem if i continue to use "sql server 2000 enterprise evaluation edition"..the evaluation period is for 120 days and my project will complete by that period..shall i continue using that or there are any problems....
I am attempting to install MS SQL 2000 SP2 on a Windows Server 2003 Enterprise SP1 box. The only installer I can find on the disc is in the MSDE directory and when I run it it immediately gives me this error:
"This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package."
I have tried copying the install files to my local hard drive for install, I have checked the version of my Windows Installer (3.1.4000.1840). I have the SP4 updates ready to go once it's installed, but I just cannot get past that point. I know that the same software version has been installed on other Windows 2003 systems, so why would it have a problem on this one machine?
I am having trouble with sql server timing out. I have the timeout set to maximum, and the query I am running is pretty simple. The data is about 10+ million lines, but It should not have a problem running queries on this. plus the timeout comes before the expiration of the timeout setting. The strange thing is, is that sometimes it will work if you just keep running the query. Has anyone run into this, and is there a fix? Also, sometimes if i link the table to an mdb and run the query through access, it will pull the results! what is that about?
I have an MSDN License from Microsoft and I am trying to install SQL 2000 enterprise edition to my XP laptop. I get an error stating that SQL is not compatable with this operating system. It is only offering to install the client tools. Can someone give me a heads up here and let me know what is going on, because I know I had this installed before.
