Skip to main content
deleted 152 characters in body
Source Link
Luke
  • 121
  • 3

When we set up web servers in AWS, we have a load balancer which allows highly scalable performance improvements per instance provided.

I would like something similar for MS Sql server. I have been informed that Transactional Replication would provide the read performance improvements I am seeking while also providing multi-instance resilience for uptime. Write performance can also scale if using Peer-to-Peer mode, but more complicated.

Is it possible to set this up in AWS without using an Active Directory? We just have random instances on there, not in any Active Directory.

How does Transactional Replication comparerelate to Availability Groups? Does Availability Groups use Transactional Replication under the Always On suite of toolshood or are they separate features? Can I use Transactional Replication without Availability Groups?

AGs use WSFC which usually requires an AD network. We just use AWS with no AD, and why wouldso how do people consider using Always On, if Transactional Replication seems toAWS normally do ideal read load scaling/load balancing?

is there a mode of Transactional Replication (eg Immediate Update mode) that prevents two subsequent queries have concurrency conflicts? or Does it provide a FIFO type model over all subscribers to prevent concurrency conflicts on an AWS network without worrying about setting up AD?

When we set up web servers in AWS, we have a load balancer which allows highly scalable performance improvements per instance provided.

I would like something similar for MS Sql server. I have been informed that Transactional Replication would provide the read performance improvements I am seeking while also providing multi-instance resilience for uptime. Write performance can also scale if using Peer-to-Peer mode, but more complicated.

Is it possible to set this up in AWS without using an Active Directory? We just have random instances on there, not in any Active Directory.

How does Transactional Replication compare to the Always On suite of tools, and why would people consider using Always On, if Transactional Replication seems to do ideal read load scaling/load balancing?

is there a mode of Transactional Replication (eg Immediate Update mode) that prevents two subsequent queries have concurrency conflicts? or Does it provide a FIFO type model over all subscribers to prevent concurrency conflicts?

When we set up web servers in AWS, we have a load balancer which allows highly scalable performance improvements per instance provided.

I would like something similar for MS Sql server. I have been informed that Transactional Replication would provide the read performance improvements I am seeking while also providing multi-instance resilience for uptime.

How does Transactional Replication relate to Availability Groups? Does Availability Groups use Transactional Replication under the hood or are they separate features? Can I use Transactional Replication without Availability Groups?

AGs use WSFC which usually requires an AD network. We just use AWS with no AD, so how do people using AWS normally do read load balancing on an AWS network without worrying about setting up AD?

added 232 characters in body
Source Link
Luke
  • 121
  • 3

When we set up web servers in AWS, we have a load balancer which allows highly scalable performance improvements per instance provided.

I would like something similar for MS Sql server. I have been informed that Transactional Replication would provide the read performance improvements I am seeking while also providing multi-instance resilience for uptime. Write performance can also scale if using Peer-to-Peer mode, but more complicated.

Is it possible to set this up in AWS without using an Active Directory? We just have random instances on there, not in any Active Directory.

How does Transactional Replication compare to the Always On suite of tools, and why would people consider using Always On, if Transactional Replication seems to do ideal read load scaling/load balancing?

is there a mode of Transactional Replication (eg Immediate Update mode) that prevents two subsequent queries have concurrency conflicts? or Does it provide a FIFO type model over all subscribers to prevent concurrency conflicts?

When we set up web servers in AWS, we have a load balancer which allows highly scalable performance improvements per instance provided.

I would like something similar for MS Sql server. I have been informed that Transactional Replication would provide the read performance improvements I am seeking while also providing multi-instance resilience for uptime. Write performance can also scale if using Peer-to-Peer mode, but more complicated.

Is it possible to set this up in AWS without using an Active Directory? We just have random instances on there, not in any Active Directory.

How does Transactional Replication compare to the Always On suite of tools, and why would people consider using Always On, if Transactional Replication seems to do ideal read load scaling/load balancing?

When we set up web servers in AWS, we have a load balancer which allows highly scalable performance improvements per instance provided.

I would like something similar for MS Sql server. I have been informed that Transactional Replication would provide the read performance improvements I am seeking while also providing multi-instance resilience for uptime. Write performance can also scale if using Peer-to-Peer mode, but more complicated.

Is it possible to set this up in AWS without using an Active Directory? We just have random instances on there, not in any Active Directory.

How does Transactional Replication compare to the Always On suite of tools, and why would people consider using Always On, if Transactional Replication seems to do ideal read load scaling/load balancing?

is there a mode of Transactional Replication (eg Immediate Update mode) that prevents two subsequent queries have concurrency conflicts? or Does it provide a FIFO type model over all subscribers to prevent concurrency conflicts?

Source Link
Luke
  • 121
  • 3

Transactional Replication vs AO for MS Sql Server

When we set up web servers in AWS, we have a load balancer which allows highly scalable performance improvements per instance provided.

I would like something similar for MS Sql server. I have been informed that Transactional Replication would provide the read performance improvements I am seeking while also providing multi-instance resilience for uptime. Write performance can also scale if using Peer-to-Peer mode, but more complicated.

Is it possible to set this up in AWS without using an Active Directory? We just have random instances on there, not in any Active Directory.

How does Transactional Replication compare to the Always On suite of tools, and why would people consider using Always On, if Transactional Replication seems to do ideal read load scaling/load balancing?