SQL Server Identity Values Check on GitHub
Last year I blogged about a script that Karen López (blog | @datachick) and I wrote together to help you determine if you were running out of identity values.
Last year I blogged about a script that Karen López (blog | @datachick) and I wrote together to help you determine if you were running out of identity values.
When it comes to monitoring data, the are only five possible resource bottlenecks (disk, memory, cpu, network, locking/blocking).
When I hear stories about folks that tried to migrate to Microsoft Azure SQL Database with a brute-force-single-click and failed, I ask several follow up questions. I have found a common pattern in the answers: lack of strategy.
Nobody likes surprises when it comes to upgrading or migrating SQL Server instances. Trace flags get set and forgotten. I’m hoping that this post will help people to remember.
The same holds true for when you restore the master database in SQL Server 2016.
If you still don’t believe that SQL Server 2016 is full of unicorns and rainbows then I would encourage you to try it for yourself.