Many of the current projects are increasingly using SQL Server AlwaysOn architecture as a highly available clustering technology for databases.
And most of the current Microsoft products, Citrix XenDesktop, XenApp, PVS, Xenmobile also support this technology, AlwaysOn both mirror and cluster dual advantages, both to achieve a unique host name, IP address access, Instead of having to use shared storage as a cluster, you can save the data as multiple copies, like Mirror, with AlwaysOn also having a multi-read-write architecture that can improve database performance very effectively, with a single AlwaysOn group supporting up to 8 secondary replicas. It can also support the AlwaysOn architecture of different sites, and realize the remote disaster preparedness and database access.
To get to the bottom, let's talk about the full issue of database logs we often encounter with SQL Server, especially the more Citrix XenDesktop Virtual desktop projects deployed, where the database log growth is very fast in the 1000-point scale, and in traditional mirror environments, We did the appropriate pruning using scripting, so let's talk about the simplest method of shrinking in AlwaysOn.
SQL Server logs will automatically free up space when it is backed up, such as a weekly log of 10GB, a weekly backup, and a log on disk that will always remain around 10GB.
Therefore, the effective way to shrink is to do a regular backup of the transaction log for SQL Server, which is done directly in the SQL Server Management tool to make a maintenance backup plan.
In a typical deployment, we have two backup plans, a full backup, a transaction log backup, and a backup that is retained for one months or more, as security requires, to automatically delete the old backup.
This article is from the "Meng Juishu Technology Blog" blog, make sure to keep this source http://superdream.blog.51cto.com/2011872/1856585
SQL Server AlwaysOn Log shrinking