i probably should have tried that first, but given that is what got me into the mess I wasn't sure it would make any difference :)
Stuart Watret Offshore - IT Ltd ________________________________ From: [email protected] <[email protected]> on behalf of [email protected] <[email protected]> Sent: 18 November 2013 15:39 To: [email protected] Subject: [mssms] RE: help !! - sql sid's I'm late to the party, but I've resolved issues on a DB (owner was a SID that no longer existed.. Curse employee's that don't use service accounts when setting up production stuff.) I just detached the database, and reattached it. Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 www.us.sogeti.com<http://www.us.sogeti.com/> From: [email protected] [mailto:[email protected]] On Behalf Of Stuart Watret Sent: Monday, November 18, 2013 10:32 AM To: [email protected] Subject: [mssms] RE: help !! - sql sid's I'm celebrating with chocolate. So I was bashing away like a karate student wondering why I couldnt get me as the owner; stumbled across a blog that reveresed the proposition, ie made sa the owner again using alter authorization. This worked straight away; I have done three times my sql quota for the year, lost weight and got a headache. The next time someone says "just move the log files to another volume"; I'll ignore them. KB issue for post moved db's (don't put the db in single user mode, try it first) kB2709082 Code for resetting the owner USE dbname ALTER AUTHORIZATION ON DATABASE::dbname TO [sa] Stuart Watret Offshore - IT Ltd ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Stuart Watret <[email protected]<mailto:[email protected]>> Sent: 18 November 2013 15:22 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: help !! - sql sid's hooray........ well done me. Stuart Watret Offshore - IT Ltd ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Stuart Watret <[email protected]<mailto:[email protected]>> Sent: 18 November 2013 15:07 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: help !! - sql sid's ok so I think the master db thinks the owner is me, and the actual db thinks it's sa......... how to resolve? ..honestly if you leave this thread long enough I'll fix it myself :) Stuart Watret Offshore - IT Ltd ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Stuart Watret <[email protected]<mailto:[email protected]>> Sent: 18 November 2013 14:40 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: help !! - sql sid's found a bit more tsql and that shows a different sid between the actual db and what the master thinks it should be, but ......how do we translate that to accounts? Stuart Watret Offshore - IT Ltd ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Stuart Watret <[email protected]<mailto:[email protected]>> Sent: 18 November 2013 14:32 To: [email protected]<mailto:[email protected]> Subject: [mssms] help !! - sql sid's Moved the sccm log file this weekend using the detach/attach method. Hit a snag with the "Trustworthy" issue; resolved that. System up and consoles connecting, but I can't import any new devices using the name/mac screen. Error states, "could not get next available key"......... the db owner sid recorded in the master db differs from the db owner sid recorded in "mt sccm db". Correct this using Alter authorization, blah blah. The issue I have is I'm not sure what to compare to find the difference; and as luck would have it, large migration tonight and need to add some devices. ANy thoughts? Stuart Watret Offshore - IT Ltd
<<inline: image001.jpg>>
