Does anyone have any information or know where I can get information about setting up SQL2000 and Windows2000 clustering? We want to set up 3 SQL 2000 servers on Windows2000 clustering. We cannot find any technical documentation about the 2 together. If you know of any books or sites please let me know.
View 1 RepliesDoes anyone know where to find a comprehensive step by step build document for clustering SQL2000 on win2k3
View 3 Replies View RelatedAnyone know where I can find some documentation on how to set up a 2 node cluster? Thanks
View 5 Replies View RelatedI want to install sql 2012 in a non-cluster windows servers, then set up Always-on between these 2 servers. Every article mentions Windows Clustering, and we dont have clustering for now.
Can I set up Always On, in a NON_CLUSTER environment?
Also where I can find instructions step-by-step installations of SQL Server 2012 and most importantly ALWAYS-ON.
How to remove clustering configuration in windows server 2008 r2 after it shows clustering events as critical and status down...
View 1 Replies View RelatedHi,
is SQL Clustering possible with Windows 2003 Standard Edition? I have read, we need Enterprise Edition but it is too expensive. is there any alternate solution?
Appreciate your thoughts on this.
Regards
Malik
We are planning to setup SQL Express on a windows os clustered environment and trying to shoot for a active-passive configuration. We know that SQL server 2005 has this ability and will be leveraging that for mission critial production applications, however there are several other apps that we intend to use internally and would like to leverage windows clustering. Has anyone done this?
- Should we share the INSTALLSQLDATADIR? If yes, then how to specify the SQL Express installtion on cluster node#2 that, "hey..utilized this dir as the data dir".
- Or Should we not worry about it, and only the databases that we create for our apps be on the quorum/clustered resource drive?
Any pointers?
I have configured two node cluster environment on vmware with windows 2008 r2 os.I want to configure sql clustering over it.but prior to that I ran failover clustering manager on node V1 to create two node cluster(node v1,node v2 and third node as a domain controller with shared storage using iscsi target).After I successfully created cluster with name SqlClus1 I shut down all my vmware.Now when I start them all and see clustering status I get error RPC server not found and Cluster server can not be connected.On my cluster manager page I see cluster events marked as critical for both nodes.and cluster staus down.
View 2 Replies View RelatedI have a windows 2012 cluster environment that consists of two SQL servers nodes with Quorum disk configured as witness.
Manual failover between nodes is working fine, however the sql instance virtual is not seeing the Quorum disk.
Moreover the Quorum disk has the same number as another cluster storage disk, is that considered a problem?
When I move the SQL instance from a node to anohter, should the Quorum Disk change ownership as well to that destination node ? if it is not changing ownership what would be the problem??
I want to setuo AlwaysON that requires Node and FileShare Majority Quorum settings..
I want to know how to configure File share for windows clustering ????
I am setting up my first sql node on a 2 node cluster and runing into this
The disks are already added into the failover cluster manager
I've come up against a wall with regards to adding login via a windows group. My end goal is to be able to manage sysadmin access to many servers via a domain group instead of via individual logins at each server.
I've got a mix of 2000 and 2005 servers, with a related issue for each. Searching far and wide has come up empty so far.
In each case below, the a login for the group was created via EM/SSMS, and set with the sysadmin role.
1. Domain Local Group
I added a domain local group "domainsql accounts" with myself among others as members, including the domain account for the sql and agent services.
Adding this group to SQL2005 worked fine, and authenticates my login as a member of this group. Oddly, xp_logininfo [domainsql accounts] , 'members' returns error code 0x8ac.
It does log me in, and it does correctly grant me sysadmin.
Adding this group to SQL2000 from EM, the group does not appear in the list for the domain. Typing it manually does recognize it as a group, but it does not allow login.
Review:
2000 fails login, fails xp_logininfo
2005 allows login, fails xp_logininfo
2. Domain Global Group
Next, I added a global group "domainsql dba", with myself among others as members.
This group IS viewable in SQL2000 EM to add as a login. Unfortunately, I still cannot login via windows auth. Even stranger, xp_logininfo [domainsql dba] , 'members' correctly returns the members of this group. I know SQL can authenticate that group, and I am part of that group, yet it won't authenticate my login?
SQL2005 fails to allow login but will also return member info via xp_logininfo.
Review:
2000 fails login, returns xp_logininfo
2005 fails login, returns xp_logininfo
The closest thing I found was a MS kb entry that suggested creating a local group, adding the domain group as a member of the local group, and adding a login for the local group. It didn't work.
Thanks for any offered suggestions
Chris
I have problem connecting to a SQL 2000 server that is hosted on a Windows 2003 server. My application uses classic ASP with VB6 components. VB6 components connect to SQL server and return data to ASP application. Everything was working fine when the application and SQL server was hosted on NT machine. Recently we have shifted to Windows 2003 server. Since then we could not establish connection to SQL2000.
I'm using UDL as connection string.
IIS and SQL2000 hosted on the same machine with Windows 2003 OS.
This seems to be a security issue. Earlier I faced this issue for a .net application which I resloved adding a domain account to both SQL server and IIS directory security.
Request your input to solve this problem.
Sunandajit Ray
Infrasoft Technologies Limited
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??
Please help!!!!!!!
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).
Many Thanks
Mark
Howdy,
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.
Thanks for your help.
Cheers,
SG.
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.
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
Are there any decent articles,troubleshooting guides,monitoring guides, books out there, which provide information on setting up SQL 2000 on Windows 2000 using clustering.
thanks
I have 2 Node Cluster with 2000 Advanced.
I have SQL 2000 Enterprise. I am trying to setup a failover cluster (active/passive)
I have tried to follow the Microsoft Documentation that came with the box but whe hey what do u know - cannot get it to work. I cannot understand the lines "install a default instance of SQL that runs on both". What does this mean?? I know what a default instance means but running on Both ???
Does anyone have document that will show me the steps.
thanks in advance.
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
View 1 Replies View RelatedWe are looking at clustering of SQL Server 2000 [standard Edition] using third party software, any inputs in this regard would be of great help
View 1 Replies View RelatedWe
are looking for clustering of SQL Server 2000 [standard Edition] using
third party software, any inputs in this regard would be of great help
Hi all,I have a Windows 2003 server, which is also a terminal server forapplication, with sql 2000 installed. My company has developed anapplication that uses SQL 2000 as its database. The application is aclient/server one. In each client computer there's a link to theapplication on the server. There is no problem with Windows 98,Windows 2000 pro, Windows xp pro clients, but the windows 95 onescannot log in to the database. The log of the application shows thefollowing error:connection error -2147467259. Cannot open database requested in login'database name'. Login fails.Till a week ago the application was running on a Windows 2000 serverwith SQL 2000 install and the W95 clients had no problem connecting tothe database, so my guess is the error has something to do withWindows 2003 server, but what'causing the error?I tried to install a newer version of MDAC (MDAC 2.5, the last versionof MDAC you can install on W95)but with no success. By the way W95clients have no problem accessing shared folder on the Windows 2003server.Any idea?ThanksMarino
View 1 Replies View Related
Does any one come across any difficulty in the following migration?
OS: Wondows Server 2K
DB: SQL Server 2K Standard Edition
Migrating to
OS: Wondows Server 2K3
DB: SQL Server 2K Standard Edition
Thank you,
Gish
We have a client running a 3rd party app on sql 2000 Enterprise on Windows 2003 Advanced attached to a new SAN. They are looking at adding another SQL server and clustering for failover. Anyone done this before. Do you have to reninstall sql server on the original box to do this. This a a heavily used app, so downtime is always an issue.
View 3 Replies View RelatedHowdy,
Is SQL 2000 clustering on windows 2000 any good ??
We are looking at spending *quite* a bit of money to implement it, but I need opinions 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?
Are there lots of bugs?
All repsonses very welcome. No response too small.
Thanks for your help.
Cheers,
SG.
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.
Thank you.
What are the main differences between the Enterprise version and the 'normal' version ?
Is it possible to link odbc-data-sources the the small version too??
Hi,
Just upgraded some development desktops to Vista Business. However we need
to still connect to some older remote windows 2000/SQL 2000 servers.
Trying to setup an ODBC system DSN on our Vista Business local desktop we get the
following errors -
-START ERROR WINDOW-
Connection Failed:
SQLState: '01000'
SQL Server Error: 772
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(SECDoClientHandshake()0.
Connection failed:
SQLState: '08001'
SQL Server Error: 18
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
-END ERROR WINDOW-
Any help greatly appreciated as this is stopping us from making
database/table connections etc. We've checked the firewall setup and all is well there.
PS - we can still connect fine using XP or windows 2000 desktops and their
local DSNs.
We have a SQL 2000 server that resides at a client. THey recently upgraded their exchange 5.5 server to 2000. I do not believe they are using Active Directory. However, our SQL Server can no longer send email. If we test it we get the error message "Error 22022 : SQL Agent error, you do not have permissions to perform this operation on this object" I found the below url to a MS error
http://support.microsoft.com/default.aspx?scid=KB;EN-US;q293422&
but ut seems to relate to someone using Active Directory. However this problem did start as soon as they upgraded to Exchange 2000. Has anyone else encountered this?
Hello,I received the error message below when i'm trying to install SQLServer 2000 standard edition into a Windows 2000 Professionaleworkstation.Error :Microsoft SQL server 2000 Standard Edition server components is notsupported on this operating system. Only client components will beavailable for installation.Any request modification ?Best regards,Thanks
View 1 Replies View RelatedI've just started getting this EXCEPTION_ACCESS_VIOLATION (0xc0000005) on machines using Windows 2000 sp4 connecting to SQLServer. This is crashing JVMs (multiple Sun versions and BEA also) in the Java VM frame (outside our code). This has just started recently - perhaps with the last set of patches? Has anyone else seen this or know what I could do to get more information? Could this be related to updates to named pipes?
Thanks!
-Brian Temple