To perform a full disk cleanup on Windows Server 2016
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
The SQL Server engineering (TIGER) team announcement a preview for a SSMS SQL Server Diagnostics extension.
My writeup on this is at http://smooth1.co.uk/sqlserver2017/SSMS_SSD.html
I have been playing with the new SQL Server on Linux command line tools
Very nice that sql-scripter has an option to limit output to a given SQL Server Version and even better Edition although did find an issue with this option and will be providing feedback to Microsoft.
Here are the slides for my recent talks on SQL Server on Linux – SQL Server 2017 goes cross platform!
If have a SQL Server database and change the Recovery Model from Full to Bulk Logged whilst a transaction is open what happens?
If the ongoing transaction which was started under Recovery Model Full does an operation which can be minimally logged what happens?
Does the operation become minimally logged which then means the VLF is tagged as a minimally logged logfile which then does not allow certain operations e.g. restores from the next log backup with STOPAT.
We test with STOPAT and also use fn_dump_dblog to see exactly what ends up in the log backup and how we can identify minimally logged operations in a log backup file.
SQL Server 2016 – Database Scoped Configuration Parameters and Always On Availability Group failovers.Posted: May 10, 2017
In SQL Server 2016 we have database scoped parameters.
With an AlwaysOn Availability Groups we can have different database scoped parameter values on the primary compare to the secondaries.
How does this work with an Always On Availability Group failover ?
To check for Instant File Initialization Permissions:
- Go to https://gallery.technet.microsoft.com/scriptcenter/Grant-Revoke-Query-user-26e259b0
- Download UserRights.ps1
- Add privilege SeDelegateSessionUserImpersonatePrivilege to the list within the script
- Download http://smooth1.co.uk/powershell/CheckSQLServerUserRights.ps1
NOTE: This script needs to be locally on the machine where you are checking for permissions.
The script assumes the SQL Servers are running under a server where the DisplayName starts with “SQL Server (“, please adapt for your own needs.