Question We have a 3TB OLTP database running Siemens Opcenter MES software at one of our manufacturing plants in China. This is setup in an Always-On Availability group with one secondary node. As this is a manufacturing plant, we are only provided 11 1/2 …
Question We have a few Basic Availability groups in production and I've been reading about the limitations of them. I'm concerned about the following limitations:
No backups on secondary replica.
No integrity checks on secondary replicas.
Suppose that we …
Caterpillars transform into beautiful butterflies to realize their full self, much in the same way CONVERT() changes binary into beautiful hexadecimal strings. Since I started at Stack Overflow, I’ve had the chance to see some of the interesting challenges …
Question For SQL Server Enterprise's Always On availability groups in Synchronous Commit mode, is there some amount of latency that can't be exceeded? For example, can it work between very distant data centers, such as between the US and Europe?
In yesterday’s post, I showed how to configure an availability group (AG) to use the RegisterAllProvidersIP=0 when you can’t get clients to connect using the MultiSubnetFailover=true connection string attribute.
I mentioned that you have to make some …
As a DBA, we have the opportunity & responsibility to build highly available database platforms for use by applications & users. Even if you are a DBA at a small company supporting databases for only internal applications, we are usually still responsible for …
Assume you have configured a transactional replication publisher, which is part of an availability group (AG). Now, you have an asynchronous secondary AG (or mirroring) replica that is offline. Perhaps this is a DR node, and you are doing patching or other …
This guy doesn't have Elvis's password and is still able to impersonate him. As a DBA or SQL Developer, you've surely encountered a scenario where something worked for you, but not for another user. DBAs usually are part of the sysadmin role, or have a …
Question We are a small business using a single SQL Server 2014 instance as our main data platform.
We now need to set up a second instance (2017) to hold additional data - this is to be standalone, ie not replicated or actively linked to the main server.
I 💜 Replication Starting with SQL Server 2017 CU6 and SQL Server 2016 SP2-CU3, you can now configure your distribution database as part of an Availability Group (AG). Up until now, your distribution database could only be part of a standalone instance, or …