If you are facing any of the following issues and have not installed any of the cumulative updates, you should indeed update to SQL Server 2012 SP2. On my personal development server, I have upgraded this SP2 and after a week’s testing, I am planning to roll it out to my production server.
I am very excited about the bug fix of Poor Performance when using table variables, as I had just talked about during my last presentation in India.
- Can’t connect to the server when you run a cube creation MDX query in SSAS 2012
- Image is not displayed correctly in the webpage when you use DrillThrough action on an SSRS 2012 report
- Text truncated when you use HPB renderer to view a report in SSRS 2012
- SQL Server crashes when the log file of tempdb database is full in SQL Server 2012
- SSRS 2012 fails with IsolatedStorageException when subscriptions exported to Excel worksheets are larger than 10 MB
- SSRS 2012 cannot export a report that is larger than 10 MB to Excel format
- Rollback causes database to go to suspect mode in SQL Server 2012
- Poor performance when you run a query against a table in an RCSI-enabled database in SQL Server 2012
- New DMF sys.dm_fts_index_keywords_position_by_document in SQL Server 2012 SP2
- New log files are not created when you restart the Reporting Services Windows Service in SSRS 2012 on January 1
- No error message when log backup failed in SQL Server 2012
- Visual Studio 2012 crashes because of access violation when the data source binding is completed in Report Viewer 2012 UI in local mode
- File Share subscription doesn’t populate the description column in SSRS 2012
- The “Name” drop-down list is empty when an SSRS 2012 report is specified
- Event ID 22 or error 0xC1000016 will be logged when you use Discover command in SSAS 2012
- Performance issues when you use SSISDB as your deployment store in SQL Server 2012
- SSAS 2012 logging feature improvement in SQL Server 2012 Service Pack 2
- Poor performance when you use table variables in SQL Server 2012
- Access violation occurs when you run CHECKTABLE or CHECKDB against a table that has persisted computed columns in SQL Server 2008 R2 or SQL Server 2012
You can download SQL SQL Server 2012 from this download link.
Reference: Pinal Dave (https://blog.sqlauthority.com)