- Now supports SQL Server 2012!

* If you are running on a non SQL 2012 server, you will need to install the following: - Microsoft® System CLR Types for Microsoft® SQL Server® 2012 - Microsoft® SQL Server® 2012 Shared Management Objects

Both of which can be located here: http://www.microsoft.com/download/en/details.aspx?id=29065

- Completely rewrote all database maintenance routines! - Added new object (DeployDatabaseMirroringNotification) to notify via email of any Database Mirroring state changes

- Added @AddStandardPermissions to NativeRestoreDB - Added new object: Foreign Keys & RecursiveTruncate - Added VIEW SERVER STATE permissions to StandardGroupPermissions - Updated WhereAMI to include @IgnoreIdentifiers - Updated Reindex procedure for partitions - Updated BackupDB to cleanup backup logic to check only the most recent backup time - Updated ShowChangedExtents to add @DiffBackupMB to estimated resulting size of a DIFF [...]]]> http://www.sqlslayer.com/wp/admin-database/

- Added @AddStandardPermissions to NativeRestoreDB
- Added new object: Foreign Keys & RecursiveTruncate
- Added VIEW SERVER STATE permissions to StandardGroupPermissions
- Updated WhereAMI to include @IgnoreIdentifiers
- Updated Reindex procedure for partitions
- Updated BackupDB to cleanup backup logic to check only the most recent backup time
- Updated ShowChangedExtents to add @DiffBackupMB to estimated resulting size of a DIFF backup in MB

New major release coming soon with completely rewritten maintenance routines!

- Added TableSizes procedure - Updated ReadErrorLog to support @FindRestarts which will show when SQL was restarted, and how long it was down for. - Man, MoveBetweenFilegroups & who all fixed for case sensitive collations. - ShowPermissions fixed to resolve collation issues. - StandardGroup permissions updated to drop non standard users from standard roles.

- BackupDB procedures updated for model tlog issues and added @SkipRecentRestoreMinutes - Added function JobHistoryDateTime_fn.sql - Added new procedure DeploySQLServerStartupInstructions - Updated maintenance procedures to resolve collation issues - Updated NativeRestoreDB to not drop backup/restore history when dropping a database via KillProcess on restore

wmic partition get BlockSize, StartingOffset, Name, Index

You’ll get something that looks like the following:

BlockSize Index Name StartingOffset 512 0 Disk #1, Partition #0 135266304 512 0 Disk #2, Partition #0 1048576 512 0 Disk #3, Partition #0 1048576 512 0 Disk #4, Partition #0 1048576 512 0 [...]]]> The GPT disk alignment can be checked and verified by using the command below:

wmic partition get BlockSize, StartingOffset, Name, Index

You’ll get something that looks like the following:

BlockSize Index Name StartingOffset
512 0 Disk #1, Partition #0 135266304
512 0 Disk #2, Partition #0 1048576
512 0 Disk #3, Partition #0 1048576
512 0 Disk #4, Partition #0 1048576
512 0 Disk #5, Partition #0 65536
512 0 Disk #6, Partition #0 65536
512 0 Disk #0, Partition #0 1048576

Disk #1 (GPT Disk)
135266304 \ 512 = 264192
264192 \ 2048  =  129

Disk #1 in this example is a basic GPT disk. If you take 135266304\512 you get 264192 which is divisible by 2048, which means that the disk is aligned properly.

This information came directly from a case I had opened up with Microsoft to verify if our GPT disks were properly aligned.

There is limited information out there on how to properly verify a GPT disk for SQL server. I hope this helps!

- Updated BackupDB to support @CopyOnly. - Updated WhereAmI to support searching jobs (@SearchJobs). - New Object: DatabaseAttributes_vw.

We’re on a roll! Finally working towards some inline documentation with the recent addition of the man procedure. Very exciting stuff! We’re getting there, slowly but surely.

Big update!