I've got a server with a number of databases in an availability group. This has been setup prior to me joining the company and I'm not that familiar with SQL Server. A question has been asked if we can failover a single database or all in the availability group. How do I check if this is possible, or is there any SQL I can run to get some configuration details?
All of the databases in an Availability Group failover at the same time. This is by design as the AG is the effective container.
If you would like to do a manual failover then refer to the instructions here
Related
I have multiple Azure SQL Databases and when I connect to them using SQL Server Management Studio, they all appear to be running on the same VM -- meaning, when I connect to the instance of SQL Server, I see my databases listed in Object Explorer.
With that said, should I assume that the DTU level set through the portal is only a throttling setting? In other words, should I assume that the databases are already running on a pretty powerful instance but based on DTU settings, Azure is throttling up/down allowed requests?
I don't think it would make a lot of sense for Microsoft to move a database to a new instance when the DTU level is increased.
Yes, you are correct, DTU is not a VM total capacity, just a way to cap database performance.
DTU is for individual databases, and can range from a small percentage of VM resources to the entire database taking one single machine. Azure doesn't guarantee all the databases under one server belongs to one physical sql server instance. The databases can potentially spread across multiple sql instances though they belongs to one logical server. For checks like firewall, it appears the instances cross connect to the master database and query the rules.
I have two SQL Server databases with the same version.
there is a Oracle bus service between the two SQL Server database.
I want transaction replication between two database,two database located in different cities.
How do I configure Transactional Replication between the two Database?
You can use CDC, but if you want to replicate an entire SQL database real-time then either use mirroring (which will become phased out) or Always on Availability Groups (recommended by MS going forward). An ESB is for message-oriented communication, not for replication.
We have a BizTalk setup, its databases are setup on a failover cluster to achieve the HA (High Availability). Client have an application database that also needs to achieve the HA, usually I'd suggest to put on the same instance with BizTalk database but client DBA insists to use the AlwaysOn feature.
BizTalk Server does not support the alwayson due to some DTC complications, having said that, is it possible to enable the AlwaysOn feature on the same SQL Server to satisfy the customer needs while not disturbing the DTC requirement by BizTalk? Or it simply has to be two sets of SQL Server deployment?
Since Always On feature does not support MSDTC, BizTalk does not support Always On since it relies on MSDTC. See link msdn link (at the bottom of page). Your other database for which you need always on, put it on a separate SQL instance. It may share the same cluster node as BizTalk server SQL instance.
I need a means to create a SQL Server Express partial replica of a SQL Server 2014 server database and then synchronize the two, triggered by a C# command. Eventually, there could be as many as a hundred partial replicas on various clients. Anyone know how I can do this and where I should look to learn how to do it? Thanks!
SymmetricDS is a product that will synchronize SQL Server 2014 with SQL Server Express either in a partial sync scenario or full sync scenario. You configure which tables you need to synchronize. It will by default synch in near real time based on your configuration or you can schedule a variety of jobs to meet your needs. To support your C# use case you could look into the JMX and/or REST API's provided as well.
SymmetricDS Open Source
SymmetricDS Professional
In an installation with 2 SQL Server 2008 SP2 Standard servers we use mirror to have failover partner for the databases.
One of the purposes of the databases are to supply reports through SQL Server Reporting Services.
My question is how I set this up to have failover of the reports AND keep cost at a minimum.
I can see one solution where the reporting databases are mirrored as well as the user databases they use. But will the reporting services failover?
Another way could be to install 2 separate instances of reporting services on each database server where the reporting databases are not mirrored and both are running. But then how do I redirect the users browsers from one entry address to a running reporting service?
There's also a witness server running SQL Server 2008 Express. This could be upgraded to standard and run the reporting services (should be able to failover through native client connection), but then the reporting service it self has no failover.
I don't know if I'm missing something here but is it impossible to do this in a good way without using SQL Server Enterprise and a failover cluster solution?
Any ideas, thoughts and links would be appreciated, but be aware that I have read a lot of guides and best practices around the internet and haven't found any that answers this question so please only post relevant links.
Any info I gather from you post, links and my research and testing will of course go back to Stackoverflow for future reference for others as I can't imagine I'm the only one who would like such a solution.
Smint
You will need to mirror all data and then manually repoint the report server when the data moves to the mirrored servers.
Moving interrelated databases with mirroring complicates things. If one goes offline for some reason and failes to the mirror, will all other databases fail as well?
You may want to have a human make these decisions and use a manual failover on the mirroring as well.