I would like to know if it's possible to make a basic SQL cluster with
windows 2003 server and SQL 2000 standard edtition. It has to be a
basic cluster, I dont need it to be very quick, I can have minutes of
servers down and it's ok.
In case the answer is Yes, can you recommend some links to build it
up, please?
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 need to cluster two NT Enterrpise Servers with SQL 7 running on them. I have been looking all over the Net for info but not much luck. I need to have some specifics. Can you help me with some good sites or books or both? I have tried Microsoft and they had some info but not much.
We are in the process of consolidating all our SQL6.5 and SQL7 databases to a single SQL 7 server - once completed we want to setup a 2 node SQL7/2000 cluster on either NT4 Enterprise or W2k Advanced Server. I would therefore appreciate any advice in choosing between the two platforms based on cost, ease of setup & configuration and ongoing reliabilty & uptime etc - we currently have no NT4 Enterprise Servers so would have to purchase these licenses anyway. Correct me if I am wrong but I also understand that setting up a cluster on NT4 Enterprise is considerabely more complicated and time consuming than on W2K Advanced Server? Any advice would be greatly appreciated..
I have a job interview and I need to know what type of questions can be asked about working in a cluster environment, I don't have much experience in clustering, can someone please give me an idea?
I have a question relating more to documentation and support. I'm trying to find documentation on clustering.
I remember quite some time ago I found a white paper that literally walked you through every step involved in setting up a SQL Server failover cluster. I had also found a white paper that walked you through setting up an Active/Active cluster.
I've been going through Microsoft's site, but all I've found are little bits and pieces.
If anyone can point me in the right direction, or even provide a link, etc. as to where to find some good solid documentation, that would be awesome.
If i have an activepassive cluster for SQL Server, under what circumstances would it prompt to automatic changeover to the passive cluster ? Failure of the SQL Server, or let's say 1 user database out of 25 becomes suspect?
We currently have a cluster configuration that is running as failover with one shared SAN storage solution. Two servers running Windows Server 2003 Enterprise and SQL 2005 Enterprise. We have two nodes right now running in failover and we will be purchasing a third.
Everything is working now, but we would like to move to an N+1 configuration with two active nodes hosting a separate SQL instance each with one failover node. I've seen N+1 mentioned on about a dozen Microsoft websites, but I cant find any documentation on how to setup or configure this clustering method. Has anyone ever set up a configuration like this or seen any documentation on how to do it? Is it possible to run failover with three nodes, two of them being active?
Hi All, Is anyone can tell me the difference between log shipping and clustering? I look at it and I think that this is the same thing as they use two different servers. TIA
Does anyone know the answers to either of these, given that we are talking about an active/passive cluster using MSCS, and we use Groupwise for mail (don't ask!)?
1) How do I configure Agent Mail on the cluster under this setup?
2) How do I set up linked servers from this setup to other (non-clustered) SQL servers - I can set up the cluster virtual server as a linked server from the others OK, but the other way around doesn't work - perhaps not surprisingly, but is there a way around it?
I need some documentation on how to trouble shoot clustering SQL7EE. I have setup the cluster and looks like it is working but I missed somthing. When I test a failover by pulling the Network cable to the main network not the heartbeat network both boxes lock up. I can failover by powering down one box and using the MSCluster Admin. I am using NT40 6a on Dell PowerEdge 2400 and PowerValut 211s
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 ?
I am installing sqlserver 7.0 in cluster server. When I start with Installing the MSDTC and give the IP Address of the Virtual server, It is giving message:
IP Address is in use.
I couldn't able to continue the installation further
1. If I cluster 2 SQL servers in an active/active configuration and want to have a seperate disk array to house the data, do I need to have 2 disk arrays, one per server, or can I have one disk array?
2. When installing an application's database on the first(primary) sql server in an active/active configuration, do I need to install it on the second(secondary) server also? The second server will pick up the processes if the first fails.
For SQL 2000, what are the licensing requirements for a clustered environment? I thought you needed datacenter for the OS, is there a clustered version of sql server, or do you need 2 copies of enterprise edition. Also, if you cluster can you license sql cals for clients, or do you have to do by processor?
We are going to implement a SQL 2000 cluster in an active/passive setup. We are going to use multiple instances. What I am confused about is the naming of the virtual server and instances. In the microsoft documentation it states that all instance/virtual names must be unique across all nodes in the cluster. But the client always specifies the same virtual server name when connecting so how can the names be unique across all nodes??
I would have thought that if there was an instance created called inst1 on node A then during the installation that instance name would be replicated to the failover node B. When installing another instance on Node A do you have to specify a different virtual server and instance name on the failover node B??
I've clustering set up for my production server, My question is when Active sever goes down the Passive server comes up. But what happens when one database gets corrupted does the clustering take place or I've to work with restore.
Should SQL Server 2000 (Enterprise edition) running on a Win2K Advanced Server (Active / Passive) cluster fail-over seamlessly?
We have been assured by our suppliers that current client connections (ODBC using TCP/IP) cannot be maintained during a fail-over. The result is that during a fail-over the client applications crash and users have to restart.
Do we have to modify the client application so that during a fail-over it will attempt to re-establish a connection?
Pointers to any resources for SQL 2000 clustering would be gratefully received (especially any which support the view that fail-over should be seamless).
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..
I have had questions from management about whether SQL 2000 clustering on windows 2000 is any good.
We are looking at spending *quite* a bit of money to implement it, but I want a "from the trenches" opinion of what its like , from the people that actually use it & look after it.
e.g.
DOES IT WORK LIKE IT SHOULD???????? Is it reliable? Is it resource hungry? Can I trust it to do what its supposed to do?
All repsonses very welcome. No response too small.
Dear all, i've read in a article that clustering and it states that clustering is possible with windows 2003 server only. is it not possible to create cluster (i'm planning for fail over clustering)? if so, is there any software for that?
and one more thing is there any free downloads for eBooks of sql server?
thank you very much
Vinod Even you learn 1%, Learn it with 100% confidence.
server: QAT on clustering server ----> 23 seconds ---------------------------------------------------- SS 2000 developer edition SP4 win NT 5.2 (3790) SP4 MeM 7935 MB processors 4 root directory C:program files... use a fixed memeroy size 640 MB
reserve physical memory for sql server minimum query memory 1024 kb
use all available processors minimum query plan threshold for considering 5
PROFILER READS = 5234
server: MILLER ----> 3 seconds ---------------------------------------------------- SS 2000 developer edition no service pack win NT 5.2 (3790) SP4 MeM 2047 MB processors 4 root directory f:MSSQL$INAQAT
dynamically configure sql server memory
use all available processors minimum query plan threshold for considering 5 PROFILER READS = 598
---------------------------------------------------- Making story short. I got an application that hits only 1 database called RECORDS. I'm getting different duration when running an application. 23 and 3 seconds. Same database, same objects and same application. SERVER QAT is our staging server, means lots of databases SERVER MILLER is just a server i just assembled, means just one database (RECORDS).
Not sure if it's because it's a clustering server that is causing the issue nor the reads. If its the reads, what is causing it? Do you think is the how the memory is configured?. Will the experts pls stand up?
Guys, I really need a help . I have one database (1TB) on two servers in different location( About 1200 miles distance). SO which options will be good: Clustering or Database Mirroring
I am totally confused . As i read from SQl-server- performance , Clustering doesn't protect data. It is server level.