One of customers changed the value returned from @@SERVERNAME. SQL Server works no problem, however an unexpected behavior appeared. Changing the value for @@SERVERNAME, caused
sys.foreign_keys does not have matching row in sys.indexes
Running DBCC CHECKDB you are getting following error message: Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=194099732,key_index_id=7) of row (object_id=2040565179) in sys.foreign_keys does not have
Index Creation Date
Often when troubleshooting performance related issues, it is beneficial to know when new indexes were introduced. However currently there is no easy way to keep
SQL Server 2012 NUMA Node Imbalance–Conclusion
Final post in the series, I hope to summarize my findings for everyone. Thanks for all the comments, feedback and comments I have received to-date
SQL Server 2012 NUMA Node Imbalance – Cont’d
Yesterday, I had posted an issue I been troubleshooting with memory allocation. That was causing CPU to pin, you can read more about the issue
SQL Server 2012 NUMA Node Imbalance
One of my client has been fighting a very strange problem and there is not much literature on the topic, NUMA Node Imbalance. Server Configuration
SQL Canada (SQLCAN) 