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.
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
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 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 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 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 am developing a windows application that needs to communicate with a remote SQL server 2005 database. Server allows remote connections and MSDTC service also running. Do I need to run MSDTC service on the client machine where I use desktop application ? any ideas ? It's throwing some error like An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
But my SQL Server allows remote connection, and I am able to do a select statement. But when I insert/update anything, it's throwing this error. I guess some problem with MSDCT. Anybody have any idea ?
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.?
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.
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 ?
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....
Trying to locate information on MSDTC. Is this "needed" to run SQL Server? That is, if this part of the installation is deleted, will SQL Server still function? Also, does anyone know if this is a crucial tool needed by Veritas Volume Manager or Windows Disk Manager?
If anyone knows of a link to this information, I'd appreciate it. My searches come up with lots on information on MSDTC, but nothing that answers my specific questions.
When i do a BEGIN TRAN to a SQL server sitting on Windows 2003 Server from a SQL Server Sitting on Windows 2000 Server, the Transaction hangs and if I try o kill it the Transaction is in ROLLBACK State.
I tried setting the Properties for the MSDTC and restarted the Windows 2003 Server but in vain
I keep getting this error on my application server...what does it mean?The description for Event ID ( 0 ) in Source ( ODBC ) cannot be found.The local computer may not have the necessary registry information ormessage DLL files to display messages from a remote computer. Thefollowing information is part of the event: Failed to enlist in DTC:SQL state 37000, native error 8501, error message [Microsoft][ODBC SQLServer Driver][SQL Server]MSDTC on server 'PROSQL' is unavailable..any help would be appreciated...thanks-Jim
I'm using msde. On the little icon in task tray, you have under currentservice, a choice of mssqlserver, and another choice is msdtc. What ismsdtc? And what is sqlserver agent?
The resource msdtc is down. Every time, it works pretty well , after we restart the servers(node1 and node2). But, about half a hour later, the problem is there. We reintalled msdtc. It didn't work out too. msdtc and sql server is on a cluster. Can anyone help me out?
I am running SQl 7.0 (SP4) on Windows XP Professional (SP2). Whenever I try an insert/update type of activity, the System returns the following message :
Server: Msg 8501, Level 16, State 3, Line 2 MSDTC on server 'SERVER' is unavailable.
However, all the required services including MSDTC are running on the System.
I have a class that use a TransactionScope object for make make two operations into a database. The problem is that in a computer works well but in another I receive a error message: "MSDTC is not running in .SQLEXPRESS". I had watched the services in the computer and the "Microsoft Distributed Transaction Coordinator" is running. Does somebody know what is happening? Thankyou and sorry for my English.
I am selectively insert data from serverA databaseX to serverB databaseX. (serverA is linked server on B.)
I could insert parent and child tables. But get error when insert to grand-child tables: Server: Msg 8501, Level 16, State 3, Line1 MSDTC on server B is unavailable.
Don't think I need to turn on MSDTC on B. But I could copy and paste from source A server to target B server. Confusing on some table could insert while others with error....
I have an ugent situation. Due to a failure we had to build a new db server for an application and this was done succuessfully. The application requires DTC and it was not intalled when we install SQL on the server.
How do I install DTC? Did I miss an obscure option during SQL install?
I recently moved & upgraded a database from 7.0 to 2000 that makes use of linked servers. After upgrading, a number of queries started failing with the error below. These linked servers with this problem either had a stopped MSDTC or were behind a firewall. I've read the articles on how to configure MSDTC to work through a firewall, but before I do this I'm wondering why this is even happening. There were no problems when the database was at SQL 7.0. Does anyone know why sql 2000 would need to use MSDTC, but SQL7.0 would not? I don't need to use a distributed transaction, so ideally I'd like to somehow tell SQL not to use MSDTC at all. Any ideas?
Thanks
Server: Msg 7391, Level 16, State 1, Line 1 The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction. [OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ] OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].
The following code:DECLARE @tsql varchar(1000)CREATE TABLE #Test (...)SET @tsql = 'SELECT * FROM OPENQUERY(MyDataSource, ...)'INSERT INTO #Test EXEC(@tsql)generates the following error message at the insert statement:Server: Msg 8501, Level 16, State 3, Line 4MSDTC on server 'MyComputer' is unavailable.Why?Thanks,Tony PerovicCompumation, Inc.
I have a SSIS package in which there are lot of Sequence Containers. Each sequence container has two Execute Sql tasks which brings 2 values, and if the comparison of the value is true, it runs a data flow task. Comparison is done using Expression.
If any of the sequence container fails the comparison, I wanted whole package to rollback so I had to use Transactions. I set "Required Transaction" on the package and "Supports Transaction" on each Sequence Container and Tasks respectively.
Now that I am trying to run the package, it runs few sequence containers fine and on few it gives this error.
[Execute SQL Task] Error: Executing the query "SELECT ISNULL(MAX(ClaimBillTypeKey), -1) ClaimBillTypeKey FROM dbo.Dim_ClaimBillType" failed with the following error: "Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Also, this is not consistent, one time one Seq. Cont will fail and next time it will run fine but something else will fail. What is going on????
I have set up two server and also created linked server between server1 to server2
I could select from there just fine but when i try to run tirgger on table server1 which updates in server2 it gives me error following: OLE DB provider "SQLNCLI" for linked server "Server2" return message "No Transaction is active" MSG 7391, level 16, state 2, Procedure servertrigger, line 34 the operation could not be performed because OLE DB provider "SQLNCLI" for linked sever "SErver2" was unbale to begin a distributed transaction.
I have configured on both server exactly same: with all the option: MSDTC > Security Configuration: Network DTC Access > TRUE Allow Remote Clients > TRUE Allow Remote Administration > TRUE Allow Inbound > TRUE Allow Outbound > TRUE Mutual Authentication Required > TRUE Enable Transaction Internet Protocol (TIP) Transactions > TRUE Enable XA Transactions > TRUE Account: NT AuthorityNetworkService on both server..
On server2 i tried remote proc trans to on and off but it did not help.