By Adam Bean, on December 12th, 2011
http://www.sqlslayer.com/wp/admin-database/
- Completely rewrote all database maintenance routines!
- Added new object (DeployDatabaseMirroringNotification) to notify via email of any Database Mirroring state changes
By Adam Bean, on October 7th, 2011
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!
By Adam Bean, on July 6th, 2011
http://www.sqlslayer.com/wp/admin-database/
- 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.
By Adam Bean, on May 3rd, 2011
http://www.sqlslayer.com/wp/admin-database/
- 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
By Kathy Toth, on April 26th, 2011
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!
By Adam Bean, on April 18th, 2011
http://www.sqlslayer.com/wp/admin-database/
- Updated BackupDB to support @CopyOnly.
- Updated WhereAmI to support searching jobs (@SearchJobs).
- New Object: DatabaseAttributes_vw.
By Adam Bean, on December 1st, 2010
http://www.sqlslayer.com/wp/admin-database/
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.
- Fixed CheckDB logging issues
- Updated ReadErrorLog to resolve collation/cursor issue
- Removed buildmax of 11.0.0
- Updated objects to 3042 where they were 4053
- Added dbo.RemoveComments_fn
- Added dbo.man
- Added dbo.GetManSection_fn
- Updated both versions of WhereAmI to include @IgnoreComments, performance enhancements and updated header
- Updated Model
By Adam Bean, on November 17th, 2010
http://www.sqlslayer.com/wp/admin-database/
Big update!
- Added ReadErrorLog
- Added sysserver_principals_vw compatibility view
- Added CacheKeyAttributesWide_fn
- Removed PlanCache_vw, logic placed in ExecutionPlanAttributes_vw and ExecutionPlans_vw is an extension of that (including QueryPlans).
- FileIO – added addition columns and output.
- IndexInfo – Added the NONE @ScanType, also changed default @ScanType to LIMITED (the actual system default)
- IndexInfo – Fixed an overflow in the rank calculation
- MissingIndexes – Added Schema name
By Adam Bean, on August 18th, 2010
http://www.sqlslayer.com/wp/admin-database/
- Resolved collation issues with 2000 version of IndexInfo.
- Added new Split_fn for 2005 and later (to support VARCHAR(MAX)).
- Renamed 200x.dbo.Split_fn.sql to 2000.Split_fn.sql.
By Adam Bean, on July 8th, 2010
http://www.sqlslayer.com/wp/admin-database/
- Updated MissingIndexes_vw to include support for ONLINE operations (Enterprise Edition). Also added DROP statements.
Comments