I have a question about database clustering. I am loking for the solution for the databse scalability, performance and zero downtime especially for MS SQL Server. As my understanding (correct if I am wrong), only Oracle provides 2 DB Servers (parallel server) or NT clustering for two sql servers. The drawback for these solution is only one server is working and another one is standing by. It is not efficent (which only 50%). Is any way that I could built the DB server farm which every DB server is working, if one failed, throw it away, rest of them still working; if I need more power, just add another db server box.How to solve the data sync problem ? Replication is not good for more than 4 or 5 db servers in the farm. Disk mirror is not good since if the server is down, there is no way to access the disks. DO you have any good idea ?
We have 2 env. : Testing and Production, both are running Windows 2003 Enterprise Server with SQL Server 2005. The difference is Testing is NOT running Windows cluster but Production do so, what is the best way to transfer a database from testing to production?
We have another systems that both testing and production are running on NON-cluster and we use backup/restore to transfer the database, can it apply in this case.
And I found that there are a tools called DTC, which can transfer all DB objects from one DB to another, is it a best way to transfer between non-cluster and cluster env.?
Those of you who are using MS Clustering, what are some advantages vs. a third party product such as "Double-Take" ? If you have used "Doube-Take" I would be extremely interested in your thought of the product.
Is it relatively easy to setup and configure with and environment that's using all the standard products of BACKOFFICE (SQL Server 7.0 Standard Edition, NT 4.0 Standard Edition etc...)
Any hints, tips, etc... would be also GREATLY appreciated.
In a clustered sql server environment having two Nodes, configured as Active/Active or Active/Passive, do I need to create the databases on both the Nodes? I am not too sure about how to create databases in the clustered environment. Can somebody help..
Will removing the built in administrator account from the sql server cluster have any related problem with failover happening. Is it ok if i add the domain account under which sql server runs and add it to the local administrators box of both the nodes. I was thinking of not allowing the built in administrator account to access the sql server. Thought adding only the account under which the sql server service runs is enough which is also a domain account with local administrator privileges on both the nodes of the cluster.
I have tried to install SQL Server 2005 Standard edition with CLUSTERING. I faced a problem and everything rolls back.
TITLE: Microsoft SQL Server 2005 Setup ------------------------------
SQL Server Setup was unable add user domain1xyz to local group domain1IT Security Admin-Group.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29512&EvtType=sqlca%5csqlsecurityca.cpp%40Do_sqlGroupMember%40Do_sqlGroupMember%40x6ba
I have refered to PostI=1659185 posted by Fly and it still won't be able to fix my problem.
I have added LOCAL SERVICE into the local group (SQLServer2005MSFTEUser$AAA$MSSQLSERVER), but it still can't work.
Please can someone help me on this. Thank a lot....
Hello, Can anyone give me a site that shows Clustering on SQL Server 2000 step by step. I am trying to have two or more servers acting as one and to get high-availability without having any impact on the application side.
I have recently inherited an active/passive cluster. Sql server agent mail is sending notifications, but I haven't figured out how - yet. The active node is setup to start the mssqlservice with a domain acct. that is a local admin on the machine, but the agent is setup to start with the local system acct. The domain acct. has an exchange profile on the server. It was my understanding that the agent and the sqlserver service had to run under the same id for this to work? Are the ids listed under services on the primary node the ids that actually run the services - or are the services run by a different id? If so, can someone point me in the right direction?
Environment: SQL Server 2000 SP3a on W2K Advanced Server SP4. 1 IBM Server x440 with FastT700 Storage (Fibre Channel)
We need to buy another IBM Server x440 or x445 and we would like to make a cluster. Question 1: Once we build the Cluster with the installation of the Cluster Service, making the W2K Cluster, is it possible to upgrade the default instance of SQL Server to a default clusterd instance of SQL Server? In BOL I have found a note that explain how to do this but I have some doubts.
When I installed SQL Server I placed the system files on the C: drive, the DB files on our SAN on disk E: and the log files on disk F:.
Question 2: If we would like to use Windows Server 2003 what would be the possibility for an upgrade? I mean, should I erase all and start with Windows Server 2003 setup or can you suggest to upgrade the OS first, from W2K Advanced Server, and then cluster SQL Server if possible?
Can you advice please? Any help is really appreciated. Thank you very much for your time. Franco
If we have a stateful connection (RDS) and the database fails how will the application reconnect. I do not believe that our application was written using MSCS API. Therefore I don't believe that it caches the user logon and password to log back into the session. So, my question is can the application work with sql server clustering since it uses stateful connections? Any help would be greatly appreciated. Thanks
Hi, Please tell me that, What is Clustering in SQL SERVER 2005 Database? What is the main reason of Clustering in SQL SERVER 2005 Database? What are the advantages of Clustering in SQL SERVER 2005 Database? How can I implement Clustering in SQL SERVER 2005 Database? waiting for your reply with thanks T C
We are using a VB application with a "dsnless" connection. It is not able to connect to the SQL box using integrated WinNT authentication. Receive the below error message:
We can connect to our test SQL box with using the same application with no problem. The only difference we can see is the clustering on the "real" box.
We are using the following program string to connect to both boxes with the exception of the server we connect to:
I understand that to implement SQL Server clustering solution, it isnecessary to have Win 2K Advanced server. We are looking at 2Nodefailover solution on a 2CPU Pentium box. Is there a site where wecan find out the cost of Win2K and SQL server for this configuration.Thanks.Ravi
Hi all:I have a clustering SQL Server on Node1 and Node2, the Node1 has namedInstance1 and Node2 has named Instance2, no default instance. Wetested it that everthing is OK, then we decide to move to DR location.The relocation kept the same virtual and phusical server name, and wedid not change SQL Server server network utility. But server IPaddresses were changed(vitual and physical). We can start theclustering SQL Server as before, and everything looks like well.However the users can not access it remotely, and they did not changethe client network utility. But if I login the server,I can access itfrom Query Analyzer even though ther is not client network utilitysetup on the server. I can ping the vitual server name, how can I makesure the ports are working well? (We did not use the default port fornamed instance).I remember I did input the virtual server IP address when I installedthe clustering SQL Server. Of course, it was change after relocation.Is it the reason for failed remote login? If it is, how to fix it?Does anyboday know there is document for clustering SQL Serverrelocation?ThanksWillie
Pl clarify how to use SQL server 2005 clustering Algorythm , I want to use the case and nested table concept. Pl let me know what is key column , Input and product with an example
I have table in the following structure
Cust_id
Age
Product
Location
Income
the above mentioned columns are in my tableand i want to perdict which product is mostly likely to sold with other based on age , location and income
Pl clarify and mail me on rajesh.ladda@lntinfotech.com
I have 2 Windows 2003 r2 servers with a SQL failover cluster installed across the 2 node. Generally I have been running off node1 with node2 as the failover partner. I have purchased the correct licensing for noe1 and from the following I do not need to purchase a license for node2:
Failover clustering is a process where the operating system and SQL Server 2005 work together to provide availability in the event of an application failure, hardware failure, or operating-system error. Failover clustering provides hardware redundancy through a configuration in which critical resources are transferred automatically from a failing machine to an equally configured server to help ensure continuity of service.
When doing failover support, a server is designated as the passive server. The purpose of the passive server is to absorb the data and information held in another server that fails. A passive server does not need a license if the number of processors in the passive server is equal to or less than the number of processors in the active server. The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly
1) If I switch my cluster instace to point to node2 for testing node2 in case of a failover, would I need to purchase another licence ? This means I am not doing the repointing because of an 'event of an application failure, hardware failure, or operating-system error' ? Can you please provide information from MS ?
2) How are SQL Licences bound to the windows install in a SQL Server failover cluster configuration ? For instance if node1 legitimately fails due to an 'event of an application failure, hardware failure, or operating-system error' and you failover to node2. Then you think, stuff (forget about) node1 as I have 1 set of licences for SQL Enterprise already and therefore can run with a legitimate licence on node2. Can you please clarify ?
3) I have heard that only one server needs a license in a failover cluster. Then how does this fit in with any of the questions from above:
'The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly' ?
In the event of a legitimate failure, node2 would be running off the license purchased. So why are MS restricting the use of it for 30 days ?
I am getting ready to have a SQL Server failover cluster setup. I have used SQL 2000 for years, mostly for DTS and related database activities, but NOT in a cluster. I have used SQL 2005 for about one year but not intensively, and NOT in a cluster.
We need to set up a cluster. We are setting up a DELL EMC solution. I am going to hire a consultant to set it up, including the SQL part. My questions are should I use SQL 2000 or 2005? (I don't know if one is better than the other for clustering. Both are supported by our vendor for the application we are running.) How hard is it to maintain a cluster if one hasn't had experience in that area before? How should I prepare?
Any opinions or experiences that you would like to share would be helpful.
I am developing an enterprise class solution using SQL Server 2005 and MS .NET v2 and am tying determine if SQL Server 2005 (which edition and if so how) would be adequate for my proposed solution. Any feedback, tips, comments would be greatly appreciated.
As a background the solution I am developing will be web services based and used by multiple offices around the globe by over 500 users. I have already developed a prototype using a single SQL Server 2005 instance but as this solution is going to be used by offices around the world I want to have an IIS Server and SQL Server 2005 server instance in each office with "links" back to the primary SQL Server 2005 cluster in Australia.
One of my thoughts was to set up replication between the offices that would happen at midnight remote office local time and then set up triggers to update the primary cluster when assoociated data was changed on the remote sites or on the primary cluster. Does anyone know or can anyone suggest alternatives to this strategy?
I effectively need some sort of inter site caching functionality with store and foreward capabilities ...
We're planning to install a Server 2005 Failover Cluster and I'd like to find more information about licensing, etc. Basic questions:
- What is the best O.S. to run? Win 2003 or the new 2008? And what version (datacenter, enterprise)? - Since I'm going to use 2 machines, will I have to pay for 2 licenses (sql and windows - two lic. each)? Or just 1 license, since just 1 machine will be the active server?
This is for some web applications, so, web environment.
I am practicing on vmware 2 node failover cluster for doing Sql failover clustering understanding.I did proper Ad Dc setup and configured san storage through iscsi software that I downloaded from net.I did target and initiator configuration for san storage on same Domain controller vm.Name of target is Target1 and has two initialtor for node1 and node2.It has two virtual disk assigned Quorumdisk.vhd and sqldisk.vhd.ON vmnode1 I have initialzed and formatted my both disk with proper volume and label.
Node which are participating in cluster are node1 and node2.while my windows clustering went fine,while Sql server installation on node 1,i got error IP Address conflict occured.
my DC has IP address:192.168.1.10 my Node1 is 192.168.1.20 node2:192.168.1.30 Cluster IP address is 192.168.1.35
What has cause this situation.What configuration is needed.How do I troubleshoot this problem as now I can not install my sql for clustering as also gave me Invalid network name error.Is my storage configuration not proper or IP address is in correct?Do I need to put my virtual disk in Clustered shared volume?
