I have a 2 node SQL 2008 R2 cluster up and running fine. SQL1 is the main server and SQL2 takes over when 1 goes offline. Tested...working great. My question is regarding the Distributed Transaction Coordinator's role. I do NOT have a DTC configured and everything seems fine.
Why would I need the DTC? What situations would require one?
Thanks,
MJ
In my case - no. I'm running a SQL cluster (2008 R2 RU6) without DTC and everything seems fine.
Related
Scenario: ISS 8.5 is on our work machines, our Microsoft SQL Server is currently down for an indeterminate amount of time, and we don't have a back-up. We can continue to develop code on localhost. Because SQL Server is down, we can't execute any data transactions. Are there any reliable resources online to, at least, test if the developed SQL syntax is correct?
Edit: I will go ahead and eat my words. I had presumed that we were not allowed to install SQL Server Express locally. That was a bad guess. After I had sent our boss the suggestion from marc_s, he gave us the go-ahead. Now we have a back-up plan. For the record, the SQL Server is now online.
You must have access to another SQL server in order to test code against a SQL server. Your only options are to install SQL server on local machines, install SQL server on a local networked computer, or use a SQL server installed at a third party host.
Suppose I have 2 bootable partitions on my local machine with Windows 7 running SQL Server 2008 R2 on one and Windows 8 with SQL Server 2012 on the other.
Is it possible to run/attach the same database (created under SQL Server 2008 R2) on both versions of Windows so if I boot up Windows 7 I can run my application against it. And if I run up Windows 8 I can run my application up against that? Would there be any issues if I tried it - i.e logins?
Thanks,
Andez
No, that won't work.
As soon as your SQL Server 2012 version would access one of the database, it will upgrade it to the latest internal database version for the 2012 version.
And once that's happened, the SQL Server 2008 R2 cannot use that database file anymore.
The best solution for this would be to put the database on a separate server which you can access from both your partitions - and consolidate on one SQL Server version (preferably 2012). The other obvious option would be to install the same version of SQL Server on both partitions.
Everything is stored within database, so no you will not have any issues. Just remember to use not only main application database, but use the same meta-databases (aka System dbs).
In fact it works this way on failover clusters.
EDIT:
Haven't noticed you are going to run 2 different db systems. I would recommend you to use exactly the same versions of SQL server.
I am currently running SQL Server 2005 Standard Edition on a Windows 2003 server machine.
I have gone to the properties of the server and confirmed that the Login Auditing is set to both failed and successful logins. For some reason though there is nothing in the logins for fails or successes in the SQL Server logs when I know there have been logins for both.
I have searched out the reason for this and have not been able to come up with anything helpful, so I am hoping that someone here could give me a little direction. This is working on my other SQL Servers, so I know where to look for the results, but there are none there.
After speaking with Microsoft about the issue and doing much research, it was determined that this was an issue with the particular version of SQL (SQL Server 2005 Service Pack 2 9.00.3042) running on that particular version of the windows release. We reinstalled SQL, and then did all the updates and patches to both windows and SQL and this seems to have resolved the issue. The SQL logs are now tracking both success and failed logins.
I am using SQL Server Management Studio 2005 Express to connect to one of my servers. How do I check the existing jobs in the server I am connected to and modify them?
I am logged in as admin and still can't see the required. I can see the jobs in SQL Server 2000 but not in 2005.
Any suggestion would be helpful. Thanks
May be this can be helpful for you
http://sql-articles.com/blogs/script-to-find-sql-job-activity-details/
We have a Sql Server 2000 database application that needs to update our applications Sql Server 2008 database when certain tables are changed. For this, we use a trigger on the Sql 2000 server that fires a stored procedure on our Sql 2008 server. When trying it from SMSS, I get this message:
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
Our application used to use a Sql Server 2005 database, but we upgraded servers this weekend. The linked server objects have the same configuration as on the old server. Here is my DTC configuration. Is there anything else that could go wrong?
dtc configuration http://yourcls.com/dtc-configuration.png
Google came up with this knowledge base article for me. From your screenshot, it looks like you've got DTC configured right (though I'm skimming, definitely double check it). Have you checked your firewall settings?
It turns out the same DTC security configuration window on our Sql 2000 server did not have any network DTC access enabled. This apparently worked just fine with our old server, but when we upgraded to Server 2008 and Sql Server 2008, this needed to be enabled on BOTH servers. It is a mystery.