Cannot resolve the collation conflict between “xxx” and “xxx” in the equal to operation

Issue – Customer was getting below error when he was running any query. Msg 468, Level 16, State 9, Line 36 Cannot resolve the collation conflict between “SQL_Latin1_General_CP1_CI_AS” and “SQL_Latin1_General_CP1_CS_AS” in the equal to operation. Back ground – Table was part of replication and when he was running query on subscribe he was getting collation conflict… Read More Cannot resolve the collation conflict between “xxx” and “xxx” in the equal to operation

Login failed for user ‘xxx’. Reason: Server is in single user mode. Only one administrator can connect at this time.

Issue – Login failed for user ‘xxx’. Reason: Server is in single user mode. Only one administrator can connect at this time. Cause – Ensure SQL Server is not running in Single user mode by checking start-up parameter. if you see -m; it mean your SQL is running with single user mode. -m : Starts an… Read More Login failed for user ‘xxx’. Reason: Server is in single user mode. Only one administrator can connect at this time.

The transaction log for database ‘XXX’ is full due to ‘LOG_BACKUP’

Yesterday, one of my client send me email stating she is not able to run any query against database. she was getting below error message – The transaction log for database ‘xxx’ is full due to ‘LOG_BACKUP’ From error message it’s look like transaction log full issue hence I looked for db property and found… Read More The transaction log for database ‘XXX’ is full due to ‘LOG_BACKUP’

Server TCP provider failed to listen on [ ‘any’ 1433]. Tcp port is already in use.

Issue – Today I faced very weird issue; on multi instance SQL Server machine, couple of SQL Services was not starting after Server reboot ( In my case it was SQL 2014 and SQL 2016 ) and every time I was trying to restart my SQL Services, I was getting below error message –  … Read More Server TCP provider failed to listen on [ ‘any’ 1433]. Tcp port is already in use.

The server principal “XYZ\USER” is not able to access the database “YourDBName” under the current security context

My Development team contacted me and said they are not able to access database  “The server principal “XYZ\USER” is not able to access the database “YourDBName” under the current security context” when I looked into server server I found – Login was there and access was granted. When I looked into database I found user… Read More The server principal “XYZ\USER” is not able to access the database “YourDBName” under the current security context

Replication – Snapshot is not getting generated

Replication issues and resolutions Today I have encountered very strange issue – Scenario – Snapshot is not getting generated for newly added articles or Error when setting up Transactional Replication via SQL scripts. Msg  14100, Level 16, State 1, Procedure sp_MSrepl_addsubscription, Line 533 Specify all articles when subscribing to a publication using concurrent snapshot processing. Step performed to… Read More Replication – Snapshot is not getting generated

Configuring deadlock and Storing Deadlock events in a table

Configuring deadlock and Storing Deadlock events in a table SQL Server 2012 and above. Verification – Ensure Extended Event “system_health” is running. SSMS, checking Management -> Extended Events -> Sessions. These should be green arrow which indicate its running.   The system_health session writes to two targets, both an event file and the ring buffer:  … Read More Configuring deadlock and Storing Deadlock events in a table