Collation conflict
by Michal Tinthofer on 07/03/2012I think there is more simple and harmless way. First we need to understand the process of tempdb collation setting.
Read moreTo resolve the issue, first I need to find which login wizard is trying to drop. Since i didn't know, I have used this aproach:
Find job to login owner relationship:
SELECT j.job_id ,j.owner_sid ,j.name , l.name
FROM msdb.dbo.sysjobs AS j LEFT JOIN
sys.server_principals AS l
ON J.Owner_sid = l.sid
Then focus on owners having specific amount (2 in my case) of jobs assinged:
SELECT l.name, COUNT(*)
FROM msdb.dbo.sysjobs AS j LEFT JOIN
sys.server_principals AS l
ON J.Owner_sid = l.sid
GROUP BY l.name
HAVING COunt(*) = 2 --here you may filter the amount of jobs owner should own
When I knew the job owner, it was easy to list just his jobs:
SELECT l.name, COUNT(*)
FROM msdb.dbo.sysjobs AS j LEFT JOIN
sys.server_principals AS l
ON J.Owner_sid = l.sid
GROUP BY l.name
HAVING COunt(*) = 2 --here you may filter the amount of jobs owner should own
Hope it helps.
With regards,
Michal.
Michal Tinthofer is the face of the Woodler company which (as he does), is fully committed to complete support of Microsoft SQL Server products to its customers. He often acts as a database architect, performance tuner, administrator, SQL Server monitoring developer (Woodler SMT) and, last but not least, a trainer of people who are developing their skills in this area. His current "Quest" is to help admins and developers to quickly and accurately identify issues related to their work and SQL Server runtime.
I think there is more simple and harmless way. First we need to understand the process of tempdb collation setting.
Read moreSMT Waits reports – handy overview of what is going on at the server
Read moreYou might have been wondering what all those ANSI settings are and how they can affect you work.
Read more