Yes the source instance is a Standard Edition as well and I initially tried to restore the database on the very same instance as the source but it failed. Also...

• This reply was modified 4 years, 10 months ago by  pooyan_pdm.

yes I posted it also on Azure SQL forums to make sure it's not missed, as the database/VM is hosted on Azure and the root cause could be very well...

In order to have AG you would need to have WSFC installed on the windows level but you don't necessary need to instal SQL Sever as a clustered instance(although...

Using Distributed Availability Groups could also be an option if your nodes are supposed to be in different countries. That would give you more scalability in future (not being limited...

there is difference between "deprecated" and "discontinued". Replication is still supported and not yet "discontinued" as there's no true replacement for it yet,but MS has not been adding anything to...

This is a gray area. Replication is deprecated and there's no true replacement for it at this time.

Not using Replication in future deployments is based on some of the...

it depends if you may greatly benefit from any of the SQL 2016 new features or improvements. I'm planning to upgrade from SQL Server 2014 to 2016 to be able...

Replication is a deprecated feature and Microsoft is not adding any thing new to it, MS recommendation is to use Always on Availability groups moving forward. The problem is Availability...

No. With(TABLOCK) specifies the granularity of the lock (Key,Page,Object) and not the lock mode(shared,exclusive,...) . if you update the table with using WITH(TABLOCK) hint SQL would put "X" lock on...

In general your right, but with our case none of those 3 was the case. Due to massive number of transactions , log file was most of the times hammered...

I said in rare situations this could be an option . The environment I'm dealing with handles more than 35000 transactions /sec and even though we're using memory flash cards...

well, in some cases it could have some performance impact depending on the workload, disk subsystem,...assuming you've also set the log backup jobs on your databases, but this doesn't...

The final destination of the dirty pages is the data files but they should be pushed to the log file before or at the same time they are being pushed...

I agree with you on that , cause other wise there could be a big hit on a log file every time a long running transaction get's committed. the reason...

It takes almost 6 min for sql server to look into the plan catch on our production. What kind of overhead does this search have? I guess it should put...