[SQL 2012] Accelerator products such as Fusion IO |
- Accelerator products such as Fusion IO
- Failover Clustering and AlwaysOn Availability Groups
- Explaining log growth for Simple recovery database
| Accelerator products such as Fusion IO Posted: 10 Jun 2013 02:33 AM PDT Can anyone share their experiences with accelerator products such as Fusion IO?I'm interested to know how easy they are to implement and what benefits / issues people have seen in practice.I presume that even for smaller databases that can mainly be cached, there would still be a benefit through increasing the speed the log can be committed to 'disk'.Any comments would be greatly appreciated.Thanks in anticipationTim |
| Failover Clustering and AlwaysOn Availability Groups Posted: 10 Jun 2013 02:51 AM PDT Does this opening gambit from BOL make sense?1/ AlwaysOn Availability Groups, the high availability and disaster recovery solution introduced in SQL Server 2012, [b]requires Windows Server Failover Clustering (WSFC)[/b]. 2/ Also, [b]though AlwaysOn Availability Groups is not dependent upon SQL Server Failover Clustering[/b], you can use a failover clustering instance (FCI) to host an availability replica for an availability group. |
| Explaining log growth for Simple recovery database Posted: 09 Jun 2013 08:08 PM PDT I thought I understood log growth, but a bit confused why the following is happening.We use SQL Monitor and Ola's maintenance scripts on our 2012 instance. These are set to rebuild indexes when 30% fragmentation occurs. Over the weekend the SQL Monitor database, set to Simple recovery, experienced the transaction log grow from 3 GB to 35 GB and it filled up the disk. This was due to the rebuild index operation from the maintenance scripts which rebuilt just 13 indexes before the disk became full.Looking at these indexes, their total storage size is just over 1GB. I thought when a rebuild happens then the log would only grow to the size of the index as that is all that would need to be rolled back, so why did the log grow to 35 GB? Any why, on a simple recovery databases did the log not get reused, after the first few rebuild commands completed?Any pointers would be good to understand this a bit better and to narrow down the reason.. Thanks. |
| You are subscribed to email updates from SQLServerCentral / SQL Server 2012 / SQL 2012 - General To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google Inc., 20 West Kinzie, Chicago IL USA 60610 | |
No comments:
Post a Comment