I have two SQL Server databases located at different locations. And I have to synchronize data between these two databases.
You didn't specified how..you can use below technologies
If both computers are in Same domain:
Always on
Log shipping
Mirroring
Replication
If both computers are not in Same domain:
Logshipping
Mirroring
Replication
I you do some research on above HA technologies, they do things differently and can serve your purpose
Related
If there is a need to set up Azure site recovery for Azure VMs (which has SQL Server installed with Always On availability group installed), then how we can do it?
For a normal Azure VM, I can set up ASR. But if we follow same steps for VMs which have SQL Server and AG group configured, then on DR server will it work same as Primary VM?
Please share any link or blog which help to set it up.
Happy to inform you that Azure provides the complete Disaster Recovery solution for your SQL Server VMs :)
Always On availability groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together. Each set of availability database is hosted by an availability replica. Two types of availability replicas exist: a single primary replica. which hosts the primary databases, and one to eight secondary replicas, each of which hosts a set of secondary databases and serves as a potential failover targets for the availability group.
The primary replica makes the primary databases available for read-write connections from clients. The primary replica sends transaction log records of each primary database to every secondary database.
You can explore more Business Continuity and Disaster Recover (BCDR) technologies with Site Recovery options here.
To create an Always On availability group for SQL Server on Azure Virtual Machines (VMs), please follow Manually configure an availability group (SQL Server on Azure VMs) tutorial.
If I only have one VM in Azure I can get outtages at any time when Azure decides to reboot/reprovision my server. Therefor I have to at least two servers in an availability group to get a stable environment.
This is used by a web app (web roles) and an important aspect is that the databases are used for reading. They will get their data from sql replication from an on-premises database. The replication can be done separately to each database. Additionally using Azure Sql Database is not an option because we have not be able to implement a durable data sync solution (using Microsoft Sync Framework), Sql Database does not support sql replication, and constantly uploading the complete database would be too slow.
How should the database VMs be hosted and accessed to able to use Sql Server VMs?
One alternative is to use AlwaysOn Availability Groups. This however requires Sql Server Enterprise edition and the price is very high considering I need to have at least two servers. In this scenario I at least get one connection point behind which a sql server always should be answering. This is however beyond our reach because of the cost.
One alternative could be to use Traffic manager to round robin the connections. When the database server goes down we have to wait for TTL to expire before the webrole would refresh the ip address so that seems a big problem.
How should one host Sql Server VMs in Azure?
You can use FailoverPartner parameter in the connection string to specify the secondary replica address. You can see more in this article.
we're close to migrating our legacy MS Access app to SQL Server for our internal warehouse management system. Our customers are often asking us for access to the data for e-commerce integration and general reporting. Once the migration is complete I would like to provide open access to the data via web services and odata. However I don't want to host these services as we are on a slow ADSL connection which won't cope with the traffic.
My question is, can I replicate (one-way) to a remote DB hosted by shared-hosting companies such as Hostgator? I see they have shared windows hosting with unlimited MS SQL DBs. Are there any special requirements on the hosted-side? For instance do I need to explicitly set-up replication on hosting db or is it managed on the client-side?
If this is possible then I might be able to run all our web services and reporting apps on the host's servers, and only the replicated data need travel over WAN. What sort of control is there over replication? Such as bandwidth throttling, replication periods etc? For instance when & how often does replication take place?
I'm new to SQL Server in general and some of the topics are a little overwhelming.
Thanks for your help.
You could try setting up transactional replication with a push subscription with the distributor on your side. The relevant bit is how the distribution agent connects to the subscriber. distrib.exe supports both trusted and SQL authentication, so you should be good to go either way.
I´m running 2 servers on Rackspace. I have set up a load balancer that balances the traffic between these two servers.
Each of these servers runs a Glassfish v3 server with a Java EE application on it, that offers a web interface to write some data into server database. The problem is that I need to have the same data on each database (server 1 database and server 2 database).
A resolution to this problem is mirroring of databases.
I would like to ask if there is some automated system to mirror these databases inside the rackspace?
Furthermore I ve found Xendros database cloud that is able to work with Rackspace Cloud. Is it possible to mirror these databases inside the Xeround?
Or are there any better solutions ?
Thanks for answers :)
With Xeround you do not need to mirror your database, you create a single database instance and direct your application servers to work with this instance.
For more information you are welcomed to visit our web site http://www.xeround.com
I was readin this month edition of SQL Server Magazine and in an article about securing Sql Server environment , the author mentioned that developer should try to have the website and the databases run in separate servers for security. I have a shared hosting account and was wondering if it makes sense to buy a second account to move all databases there. Or does it only make sense when using dedicated servers? How would it affect performances on my website?
I use asp.net and have a hosting account with DisountAsp
That article probably doesn't apply to your situation. Running the database on a separate server is a measure to protect against root compromise of the web server hosting machine. I a shared hosting environment the same situation would result in compromising all accounts on that machine anyway. Depending on the particular settings of your hosting, your account database may alreayd be on a separate server.
Besides, with a shared hosting account is very unlikely you'll even be able to query a database from another account.
If you buy a second server, what will it be, a VPS? I imagine you will get more CPU cycles on a VPS with a dedicated database server than a dedicated machine with multiple databases, but who really knows.
Still, your host isn't running websites on their shared database servers, so what's the difference, security wise?
Performance would me my number one driving factor. I mean if someone compromises your web server, unless your connection strings are encrypted, they've got what they need to connect to the DBs.