I did a stupid thing yesterday: I had to detach a database, and forgot it
was the default for that login account (Windows authentication). After it
was detached, I was unable to connect to that server through enterprise
manager afterward with that login.
Once I realized my error, I found a way to reattach the database using query
analyzer and that worked great. Unfortunately, I still can't login with the
Windows admin account. I connected as a different user (SQL Server internal
account) and saw that the default database for the Windows admin account in
question is now blank. !!!
So it seems I'm in a catch-22. Can't login to fix my login. I can't get a
response from our support staff so I'm trying to figure this out myself. I
need to have this access restored asap. How do I recover from this
embarrassing blunder (technically, not emotionally... lol)?
Thanks,
Randall Arnold
> Once I realized my error, I found a way to reattach the database using query analyzer and that
> worked great.
This indicates that you have some login that you can use, possibly with sysadmin privileges. Use
sp_defaultdb to change the default database for the messed up login.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158249818.863918@.xnews001...
>I did a stupid thing yesterday: I had to detach a database, and forgot it was the default for that
>login account (Windows authentication). After it was detached, I was unable to connect to that
>server through enterprise manager afterward with that login.
> Once I realized my error, I found a way to reattach the database using query analyzer and that
> worked great. Unfortunately, I still can't login with the Windows admin account. I connected as
> a different user (SQL Server internal account) and saw that the default database for the Windows
> admin account in question is now blank. !!!
> So it seems I'm in a catch-22. Can't login to fix my login. I can't get a response from our
> support staff so I'm trying to figure this out myself. I need to have this access restored asap.
> How do I recover from this embarrassing blunder (technically, not emotionally... lol)?
> Thanks,
> Randall Arnold
>
|||The problem is, the only login I had with sysadmin privileges is the one I
can no longer use. I tried the same local login I mentioned below, running
sp_defaultdb in query analyzer, and got this error:
Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
Cannot change default database belonging to someone else.
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
> This indicates that you have some login that you can use, possibly with
> sysadmin privileges. Use sp_defaultdb to change the default database for
> the messed up login.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158249818.863918@.xnews001...
>
|||So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes sense it cannot change
default database for somebody else.
If the only sysadmin you have left is the messed up login, use ISQL.EXE, which will allow you in
even though the default database doesn't exist.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158254641.735397@.xnews001...
> The problem is, the only login I had with sysadmin privileges is the one I can no longer use. I
> tried the same local login I mentioned below, running sp_defaultdb in query analyzer, and got this
> error:
> Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
> Cannot change default database belonging to someone else.
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>
|||Thanks.
There are other sysadmin logins, I just don't have access to them. I
finally got ahold of our IT guys who do have such access so hopefully they
can get it resolved for me. Thanks for your advice!
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
> So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes
> sense it cannot change default database for somebody else.
> If the only sysadmin you have left is the messed up login, use ISQL.EXE,
> which will allow you in even though the default database doesn't exist.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158254641.735397@.xnews001...
>
|||Problem fixed by IT support, lesson learned, thanks again!
I gave one of my SQL accounts sysadmin privileges and made sure its default
database was master. ; )
Randall Arnold
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158259731.549347@.xnews001...
> Thanks.
> There are other sysadmin logins, I just don't have access to them. I
> finally got ahold of our IT guys who do have such access so hopefully they
> can get it resolved for me. Thanks for your advice!
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
>
Showing posts with label stupid. Show all posts
Showing posts with label stupid. Show all posts
Sunday, March 25, 2012
default database problem
I did a stupid thing yesterday: I had to detach a database, and forgot it
was the default for that login account (Windows authentication). After it
was detached, I was unable to connect to that server through enterprise
manager afterward with that login.
Once I realized my error, I found a way to reattach the database using query
analyzer and that worked great. Unfortunately, I still can't login with the
Windows admin account. I connected as a different user (SQL Server internal
account) and saw that the default database for the Windows admin account in
question is now blank. !!!
So it seems I'm in a catch-22. Can't login to fix my login. I can't get a
response from our support staff so I'm trying to figure this out myself. I
need to have this access restored asap. How do I recover from this
embarrassing blunder (technically, not emotionally... lol)?
Thanks,
Randall Arnold> Once I realized my error, I found a way to reattach the database using query analyzer and
that
> worked great.
This indicates that you have some login that you can use, possibly with sysa
dmin privileges. Use
sp_defaultdb to change the default database for the messed up login.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158249818.863918@.xnews001...
>I did a stupid thing yesterday: I had to detach a database, and forgot it w
as the default for that
>login account (Windows authentication). After it was detached, I was unabl
e to connect to that
>server through enterprise manager afterward with that login.
> Once I realized my error, I found a way to reattach the database using que
ry analyzer and that
> worked great. Unfortunately, I still can't login with the Windows admin a
ccount. I connected as
> a different user (SQL Server internal account) and saw that the default da
tabase for the Windows
> admin account in question is now blank. !!!
> So it seems I'm in a catch-22. Can't login to fix my login. I can't get
a response from our
> support staff so I'm trying to figure this out myself. I need to have thi
s access restored asap.
> How do I recover from this embarrassing blunder (technically, not emotiona
lly... lol)?
> Thanks,
> Randall Arnold
>|||The problem is, the only login I had with sysadmin privileges is the one I
can no longer use. I tried the same local login I mentioned below, running
sp_defaultdb in query analyzer, and got this error:
Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
Cannot change default database belonging to someone else.
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
> This indicates that you have some login that you can use, possibly with
> sysadmin privileges. Use sp_defaultdb to change the default database for
> the messed up login.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158249818.863918@.xnews001...
>|||So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes sens
e it cannot change
default database for somebody else.
If the only sysadmin you have left is the messed up login, use ISQL.EXE, whi
ch will allow you in
even though the default database doesn't exist.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158254641.735397@.xnews001...
> The problem is, the only login I had with sysadmin privileges is the one I
can no longer use. I
> tried the same local login I mentioned below, running sp_defaultdb in quer
y analyzer, and got this
> error:
> Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
> Cannot change default database belonging to someone else.
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>|||Thanks.
There are other sysadmin logins, I just don't have access to them. I
finally got ahold of our IT guys who do have such access so hopefully they
can get it resolved for me. Thanks for your advice!
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
> So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes
> sense it cannot change default database for somebody else.
> If the only sysadmin you have left is the messed up login, use ISQL.EXE,
> which will allow you in even though the default database doesn't exist.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158254641.735397@.xnews001...
>|||Problem fixed by IT support, lesson learned, thanks again!
I gave one of my SQL accounts sysadmin privileges and made sure its default
database was master. ; )
Randall Arnold
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158259731.549347@.xnews001...
> Thanks.
> There are other sysadmin logins, I just don't have access to them. I
> finally got ahold of our IT guys who do have such access so hopefully they
> can get it resolved for me. Thanks for your advice!
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
>
was the default for that login account (Windows authentication). After it
was detached, I was unable to connect to that server through enterprise
manager afterward with that login.
Once I realized my error, I found a way to reattach the database using query
analyzer and that worked great. Unfortunately, I still can't login with the
Windows admin account. I connected as a different user (SQL Server internal
account) and saw that the default database for the Windows admin account in
question is now blank. !!!
So it seems I'm in a catch-22. Can't login to fix my login. I can't get a
response from our support staff so I'm trying to figure this out myself. I
need to have this access restored asap. How do I recover from this
embarrassing blunder (technically, not emotionally... lol)?
Thanks,
Randall Arnold> Once I realized my error, I found a way to reattach the database using query analyzer and
that
> worked great.
This indicates that you have some login that you can use, possibly with sysa
dmin privileges. Use
sp_defaultdb to change the default database for the messed up login.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158249818.863918@.xnews001...
>I did a stupid thing yesterday: I had to detach a database, and forgot it w
as the default for that
>login account (Windows authentication). After it was detached, I was unabl
e to connect to that
>server through enterprise manager afterward with that login.
> Once I realized my error, I found a way to reattach the database using que
ry analyzer and that
> worked great. Unfortunately, I still can't login with the Windows admin a
ccount. I connected as
> a different user (SQL Server internal account) and saw that the default da
tabase for the Windows
> admin account in question is now blank. !!!
> So it seems I'm in a catch-22. Can't login to fix my login. I can't get
a response from our
> support staff so I'm trying to figure this out myself. I need to have thi
s access restored asap.
> How do I recover from this embarrassing blunder (technically, not emotiona
lly... lol)?
> Thanks,
> Randall Arnold
>|||The problem is, the only login I had with sysadmin privileges is the one I
can no longer use. I tried the same local login I mentioned below, running
sp_defaultdb in query analyzer, and got this error:
Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
Cannot change default database belonging to someone else.
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
> This indicates that you have some login that you can use, possibly with
> sysadmin privileges. Use sp_defaultdb to change the default database for
> the messed up login.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158249818.863918@.xnews001...
>|||So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes sens
e it cannot change
default database for somebody else.
If the only sysadmin you have left is the messed up login, use ISQL.EXE, whi
ch will allow you in
even though the default database doesn't exist.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158254641.735397@.xnews001...
> The problem is, the only login I had with sysadmin privileges is the one I
can no longer use. I
> tried the same local login I mentioned below, running sp_defaultdb in quer
y analyzer, and got this
> error:
> Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
> Cannot change default database belonging to someone else.
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>|||Thanks.
There are other sysadmin logins, I just don't have access to them. I
finally got ahold of our IT guys who do have such access so hopefully they
can get it resolved for me. Thanks for your advice!
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
> So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes
> sense it cannot change default database for somebody else.
> If the only sysadmin you have left is the messed up login, use ISQL.EXE,
> which will allow you in even though the default database doesn't exist.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158254641.735397@.xnews001...
>|||Problem fixed by IT support, lesson learned, thanks again!
I gave one of my SQL accounts sysadmin privileges and made sure its default
database was master. ; )
Randall Arnold
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158259731.549347@.xnews001...
> Thanks.
> There are other sysadmin logins, I just don't have access to them. I
> finally got ahold of our IT guys who do have such access so hopefully they
> can get it resolved for me. Thanks for your advice!
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
>
default database problem
I did a stupid thing yesterday: I had to detach a database, and forgot it
was the default for that login account (Windows authentication). After it
was detached, I was unable to connect to that server through enterprise
manager afterward with that login.
Once I realized my error, I found a way to reattach the database using query
analyzer and that worked great. Unfortunately, I still can't login with the
Windows admin account. I connected as a different user (SQL Server internal
account) and saw that the default database for the Windows admin account in
question is now blank. !!!
So it seems I'm in a catch-22. Can't login to fix my login. I can't get a
response from our support staff so I'm trying to figure this out myself. I
need to have this access restored asap. How do I recover from this
embarrassing blunder (technically, not emotionally... lol)?
Thanks,
Randall Arnold> Once I realized my error, I found a way to reattach the database using query analyzer and that
> worked great.
This indicates that you have some login that you can use, possibly with sysadmin privileges. Use
sp_defaultdb to change the default database for the messed up login.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158249818.863918@.xnews001...
>I did a stupid thing yesterday: I had to detach a database, and forgot it was the default for that
>login account (Windows authentication). After it was detached, I was unable to connect to that
>server through enterprise manager afterward with that login.
> Once I realized my error, I found a way to reattach the database using query analyzer and that
> worked great. Unfortunately, I still can't login with the Windows admin account. I connected as
> a different user (SQL Server internal account) and saw that the default database for the Windows
> admin account in question is now blank. !!!
> So it seems I'm in a catch-22. Can't login to fix my login. I can't get a response from our
> support staff so I'm trying to figure this out myself. I need to have this access restored asap.
> How do I recover from this embarrassing blunder (technically, not emotionally... lol)?
> Thanks,
> Randall Arnold
>|||The problem is, the only login I had with sysadmin privileges is the one I
can no longer use. I tried the same local login I mentioned below, running
sp_defaultdb in query analyzer, and got this error:
Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
Cannot change default database belonging to someone else.
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great.
> This indicates that you have some login that you can use, possibly with
> sysadmin privileges. Use sp_defaultdb to change the default database for
> the messed up login.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158249818.863918@.xnews001...
>>I did a stupid thing yesterday: I had to detach a database, and forgot it
>>was the default for that login account (Windows authentication). After it
>>was detached, I was unable to connect to that server through enterprise
>>manager afterward with that login.
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great. Unfortunately, I still can't login
>> with the Windows admin account. I connected as a different user (SQL
>> Server internal account) and saw that the default database for the
>> Windows admin account in question is now blank. !!!
>> So it seems I'm in a catch-22. Can't login to fix my login. I can't get
>> a response from our support staff so I'm trying to figure this out
>> myself. I need to have this access restored asap. How do I recover from
>> this embarrassing blunder (technically, not emotionally... lol)?
>> Thanks,
>> Randall Arnold
>|||So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes sense it cannot change
default database for somebody else.
If the only sysadmin you have left is the messed up login, use ISQL.EXE, which will allow you in
even though the default database doesn't exist.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158254641.735397@.xnews001...
> The problem is, the only login I had with sysadmin privileges is the one I can no longer use. I
> tried the same local login I mentioned below, running sp_defaultdb in query analyzer, and got this
> error:
> Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
> Cannot change default database belonging to someone else.
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>> Once I realized my error, I found a way to reattach the database using query analyzer and that
>> worked great.
>> This indicates that you have some login that you can use, possibly with sysadmin privileges. Use
>> sp_defaultdb to change the default database for the messed up login.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
>> news:1158249818.863918@.xnews001...
>>I did a stupid thing yesterday: I had to detach a database, and forgot it was the default for
>>that login account (Windows authentication). After it was detached, I was unable to connect to
>>that server through enterprise manager afterward with that login.
>> Once I realized my error, I found a way to reattach the database using query analyzer and that
>> worked great. Unfortunately, I still can't login with the Windows admin account. I connected
>> as a different user (SQL Server internal account) and saw that the default database for the
>> Windows admin account in question is now blank. !!!
>> So it seems I'm in a catch-22. Can't login to fix my login. I can't get a response from our
>> support staff so I'm trying to figure this out myself. I need to have this access restored
>> asap. How do I recover from this embarrassing blunder (technically, not emotionally... lol)?
>> Thanks,
>> Randall Arnold
>>
>|||Thanks.
There are other sysadmin logins, I just don't have access to them. I
finally got ahold of our IT guys who do have such access so hopefully they
can get it resolved for me. Thanks for your advice!
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
> So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes
> sense it cannot change default database for somebody else.
> If the only sysadmin you have left is the messed up login, use ISQL.EXE,
> which will allow you in even though the default database doesn't exist.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158254641.735397@.xnews001...
>> The problem is, the only login I had with sysadmin privileges is the one
>> I can no longer use. I tried the same local login I mentioned below,
>> running sp_defaultdb in query analyzer, and got this error:
>> Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
>> Cannot change default database belonging to someone else.
>> Randall
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great.
>> This indicates that you have some login that you can use, possibly with
>> sysadmin privileges. Use sp_defaultdb to change the default database for
>> the messed up login.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
>> news:1158249818.863918@.xnews001...
>>I did a stupid thing yesterday: I had to detach a database, and forgot
>>it was the default for that login account (Windows authentication).
>>After it was detached, I was unable to connect to that server through
>>enterprise manager afterward with that login.
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great. Unfortunately, I still can't
>> login with the Windows admin account. I connected as a different user
>> (SQL Server internal account) and saw that the default database for the
>> Windows admin account in question is now blank. !!!
>> So it seems I'm in a catch-22. Can't login to fix my login. I can't
>> get a response from our support staff so I'm trying to figure this out
>> myself. I need to have this access restored asap. How do I recover
>> from this embarrassing blunder (technically, not emotionally... lol)?
>> Thanks,
>> Randall Arnold
>>
>>
>|||Problem fixed by IT support, lesson learned, thanks again!
I gave one of my SQL accounts sysadmin privileges and made sure its default
database was master. ; )
Randall Arnold
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158259731.549347@.xnews001...
> Thanks.
> There are other sysadmin logins, I just don't have access to them. I
> finally got ahold of our IT guys who do have such access so hopefully they
> can get it resolved for me. Thanks for your advice!
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
>> So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes
>> sense it cannot change default database for somebody else.
>> If the only sysadmin you have left is the messed up login, use ISQL.EXE,
>> which will allow you in even though the default database doesn't exist.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
>> news:1158254641.735397@.xnews001...
>> The problem is, the only login I had with sysadmin privileges is the one
>> I can no longer use. I tried the same local login I mentioned below,
>> running sp_defaultdb in query analyzer, and got this error:
>> Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
>> Cannot change default database belonging to someone else.
>> Randall
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great.
>> This indicates that you have some login that you can use, possibly with
>> sysadmin privileges. Use sp_defaultdb to change the default database
>> for the messed up login.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
>> news:1158249818.863918@.xnews001...
>>I did a stupid thing yesterday: I had to detach a database, and forgot
>>it was the default for that login account (Windows authentication).
>>After it was detached, I was unable to connect to that server through
>>enterprise manager afterward with that login.
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great. Unfortunately, I still can't
>> login with the Windows admin account. I connected as a different user
>> (SQL Server internal account) and saw that the default database for
>> the Windows admin account in question is now blank. !!!
>> So it seems I'm in a catch-22. Can't login to fix my login. I can't
>> get a response from our support staff so I'm trying to figure this out
>> myself. I need to have this access restored asap. How do I recover
>> from this embarrassing blunder (technically, not emotionally... lol)?
>> Thanks,
>> Randall Arnold
>>
>>
>
was the default for that login account (Windows authentication). After it
was detached, I was unable to connect to that server through enterprise
manager afterward with that login.
Once I realized my error, I found a way to reattach the database using query
analyzer and that worked great. Unfortunately, I still can't login with the
Windows admin account. I connected as a different user (SQL Server internal
account) and saw that the default database for the Windows admin account in
question is now blank. !!!
So it seems I'm in a catch-22. Can't login to fix my login. I can't get a
response from our support staff so I'm trying to figure this out myself. I
need to have this access restored asap. How do I recover from this
embarrassing blunder (technically, not emotionally... lol)?
Thanks,
Randall Arnold> Once I realized my error, I found a way to reattach the database using query analyzer and that
> worked great.
This indicates that you have some login that you can use, possibly with sysadmin privileges. Use
sp_defaultdb to change the default database for the messed up login.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158249818.863918@.xnews001...
>I did a stupid thing yesterday: I had to detach a database, and forgot it was the default for that
>login account (Windows authentication). After it was detached, I was unable to connect to that
>server through enterprise manager afterward with that login.
> Once I realized my error, I found a way to reattach the database using query analyzer and that
> worked great. Unfortunately, I still can't login with the Windows admin account. I connected as
> a different user (SQL Server internal account) and saw that the default database for the Windows
> admin account in question is now blank. !!!
> So it seems I'm in a catch-22. Can't login to fix my login. I can't get a response from our
> support staff so I'm trying to figure this out myself. I need to have this access restored asap.
> How do I recover from this embarrassing blunder (technically, not emotionally... lol)?
> Thanks,
> Randall Arnold
>|||The problem is, the only login I had with sysadmin privileges is the one I
can no longer use. I tried the same local login I mentioned below, running
sp_defaultdb in query analyzer, and got this error:
Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
Cannot change default database belonging to someone else.
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great.
> This indicates that you have some login that you can use, possibly with
> sysadmin privileges. Use sp_defaultdb to change the default database for
> the messed up login.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158249818.863918@.xnews001...
>>I did a stupid thing yesterday: I had to detach a database, and forgot it
>>was the default for that login account (Windows authentication). After it
>>was detached, I was unable to connect to that server through enterprise
>>manager afterward with that login.
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great. Unfortunately, I still can't login
>> with the Windows admin account. I connected as a different user (SQL
>> Server internal account) and saw that the default database for the
>> Windows admin account in question is now blank. !!!
>> So it seems I'm in a catch-22. Can't login to fix my login. I can't get
>> a response from our support staff so I'm trying to figure this out
>> myself. I need to have this access restored asap. How do I recover from
>> this embarrassing blunder (technically, not emotionally... lol)?
>> Thanks,
>> Randall Arnold
>|||So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes sense it cannot change
default database for somebody else.
If the only sysadmin you have left is the messed up login, use ISQL.EXE, which will allow you in
even though the default database doesn't exist.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158254641.735397@.xnews001...
> The problem is, the only login I had with sysadmin privileges is the one I can no longer use. I
> tried the same local login I mentioned below, running sp_defaultdb in query analyzer, and got this
> error:
> Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
> Cannot change default database belonging to someone else.
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>> Once I realized my error, I found a way to reattach the database using query analyzer and that
>> worked great.
>> This indicates that you have some login that you can use, possibly with sysadmin privileges. Use
>> sp_defaultdb to change the default database for the messed up login.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
>> news:1158249818.863918@.xnews001...
>>I did a stupid thing yesterday: I had to detach a database, and forgot it was the default for
>>that login account (Windows authentication). After it was detached, I was unable to connect to
>>that server through enterprise manager afterward with that login.
>> Once I realized my error, I found a way to reattach the database using query analyzer and that
>> worked great. Unfortunately, I still can't login with the Windows admin account. I connected
>> as a different user (SQL Server internal account) and saw that the default database for the
>> Windows admin account in question is now blank. !!!
>> So it seems I'm in a catch-22. Can't login to fix my login. I can't get a response from our
>> support staff so I'm trying to figure this out myself. I need to have this access restored
>> asap. How do I recover from this embarrassing blunder (technically, not emotionally... lol)?
>> Thanks,
>> Randall Arnold
>>
>|||Thanks.
There are other sysadmin logins, I just don't have access to them. I
finally got ahold of our IT guys who do have such access so hopefully they
can get it resolved for me. Thanks for your advice!
Randall
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
> So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes
> sense it cannot change default database for somebody else.
> If the only sysadmin you have left is the messed up login, use ISQL.EXE,
> which will allow you in even though the default database doesn't exist.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
> news:1158254641.735397@.xnews001...
>> The problem is, the only login I had with sysadmin privileges is the one
>> I can no longer use. I tried the same local login I mentioned below,
>> running sp_defaultdb in query analyzer, and got this error:
>> Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
>> Cannot change default database belonging to someone else.
>> Randall
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great.
>> This indicates that you have some login that you can use, possibly with
>> sysadmin privileges. Use sp_defaultdb to change the default database for
>> the messed up login.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
>> news:1158249818.863918@.xnews001...
>>I did a stupid thing yesterday: I had to detach a database, and forgot
>>it was the default for that login account (Windows authentication).
>>After it was detached, I was unable to connect to that server through
>>enterprise manager afterward with that login.
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great. Unfortunately, I still can't
>> login with the Windows admin account. I connected as a different user
>> (SQL Server internal account) and saw that the default database for the
>> Windows admin account in question is now blank. !!!
>> So it seems I'm in a catch-22. Can't login to fix my login. I can't
>> get a response from our support staff so I'm trying to figure this out
>> myself. I need to have this access restored asap. How do I recover
>> from this embarrassing blunder (technically, not emotionally... lol)?
>> Thanks,
>> Randall Arnold
>>
>>
>|||Problem fixed by IT support, lesson learned, thanks again!
I gave one of my SQL accounts sysadmin privileges and made sure its default
database was master. ; )
Randall Arnold
"Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
news:1158259731.549347@.xnews001...
> Thanks.
> There are other sysadmin logins, I just don't have access to them. I
> finally got ahold of our IT guys who do have such access so hopefully they
> can get it resolved for me. Thanks for your advice!
> Randall
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:uyVKisC2GHA.3476@.TK2MSFTNGP04.phx.gbl...
>> So you tried sp_defaultdb using a login which isn't sysadmin? OK, makes
>> sense it cannot change default database for somebody else.
>> If the only sysadmin you have left is the messed up login, use ISQL.EXE,
>> which will allow you in even though the default database doesn't exist.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
>> news:1158254641.735397@.xnews001...
>> The problem is, the only login I had with sysadmin privileges is the one
>> I can no longer use. I tried the same local login I mentioned below,
>> running sp_defaultdb in query analyzer, and got this error:
>> Server: Msg 15132, Level 16, State 1, Procedure sp_defaultdb, Line 14
>> Cannot change default database belonging to someone else.
>> Randall
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:%23rfuV%23B2GHA.3372@.TK2MSFTNGP04.phx.gbl...
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great.
>> This indicates that you have some login that you can use, possibly with
>> sysadmin privileges. Use sp_defaultdb to change the default database
>> for the messed up login.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Randall Arnold" <randall.nospam.arnold@.nokia.com.> wrote in message
>> news:1158249818.863918@.xnews001...
>>I did a stupid thing yesterday: I had to detach a database, and forgot
>>it was the default for that login account (Windows authentication).
>>After it was detached, I was unable to connect to that server through
>>enterprise manager afterward with that login.
>> Once I realized my error, I found a way to reattach the database using
>> query analyzer and that worked great. Unfortunately, I still can't
>> login with the Windows admin account. I connected as a different user
>> (SQL Server internal account) and saw that the default database for
>> the Windows admin account in question is now blank. !!!
>> So it seems I'm in a catch-22. Can't login to fix my login. I can't
>> get a response from our support staff so I'm trying to figure this out
>> myself. I need to have this access restored asap. How do I recover
>> from this embarrassing blunder (technically, not emotionally... lol)?
>> Thanks,
>> Randall Arnold
>>
>>
>
Sunday, March 11, 2012
Declare or Create cursor
Hello guys,just wanted to ask a question some might percieve it as a stupid one but I don't know so I will ask anyway?
Is Declare Cursor same as Create Cursor and if not what is the major difference?Hello guys,just wanted to ask a question some might percieve it as a stupid one but I don't know so I will ask anyway?
Is Declare Cursor same as Create Cursor and if not what is the major difference?
DECLARE CURSOR is part of the T-SQL Language dfinition. CREATE CURSOR is not.|||I do not think there is "Create Cursor". Does anyone know that?
Is Declare Cursor same as Create Cursor and if not what is the major difference?Hello guys,just wanted to ask a question some might percieve it as a stupid one but I don't know so I will ask anyway?
Is Declare Cursor same as Create Cursor and if not what is the major difference?
DECLARE CURSOR is part of the T-SQL Language dfinition. CREATE CURSOR is not.|||I do not think there is "Create Cursor". Does anyone know that?
Friday, February 17, 2012
debug via Enterprise Manager
Hi
I wonder if there is a trick I can use to debug what was changed in my
database (mssql2000).
The idea maybe sound stupid but my boss have got old console application
which is doing some changes in database (only in data in tables rather:). I
have no code for that application and we are wondering where this appl.
writes - what changes and so on.
Any idea?
DarekHi
You may want to use SQL Profiler to see what statements the application is
sending to the database server.
John
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:eIJBW$aKGHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> I wonder if there is a trick I can use to debug what was changed in my
> database (mssql2000).
> The idea maybe sound stupid but my boss have got old console application
> which is doing some changes in database (only in data in tables rather:).
> I have no code for that application and we are wondering where this appl.
> writes - what changes and so on.
> Any idea?
> Darek
>
I wonder if there is a trick I can use to debug what was changed in my
database (mssql2000).
The idea maybe sound stupid but my boss have got old console application
which is doing some changes in database (only in data in tables rather:). I
have no code for that application and we are wondering where this appl.
writes - what changes and so on.
Any idea?
DarekHi
You may want to use SQL Profiler to see what statements the application is
sending to the database server.
John
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:eIJBW$aKGHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> I wonder if there is a trick I can use to debug what was changed in my
> database (mssql2000).
> The idea maybe sound stupid but my boss have got old console application
> which is doing some changes in database (only in data in tables rather:).
> I have no code for that application and we are wondering where this appl.
> writes - what changes and so on.
> Any idea?
> Darek
>
debug via Enterprise Manager
Hi
I wonder if there is a trick I can use to debug what was changed in my
database (mssql2000).
The idea maybe sound stupid but my boss have got old console application
which is doing some changes in database (only in data in tables rather
. I
have no code for that application and we are wondering where this appl.
writes - what changes and so on.
Any idea?
DarekHi
You may want to use SQL Profiler to see what statements the application is
sending to the database server.
John
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:eIJBW$aKGHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> I wonder if there is a trick I can use to debug what was changed in my
> database (mssql2000).
> The idea maybe sound stupid but my boss have got old console application
> which is doing some changes in database (only in data in tables rather.
> I have no code for that application and we are wondering where this appl.
> writes - what changes and so on.
> Any idea?
> Darek
>
I wonder if there is a trick I can use to debug what was changed in my
database (mssql2000).
The idea maybe sound stupid but my boss have got old console application
which is doing some changes in database (only in data in tables rather
. Ihave no code for that application and we are wondering where this appl.
writes - what changes and so on.
Any idea?
DarekHi
You may want to use SQL Profiler to see what statements the application is
sending to the database server.
John
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:eIJBW$aKGHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> I wonder if there is a trick I can use to debug what was changed in my
> database (mssql2000).
> The idea maybe sound stupid but my boss have got old console application
> which is doing some changes in database (only in data in tables rather
.> I have no code for that application and we are wondering where this appl.
> writes - what changes and so on.
> Any idea?
> Darek
>
debug via Enterprise Manager
Hi
I wonder if there is a trick I can use to debug what was changed in my
database (mssql2000).
The idea maybe sound stupid but my boss have got old console application
which is doing some changes in database (only in data in tables rather. I
have no code for that application and we are wondering where this appl.
writes - what changes and so on.
Any idea?
Darek
Hi
You may want to use SQL Profiler to see what statements the application is
sending to the database server.
John
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:eIJBW$aKGHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> I wonder if there is a trick I can use to debug what was changed in my
> database (mssql2000).
> The idea maybe sound stupid but my boss have got old console application
> which is doing some changes in database (only in data in tables rather.
> I have no code for that application and we are wondering where this appl.
> writes - what changes and so on.
> Any idea?
> Darek
>
I wonder if there is a trick I can use to debug what was changed in my
database (mssql2000).
The idea maybe sound stupid but my boss have got old console application
which is doing some changes in database (only in data in tables rather
. Ihave no code for that application and we are wondering where this appl.
writes - what changes and so on.
Any idea?
Darek
Hi
You may want to use SQL Profiler to see what statements the application is
sending to the database server.
John
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:eIJBW$aKGHA.216@.TK2MSFTNGP15.phx.gbl...
> Hi
> I wonder if there is a trick I can use to debug what was changed in my
> database (mssql2000).
> The idea maybe sound stupid but my boss have got old console application
> which is doing some changes in database (only in data in tables rather
.> I have no code for that application and we are wondering where this appl.
> writes - what changes and so on.
> Any idea?
> Darek
>
Subscribe to:
Posts (Atom)