I have active Server A and standby Server B and B is replicating data from Server A.
I'm using SQL Server 2005 enterprise edition.
When Server A is failed, the application server is programmed to route traffic to Server B.
Then Server B becomes active server and Server A becomes standby server.
To turn Server A to be active server, the data modification when Server A failed in Server B needs to replicate back to Server A.
I don't want to over load in active server.
I'm thinking to use pull transactional replication method for replication.
But I want to know what is the best method for doing above operations because this is the first time doing this operation for me.
Have you considered utilizing database mirroring instead?
Of course... you'll end up needing a witness server, but unlike replication, there is less work for everyone. No scripts are needed to make sure that the previously failed server has the most updated data.
Related
I have 2 Linked servers (B and C) that simply stopped working from my main server (A), and returns me a "Login Timeout Expired" error when I try to test them, but, the server A has access to B and C servers, I can login into the B and C via SSMS in the server A, with the same credentials that the linked server use, but I cannot create the linked server, server A is SQL Server 2012 Standard, servers B and C are SQL Server 2008 R2 Standard.
I used another, smaller server (D), which is also SQL Server 2012 Standard, to test the linked servers to B and C and they worked, so I guess the problem is within A.
In A, I have another linked server to a SQL Server 2008 R2, and it works, just this two.
I tried opening all doors in the firewall, making the linked server by server name and by IP address, creating a new SQL User to make the linked server, none of that worked, my next step is to reboot the server, but I can do that only by nighttime, since A is a production server.
Anyone can help me on this please?
I have SQL Server 2012 installed on our Office.
and its storage is going to be full
what I want is that How can I connect my SQL Server to another Server to store its database and files
there.
means I want to have a connection to another Server for just storing my database files.
If I create new database it should also be created in the new server.
the server will not be running any databases it just will be a storage place.
How can I create a connection from my SQL Server to an Storage Server.
what I mean is the second server will be just as a secondary storage for my SQL Server
if my current server gets full than it should automatically stores its data to another server.
please proved with a detailed answer because it is first time i faced this issue.
I've gotta admit that I'm a Microsoft .NET developer, and I'm not an expert in SQL Server.
I have developed a Windows app, with data stored in my local SQL Server (Express version). I recently purchase a shared hosting service, including a SQL Server. I thought about backing up my local data to remote server: about 5-6 tables from my local SQL Server to remote server, and 1-2 tables from remote to local
What's the best way to do this? DB size is limited to about 5-10MB. The structure of 2 DBs are different, synced tables have same structures. Is there an automatic script I can run from SQL Server Express to do this task every 15 minutes or so?
For initial publishing I’d just go with restoring a backup in the hosting environment. For further synchronization you can try some of the 3rd party tools such as ApexSQL Data Diff or SQL Data Compare or basically any other tool in this category…
I have a powercenter 9.1 installation on windows server 2008 R2.
The repository is on the same box, hosted on sql server 2012. I have configured a new user (with sql server authentication) and have the repo db owned by that user. (it has the owner role)
The core problem : I am not able to run a simple test workflow on this setup.
Here's what I have been trying
The windows firewall has been taken down now for about an hour or so.
The repository service and integration service are running in trace/debug mode respectively.
The integration service log complains that it cant find a certain session for a certain workflow in certain folder (with ids for all of them).
When I log into sql server mgmt console, and try to query the repository tables for those exact items (since i have the ids from logs), all the data is present...
I fail to understand what is that I am messing up...
Disclaimer - my knowledge of sql server is really low.. may be 1 or 2 on scale of 10, since I have been living on the other side of fence (with oracle) for all of my career...
Did you try keeping the sql server login/user name and the associated default schema name as same?
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.