October 4, 2011 at 2:22 pm
you still need the -S option
---------------------------------------------------------------------
October 4, 2011 at 2:27 pm
Oh, and that command won't fix this error anyway. That SQL command you have is specific to the error that the page talks about, which is not the problem you have.
I pointed you at that for a way to start SQL in the middle of the upgrade. You don't need to change the sa login name, you need to fix the database owner as I said earlier
Fix the database ownership (set the db owner to sa) then repair the installation or reinstall the patch.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 4, 2011 at 2:32 pm
Yes but in order to fix the DB owner I need to utilize sqlcmd.
sqlcmd -E -S .\myinstance -A
This part is failing. With this failing I can not modify the owner. Am I doing something wrong? If so, Please send me an example? THANK YOU!
October 4, 2011 at 2:36 pm
SQLSeTTeR (10/4/2011)
This part is failing.
Define 'failing'. I can't see your screen.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 4, 2011 at 2:38 pm
C:\Program Files\Microsoft SQL Server\100\Tools\Binn>sqlcmd -E -S .\injest -A
HResult 0x274D, Level 16, State 1
TCP Provider: No connection could be made because the target machine actively refused it.
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or instance-specific erro
r has occurred while establishing a connection to SQL Server. Server is not found or not accessible.
Check if instance name is correct and if SQL Server is configured to allow remote connections. For
more information see SQL Server Books Online..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.
October 4, 2011 at 2:50 pm
Fix the database ownership (set the db owner to sa) then repair the installation or reinstall the patch.
How can I fix the DB ownership if I cannot log in to modify it?
October 4, 2011 at 3:15 pm
Gail - Just to be clear. This is what I'm trying.
C:\Program Files\Microsoft SQL Server\100\Tools\Binn>sqlcmd -E -S .\injest -A -Q"alter login [sys-admin] with name = sa"
October 4, 2011 at 4:26 pm
Does this mean it's making a connection?
C:\Program Files\Microsoft SQL Server\100\Tools\Binn>sqlcmd -E -S .\injest -A -Q"alter login [sys-ad
min] with name = sa"
Msg 15151, Level 16, State 1, Server ICMDBORSTG\INJEST, Line 1
Cannot alter the login 'sys-admin', because it does not exist or you do not have permission.
October 4, 2011 at 4:41 pm
Why, why, why are you trying to alter a login? Your problem is not that the SA account has been renamed. The command you need to run is one to change the ownership of a database. The code in the article was solely and only for the problem covered by the article, which you do not have.
Yes, it's making a connection.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 4, 2011 at 4:50 pm
I apologize for my ignorance. Can you please send me an example on how to change ownership of the master DB in sqlcmd mode? Thank you soo much.
October 4, 2011 at 4:54 pm
First you have to identify which DB it is (it's highly unlikely to be master). A query of sys.databases will do that. Changing the ownership of a DB is not something I know offhand how to do so...
http://www.google.com/search?q=change+owner+of+a+SQL+database+site%3Amsdn.microsoft.com
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 4, 2011 at 5:29 pm
Thank you very much. I identified the DB which had ownership and changed to sa. I am now able to login. Thank you for all your help.
Viewing 12 posts - 16 through 26 (of 26 total)
You must be logged in to reply to this topic. Login to reply