I am looking in to using Microsoft Clustering supported in NT Server Enterprise to provide failover support for 2 database servers running SQL Server 7. I was wondering if anyone had any experience with it--good or bad. I read the white paper and it sounds good, but I'd like to get some real
world application experience.
Thanks for any info.
Bob
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.
View 3 Replies View RelatedDear All,Access adp on sql-server 2000After upgrating to A2003 updating data with 1 perticular combobox causes theprogram to hangs without any error-msg.Traying to change te combobox recordsource i get this error:This version of Microsoft Access doesn't support design changes to theversion of Microsoft SQL Server your project is connected to. See theMicrosoft Office Update Web site for the latest information and downloads(on the Help menu, click Office on the Web). Your design changes will not besaved.The solution in :http://support.microsoft.com/defaul...kb;en-us;313298tolks about SP 'dt_verstamp007' but I have SP 'dt_verstamp006'What should I do.Is the failure of the combobox also caused by the absence of dt_verstamp007???Filip
View 2 Replies View RelatedI have a 2 node Microsoft 2000 cluster with a shared storage device. Iwant to create automatic failover for MS SQL 2000 server. I can dothat wit the following options:1. Active/Pasive (one instance installed)2. Active/Active (More then one instance/virtual sql serversinstalled)I have a question about option 2.Is it possible to have more then one instance/virtual SQL server,service only one database for example loadbalancing. ?, or when youcreate multiple instances/virtual SQL servers, does that mean you havemultiple databases ? If not why does a Virtual SQL server has to betaken over by a cluster node that didnt fail. Then you can actuallyuse option 1. Please advise!The documentation is not very clear on this issues.Regards,Nico de Groot
View 1 Replies View RelatedHi all,
We are the studying the possibilty of implementing SQL - Clustering for
Failover server.
Are there any third party tools readily available.
Any suggestion or checklist ??
Any suggestions or comments will be appreciated.
Thanks and have a great day.
Dear Friends,I wanted to configure Failover cluster for SQL Server 2000 on Windows2000 advanced servers.I have only 2 no.s of windows 2000 advanced server m/cs. I dont haveany shared disks and SCSI drives. Can I still configure the Failoverclustering?I would like to know more about the need for the shared disks in theFailover clustering.Please shed some light.RegardsKumar
View 1 Replies View RelatedDoes anyone know how to obtain the physical server name that a SQL failover cluster instance is running on through the system tables or other database commands? Thanks in advance.
View 3 Replies View RelatedI have two SQL 7.0 SP1 (WinNT 4.0 SP 6.2) Servers using Clustering.
Problem: When SQLBox1 goes down, the Failover sends it to SQLBox2. When
SQLBox1 comes back up, the node stays on SQLBox2, instead of going back to
SQLBox1. This happens over 50% of the time, but not every time. Sometimes
it works fine.
I have done 3 hours of research, and can not find anything on this problem,
can any one a tleast point me in the right direction. I can hardly find any
troubleshooting on this issue. I do have January 2000 of the MSDN Library
installed on my machine if that helps, but there was not much on it in there
either (at least not that I found).
:confused:
In evaluating/comparing MS Clustering vs Hardware Failover Blades, has anyone come across any disadvantages/concerns for a Hardware Failover Blades.
Why would you install MS SQL 2000 Clustering when you can use a Hardware Failover Blade and use a SQL 2000 standard edition. e.g In an event a hardware failure occurs the admin manager brings over a standby hardware blade and reassigns it to the SAN (on which OS and SQL 2000) is installed and you are up and running.
Would appreciate any comments and suggestions to compare these solutions.
Thanks
how to configure email in SQL server failover clustering. I need to configure email to send when node switches from one node to another. best way to configure email in fail over clustering?
View 1 Replies View RelatedI tested the failover clustering for SQL 2008R2.When I stop the SQL server services manully, the failover did not fail to another resource. At the Faiolover cluster manager, SQl server(MSSQLSERVER) only show the status for offline. I think it should be move to another owner intead of just show as offline.
View 3 Replies View Related
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
http://www.microsoft.com/sql/howtobuy/activepassive.mspx
My questions are:
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 ?
Could I implement a failover cluster solution on the two DBs which are based in two different cities?
Possible?
Hi All,
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.
Any help?
Thank you!
Hello.
I am confuse and cant decide on how to setup high availability on our SQL 2005. Here's what on my mind and on resources list:
I plan to have mirroring on my SQL1 to SQL2 with the help of SQL3 as witness. So this would be automatic failover. My idea on mirroring is when SQL1 goes down, SQL3 would tell SQL2 to run and be the primary. It will automatically failover to SQL2. Right? My questions are:
1) How can I revert back to SQL1 once it is ready?
2) I read in one of the post that it is impossible to write in a mirrored DB, is this true? I mean, what's the use of failing over to the next node when it's not possible to write and update data/records?
3) If number 2 is false (i hope so), how would the data be synchronize from SQL2 back to SQL1. Those transaction that were made while SQL1 is down.
4) How about the connection string from the web applications? Would it be automatically point to SQL2? We have load balancing setup in place, would this help web application connection to automatically point to SQL2?
Another setup:
We have SAN in place (not yet used, but is planning to use for this SQL thing), EMC to be specific. My question would be:
1) For SAN setup, the data storage would be centralize. So would that mean that SQL1 and SQL2 services will use the same data and log file from the SAN storage?
2) How would you call this setup then? Can this be clustering type of high availability? Will clustering work under load balancing setup? I believe mirroring is not possible here? Right?
3) How can I setup my 3 SQL servers with the same theory in mind: when SQL1 goes down, SQL2 will take over. Data will be synchronize when SQL1 is up and running again. With automatic failover and reverting back to primary.
I read so much topics about this, but the more I research, the more I get confuse.
Any suggestions, comments, advice is greatly appreciated!
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
Does anyone know when Microsoft is due to end support for 6.5?
View 1 Replies View RelatedWhen does Microsoft support for 6.5 end? I am anxious to get rid of my old 6.5s but won't get approval until MS finally pulls the plug.
View 1 Replies View RelatedHi ,
Does microsoft supports MSDE still or it will support only Sql 2005 Express edition.
Has anyone heard that microsoft is dropping support for their sql language and going just with the ansi standards?
Just curious.
Hello,
I would like to see if Microsoft has issued any announcement on SQL Server 2000 end of support. If anyone is aware of this or seen new posts/articles, please let me know.
Thank you!
I was wondering if Microsoft SQL Server support any partitioning method (like range, list, hash or composite partitioning in Oracle) or you have to partition all tables manually?
Thanks in advance,
Bracia
Does Microsoft officially support installing SQL 2005 Express on a server where SQL 2000 Enterprise Edition is already running (a has to keep running).
In case they do, where do i find this official info / note.
Have they released white papers on this matter?
I know it is possible to install the two together and that they can coexist, but I am worried about how the two SQL installations wil behave when being updated with patches, security updates, service packs etc. do you run the possibility of them corrupting each other? Therefor it is vital to know if Microsoft supports the two running on the same system.
I got this system error log in the event viewer every time I start the SQL Server cluster resource:
The Microsoft Clustering Service failed restore a registry key for resource SQL Server when it was brought online. This error code was 2. Some changes may be lost.
Even though the SQL seems to be working fine now, I won't know if something drastic will happen later. :confused:
Searching the Internet for resolution, I saw this article. The Microsoft Knowledge Base Article - 307469 (http://support.microsoft.com/default.aspx?kbid=307469) requires using the Windows Server 2003 ClusterRecover utility to reset the server cluster check points.
I've not tried it because I don't know if this is the correct solution or if it will work or not.
Can I even solve the error without using the above utility? I also cannot afford to reinstall the clustering or SQL server. :mad:
Thanks in advance. :)
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'm trying in vain to upgrade sql server 2000 to 2005 with great headache and pain.
I (finally) have removed all Beta, and other incompatible version of .NET, Visual Studio and any other offending components, and made it to the first page of the install shield.
The .NET 2.0 components installed fine - but I get a fatal error trying to install the SQL Server Set Support Files.
I do have a log file - and have tired searching on the various error codes in it, but am coming up blank. Please advise - this is taking forever!
sample of error msgs in log file:
MSI (s) (B0:E0) [12:33:06:613]: Note: 1: 1935 2: 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.NetEnterpriseServers.ExceptionMessageBox,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:613]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:613]: Executing op: ComponentRegister(ComponentId={52723CBD-3400-458C-988A-4D012E6CAEDB},KeyPath=<Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:629]: MSCOREE not loaded loading copy from system32
MSI (s) (B0:E0) [12:33:06:629]: Assembly Error:Function not defined in specified DLL.
MSI (s) (B0:E0) [12:33:06:629]: Note: 1: 1935 2: {52723CBD-3400-458C-988A-4D012E6CAEDB} 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:629]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
MSI (s) (B0:E0) [12:33:06:629]: User policy value 'DisableRollback' is 0
MSI (s) (B0:E0) [12:33:06:629]: Machine policy value 'DisableRollback' is 0
Action ended 12:33:06: InstallFinalize. Return value 3.
mandpenny
I am trying to configure distributed transaction and XA support using Microsoft SQL Server 2005 JDBC Driver. I have coppied SQLJDBC_XA.dll from XA directory and placed in my sql server binn directory and trying to run the script xa_install.sql from binn directory with command as below :
C:Program FilesMicrosoft SQL Server80ToolsBinn>
osql -U sa -n -P admin -S localhost -i C:JavaLibrariesMS SQL Driversqljdbc_1.2enuxa xa_install.sql
But I am getting error saying :
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
when I replaced local host with the machine name it gives error :
[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen (Connect()).
where in I am able to test connection from Websphere using the same connection.
Please help some one ....... I am in URGENT need.... I need to enable XA suport for my application to run........
Thanks ----
Hi guys,
I have problems installing SQL server 2005, any help ??
Tks...
This is the log file description...
=== Verbose logging started: 25/12/2007 21:05:41 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: c:Archivos de programaMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (AC:50) [21:05:41:656]: Resetting cached policy values
MSI (c) (AC:50) [21:05:41:656]: Machine policy value 'Debug' is 0
MSI (c) (AC:50) [21:05:41:656]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (AC:50) [21:05:41:656]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (AC:50) [21:05:41:656]: Grabbed execution mutex.
MSI (c) (AC:50) [21:05:41:671]: No se puede conectar al servidor. Error: 0x80040154
MSI (c) (AC:50) [21:05:41:671]: Failed to connect to server.
MSI (c) (AC:50) [21:05:41:671]: MainEngineThread is returning 1601
=== Verbose logging stopped: 25/12/2007 21:05:41 ===
I'm attempting to install the standard version of SQL server 2005 on XP SP2. I'm getting the following:
Errors occurred during the installation:
Error 1603 installing Microsoft SQL Server 2005 setup support files.
We have a Prinicipal, a Mirror and a Witness server. We have automatic failover configured between the Prinicipal and Mirrored server. When we stop MMSQL service on Prinicipal, not all the databases failover to the Mirrored instance.
Any suggestions would be welcomed as we have a tight deadline to get this in Production.
1. Once fail over to secondary replica, what will happen to connected session in primary node? can the session fail over to secondary seamlessly or need to re-login. what happen committed transactions which has not write to disk.
2. Assume I have always on cluster with three nodes, if primary fails, how second node make write/ read mode.
3. after fail over done to 2nd secondary node what mode in production(readonly or read write).
4. how to rollback to production primary ,will change data in secondary will get updated in primary.
We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.
However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.
The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.
Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.
The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.
Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.
Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.
We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?
Are we missing a service pack on the client?
Thanks,
Kimball
1. In alwaysON fail over cluster, Once fail over to secondary replica, what will happen to connected session in primary node? can the session fail over to secondary seamlessly or need to re-login. what happen committed transactions which has not write to disk.
2. Assume I have always on cluster with three nodes, if primary fails, how second node make write/ read mode.
3. After fail over done to 2nd secondary node what mode in production(readonly or read write).
4. How to rollback to production primary ,will change data in secondary will get updated in primary.