I was quite puzzled with a situation that happened recently and i find it interesting to share, well it could help someone in the same or similar situation that have bypassed this issue by using DB Snapshots (run integrity checks againts those same snapshots, among other approaches)… Basically, what started to happen after migration, was
Change NUMA-Node Processor Affinity is an online operation that can be done without causing downtime but I have experienced that it can lead to bring an instance offline if the resource monitor takes long time to free memory and keeps generating Mini-Dumps, at #51 it will bring the instance offline. Started to have Non yielding
When you have a negative spid ( ex: -2) in SQL SERVER, it is related with Microsoft Distributed Transaction Coordinator (MSDTC). You can do it from 2 different ways: Outside SQL SERVER, in component services > DTC > Transactions > rollback the transaction. OR select distinct req_transactionUOW from syslockinfo , ignore the 000000’s kill ‘GUID’ . ( ghost/orphaned transaction
SSMS (SQL SERVER MANAGEMENT STUDIO) slow startup and how to optimize SSMS startup time : To sump up, everytime you open SSMS it will check some certs, so, do the following if you want faster load times : Open IE > TOOLS > OPTIONS > ADVANCED > UNCHECK PUBLISHER CERTIFICATE REVOCATION .
SQL SERVER 2005 Partitioning <- Can read a fully formated .doc in here . Microsoft worked well in the Microsoft SQL Server 2005 (even better in MSSQL Server 2008), bringing a shine to their RDBMS engine and building it to be a real Enterprise Class Product. I’m not going to write about all the new features
Objectivo I. Benefícios e Limitações de Partitioned Clustered INDEX em SQL SERVER 2005. II. Metodologia de Implementação. III. Gestão de Particionamento. Descrição I. Benefícios e Limitações de Partitioned Clustered INDEX em SQL SERVER 2005: + Dados podem ser acedidos através de múltiplas partições em paralelo. Diferentes partições podem ser geridas em separado. Gestão de Histórico