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
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
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 ...
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....
We want to use sql 2005 failover clustering feature, so that upgrade sql 2000 is necessary. But some of the stored procedures built in 2000 are not working directly in 2005, set the compatibility level to 80 could make them work. In this case, can somebody here tell me if down grade the database level will affect failover clustering running properly? e.g. will data still be synchronized properly? Thanks in advance.
hi all....active/active. windows 2003 sp2. two nodes. two instances, each on a separate virtual server. my msdtc resource is in the cluster group. when i have the cluster group on one node, the sql instance that is running on the other node can't see DTC. Makes sense since the service is not up, but is this a problem? Seems strange to have a red stop sign on my dtc icon in sql management studio. I suppose I won't be able to run Distributed Transactions on that node, which kinda stinks. Wondering if anyone has seen a workaround.
I am new in clustering setup and I have a MSSQL2005 (Enterprise edition SP1 and Win2003 Enterprise edition) standalone production server and it will be setup with clustering and SAN. How can I setup the clustering? What are the steps?
I have a testing machine to setup new sql clustering which is working fine. I wonder how to setup from a standalone server. Kindly advise. Thanks in advance
Installing a SQL2005 active/passive cluster for the first time and have an issue/question. When running throught the SQL2005 setup and you have to enter the Virtual Server name, I enter the Virtual name that has been allocated an IP address and up pops a message saying the name already exists. Why is this? Surely the name and IP address have to be in place before running the setup. Slightly confused here.
I am trying to setup clustering for SQL 2005. I initially want to setup a 2 node cluster in Active/Active Configuration.
I am trying to understand the Quorum disk in SQL 2005. As I understand the quorum disk is a shared resource. How is this resource configured? Would I need to have an iSCSI or fibrechannel connection from each of the nodes to the shared disk?
As well, does each node have a separate data drive? Or do all the nodes use only the shared storage?
My company is planning on using a datacenter for our customers. These are manufacturing plants from which we collect batch and trend data (currently stored in SQL Server)
I am trying to set up a SQL 2005 analysis server cluster in our two servers, AS02 and AS04. The server cluster is built up on Majority Node Set (MNS). During the installation of the analysis service, I don't see the available cluster groups. In the cluster admin, the cluster is up and running fine. The MNS cluster has no shared disk, and it has two nodes.
Any thoughts or suggestions? or is it possible to built the SQL 2005 analysis service cluster with MNS?
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.?
I have a question about using MSSQL server 2005 standard edition in Clustering mode. I would like to build a msql cluster with only 2 servers (2 nodes).
I read here -> http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&DisplayLang=en page 5 that you can use MSSQL server 2005 standard edition in Clustering mode with 2 nodes.
But my question is : Can I use windows 2003 standard edition (Clustering mode managed ????) or I only can use windows 2003 enterprise edition ?
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.
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 ?
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.
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
