Cannot Drop Table

I have a table with no dependencies. I cannot drop the table. I tried
from EM to delete it. I tried from Query Analyzer. I cannot even
delete an index that it has. It's not a big table and it only has about
6,000 rows. Any ideas where to look? Thanks.
What does "cannot" mean? Do you get an error message? If so, what is it?
http://www.aspfaq.com/
(Reverse address to reply.)
"CR" <chuck._rich7ardson@.sfcc.edu> wrote in message
news:#TO86GevEHA.1260@.TK2MSFTNGP12.phx.gbl...
> I have a table with no dependencies. I cannot drop the table. I tried
> from EM to delete it. I tried from Query Analyzer. I cannot even
> delete an index that it has. It's not a big table and it only has about
> 6,000 rows. Any ideas where to look? Thanks.
|||CR wrote:
> I have a table with no dependencies. I cannot drop the table. I
> tried from EM to delete it. I tried from Query Analyzer. I cannot
> even delete an index that it has. It's not a big table and it only
> has about 6,000 rows. Any ideas where to look? Thanks.
More information please. Can you post the error you are seeing.
Also, grab the id for the table from sysobjects. Then, run sp_lock and
see if any other spid has a lock on the table.
David Gugick
Imceda Software
www.imceda.com
|||Are you SURE that someone or something doesn't have a lock on it?
"CR" <chuck._rich7ardson@.sfcc.edu> wrote in message
news:%23TO86GevEHA.1260@.TK2MSFTNGP12.phx.gbl...
> I have a table with no dependencies. I cannot drop the table. I tried
> from EM to delete it. I tried from Query Analyzer. I cannot even
> delete an index that it has. It's not a big table and it only has about
> 6,000 rows. Any ideas where to look? Thanks.
|||That's part of the problem -- there is no error message -- just hangs
and I have to kill application from task manager.
Aaron [SQL Server MVP] wrote:

> What does "cannot" mean? Do you get an error message? If so, what is it?
>
|||It is looking like a lock now. Thanks to all. I just didn't think of that.
David Gugick wrote:

> CR wrote:
>
> More information please. Can you post the error you are seeing.
> Also, grab the id for the table from sysobjects. Then, run sp_lock and
> see if any other spid has a lock on the table.
>

Cannot Drop Table

I have a table with no dependencies. I cannot drop the table. I tried
from EM to delete it. I tried from Query Analyzer. I cannot even
delete an index that it has. It's not a big table and it only has about
6,000 rows. Any ideas where to look? Thanks.What does "cannot" mean? Do you get an error message? If so, what is it?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"CR" <chuck._rich7ardson@.sfcc.edu> wrote in message
news:#TO86GevEHA.1260@.TK2MSFTNGP12.phx.gbl...
> I have a table with no dependencies. I cannot drop the table. I tried
> from EM to delete it. I tried from Query Analyzer. I cannot even
> delete an index that it has. It's not a big table and it only has about
> 6,000 rows. Any ideas where to look? Thanks.|||CR wrote:
> I have a table with no dependencies. I cannot drop the table. I
> tried from EM to delete it. I tried from Query Analyzer. I cannot
> even delete an index that it has. It's not a big table and it only
> has about 6,000 rows. Any ideas where to look? Thanks.
More information please. Can you post the error you are seeing.
Also, grab the id for the table from sysobjects. Then, run sp_lock and
see if any other spid has a lock on the table.
David Gugick
Imceda Software
www.imceda.com|||Are you SURE that someone or something doesn't have a lock on it?
"CR" <chuck._rich7ardson@.sfcc.edu> wrote in message
news:%23TO86GevEHA.1260@.TK2MSFTNGP12.phx.gbl...
> I have a table with no dependencies. I cannot drop the table. I tried
> from EM to delete it. I tried from Query Analyzer. I cannot even
> delete an index that it has. It's not a big table and it only has about
> 6,000 rows. Any ideas where to look? Thanks.|||That's part of the problem -- there is no error message -- just hangs
and I have to kill application from task manager.
Aaron [SQL Server MVP] wrote:
> What does "cannot" mean? Do you get an error message? If so, what is it?
>|||It is looking like a lock now. Thanks to all. I just didn't think of that.
David Gugick wrote:
> CR wrote:
>> I have a table with no dependencies. I cannot drop the table. I
>> tried from EM to delete it. I tried from Query Analyzer. I cannot
>> even delete an index that it has. It's not a big table and it only
>> has about 6,000 rows. Any ideas where to look? Thanks.
>
> More information please. Can you post the error you are seeing.
> Also, grab the id for the table from sysobjects. Then, run sp_lock and
> see if any other spid has a lock on the table.
>

Cannot Drop Table

I have a table with no dependencies. I cannot drop the table. I tried
from EM to delete it. I tried from Query Analyzer. I cannot even
delete an index that it has. It's not a big table and it only has about
6,000 rows. Any ideas where to look? Thanks.What does "cannot" mean? Do you get an error message? If so, what is it?
http://www.aspfaq.com/
(Reverse address to reply.)
"CR" <chuck._rich7ardson@.sfcc.edu> wrote in message
news:#TO86GevEHA.1260@.TK2MSFTNGP12.phx.gbl...
> I have a table with no dependencies. I cannot drop the table. I tried
> from EM to delete it. I tried from Query Analyzer. I cannot even
> delete an index that it has. It's not a big table and it only has about
> 6,000 rows. Any ideas where to look? Thanks.|||CR wrote:
> I have a table with no dependencies. I cannot drop the table. I
> tried from EM to delete it. I tried from Query Analyzer. I cannot
> even delete an index that it has. It's not a big table and it only
> has about 6,000 rows. Any ideas where to look? Thanks.
More information please. Can you post the error you are seeing.
Also, grab the id for the table from sysobjects. Then, run sp_lock and
see if any other spid has a lock on the table.
David Gugick
Imceda Software
www.imceda.com|||Are you SURE that someone or something doesn't have a lock on it?
"CR" <chuck._rich7ardson@.sfcc.edu> wrote in message
news:%23TO86GevEHA.1260@.TK2MSFTNGP12.phx.gbl...
> I have a table with no dependencies. I cannot drop the table. I tried
> from EM to delete it. I tried from Query Analyzer. I cannot even
> delete an index that it has. It's not a big table and it only has about
> 6,000 rows. Any ideas where to look? Thanks.|||That's part of the problem -- there is no error message -- just hangs
and I have to kill application from task manager.
Aaron [SQL Server MVP] wrote:

> What does "cannot" mean? Do you get an error message? If so, what is it?
>|||It is looking like a lock now. Thanks to all. I just didn't think of that.
David Gugick wrote:

> CR wrote:
>
>
> More information please. Can you post the error you are seeing.
> Also, grab the id for the table from sysobjects. Then, run sp_lock and
> see if any other spid has a lock on the table.
>sql

Cannot connect with Enterprise Manager

Hi All
I can connect to a server with Query Analyzer but not with
Enterprise manager (from a lot of clients so problem is
not client based). I used to be able to connect using
both, then all of a sudden it stopped. I rebooted the
server and Enterprise Manager connectivity worked for a
few hours and then stopped again (QA access still works!).
Can anyone think of any reason why this may be so?
Thanks
Jono
Jono
Any error message?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:ad9901c488df$5d5c9690$a501280a@.phx.gbl...
> Hi All
> I can connect to a server with Query Analyzer but not with
> Enterprise manager (from a lot of clients so problem is
> not client based). I used to be able to connect using
> both, then all of a sudden it stopped. I rebooted the
> server and Enterprise Manager connectivity worked for a
> few hours and then stopped again (QA access still works!).
> Can anyone think of any reason why this may be so?
> Thanks
> Jono
|||No, just hangs.

>--Original Message--
>Jono
>Any error message?
>
|||No, just hangs.

>--Original Message--
>Jono
>Any error message?
>

Cannot connect with Enterprise Manager

Hi All
I can connect to a server with Query Analyzer but not with
Enterprise manager (from a lot of clients so problem is
not client based). I used to be able to connect using
both, then all of a sudden it stopped. I rebooted the
server and Enterprise Manager connectivity worked for a
few hours and then stopped again (QA access still works!).
Can anyone think of any reason why this may be so?
Thanks
JonoJono
Any error message?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:ad9901c488df$5d5c9690$a501280a@.phx.gbl...
> Hi All
> I can connect to a server with Query Analyzer but not with
> Enterprise manager (from a lot of clients so problem is
> not client based). I used to be able to connect using
> both, then all of a sudden it stopped. I rebooted the
> server and Enterprise Manager connectivity worked for a
> few hours and then stopped again (QA access still works!).
> Can anyone think of any reason why this may be so?
> Thanks
> Jono|||No, just hangs.
>--Original Message--
>Jono
>Any error message?
>|||No, just hangs.
>--Original Message--
>Jono
>Any error message?
>

Cannot connect with Enterprise Manager

Hi All
I can connect to a server with Query Analyzer but not with
Enterprise manager (from a lot of clients so problem is
not client based). I used to be able to connect using
both, then all of a sudden it stopped. I rebooted the
server and Enterprise Manager connectivity worked for a
few hours and then stopped again (QA access still works!).
Can anyone think of any reason why this may be so?
Thanks
JonoJono
Any error message?
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:ad9901c488df$5d5c9690$a501280a@.phx.gbl...
> Hi All
> I can connect to a server with Query Analyzer but not with
> Enterprise manager (from a lot of clients so problem is
> not client based). I used to be able to connect using
> both, then all of a sudden it stopped. I rebooted the
> server and Enterprise Manager connectivity worked for a
> few hours and then stopped again (QA access still works!).
> Can anyone think of any reason why this may be so?
> Thanks
> Jono|||No, just hangs.

>--Original Message--
>Jono
>Any error message?
>|||No, just hangs.

>--Original Message--
>Jono
>Any error message?
>

Cannot connect using sql authentication in query analyzer

I just moved a database from one sql server to another. Both use Windows
2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
I connect to the database in the old server without a problem. I connect to
the new server fine with NT authentication, or if I log in as sa with SQL
authentication, but if I log in as a different user with SQL authentication
on the new server, I get this message:
Unable to connect to server Enterprise3:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
Server is terminating this process.
Ooops - Just remembered one other piece that may be impartant: We were
swapping the two servers, so had to rename both. With SQL Server 7, that
means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
to reapply the service packs and the hotfixes, but it will not allow it.
(Current installation is more recent.) This is not a problem with the SP3
server, but only with the sp4+ server.
"UWKC Admin" wrote:

> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Hi
What do you call "mini-reinstall"? If you have problems, always do a full
install, anything else is not supported by Microsoft.
Regards
Mike
"UWKC Admin" wrote:
[vbcol=seagreen]
> Ooops - Just remembered one other piece that may be impartant: We were
> swapping the two servers, so had to rename both. With SQL Server 7, that
> means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
> to reapply the service packs and the hotfixes, but it will not allow it.
> (Current installation is more recent.) This is not a problem with the SP3
> server, but only with the sp4+ server.
> "UWKC Admin" wrote:
|||Mike - Thanks for the question. When I say mini-reinstall, I mean the
reinstall that SQL Server demands we do after renaming a SQL Server 7.0
installation. It tells us something to the effect that that the
installstallation is bad and may have been tampered with, then tells us to
reinstall SQL Server. We do that, using the original SQL Server CD. I call
it a mini-install because it only takes a couple of minutes to complete.
"UWKC Admin" wrote:

> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Did you run sp_dropserver and sp_addserver after you
changed the server name and updated the registry with the
SQL Server CD (the process you refer to as a mini-reinstall
just updates the server name entries in the registry)?
e.g.
sp_dropserver 'YourOldServerName'
go
sp_addserver 'YourNewServerName', local
This part of the process just updates the server name in the
sysservers table. You should run in on both servers that you
renamed.
I'm not sure this will make any difference as I don't
remember anyone getting access violations if they miss any
of the steps in renaming a server...but worth a try.
-Sue
On Thu, 9 Dec 2004 11:33:06 -0800, "UWKC Admin"
<UWKCAdmin@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mike - Thanks for the question. When I say mini-reinstall, I mean the
>reinstall that SQL Server demands we do after renaming a SQL Server 7.0
>installation. It tells us something to the effect that that the
>installstallation is bad and may have been tampered with, then tells us to
>reinstall SQL Server. We do that, using the original SQL Server CD. I call
>it a mini-install because it only takes a couple of minutes to complete.
>"UWKC Admin" wrote:

cannot connect to SQL Server via Query Analyzer

Hello, I am new to SQL and I would like to connect to a remote sql server.
I have Win 2k Professional installed at my PC and I have installation CD of
SQL Server 2000 Developer Edition.
I have chosen following options during installation:
SQL Server 2000 Components --> Install Database Server --> Local
Computer --> Create a new instance of SQL Server, or install Client
tools --> Client tools only
All installation process has looked good, no error message during it.
Now I am running SQL Query Analyzer and I am trying to connect to our remote
SQL server (which is certainly running) but without any success, the error
message "Unable to connect to server xxxxxx: SQL Server doesnot exist or
access denied." always will appear.
Maybe there is something wrong with my PC as only following ports are opened
there: 80, 135, 139, 445, 1025
I think that also the port 1434 should be opened but it is not and I cannot
open it.
Please help
MarkIf you are connecting to a default instance then, try to use the follwing
for your server name
tcp:<servername>,1433
replace <servername> with your server name.
and make sure the port 1433 is open.
This way we are forcing it to use the tcpip protocol on the specified port.
Be default the default instance listens on port 1433.
hth
--
Vikram Vamshi
Eclipsys Corporation
"Marcello" <marcello@.inetcom.cz> wrote in message
news:%23Ufg2GFIFHA.2860@.TK2MSFTNGP12.phx.gbl...
> Hello, I am new to SQL and I would like to connect to a remote sql server.
> I have Win 2k Professional installed at my PC and I have installation CD
> of
> SQL Server 2000 Developer Edition.
> I have chosen following options during installation:
> SQL Server 2000 Components --> Install Database Server --> Local
> Computer --> Create a new instance of SQL Server, or install Client
> tools --> Client tools only
> All installation process has looked good, no error message during it.
> Now I am running SQL Query Analyzer and I am trying to connect to our
> remote
> SQL server (which is certainly running) but without any success, the error
> message "Unable to connect to server xxxxxx: SQL Server doesnot exist or
> access denied." always will appear.
> Maybe there is something wrong with my PC as only following ports are
> opened
> there: 80, 135, 139, 445, 1025
> I think that also the port 1434 should be opened but it is not and I
> cannot
> open it.
> Please help
> Mark
>

cannot connect to SQL Server via Query Analyzer

Hello, I am new to SQL and I would like to connect to a remote sql server.
I have Win 2k Professional installed at my PC and I have installation CD of
SQL Server 2000 Developer Edition.
I have chosen following options during installation:
SQL Server 2000 Components --> Install Database Server --> Local
Computer --> Create a new instance of SQL Server, or install Client
tools --> Client tools only
All installation process has looked good, no error message during it.
Now I am running SQL Query Analyzer and I am trying to connect to our remote
SQL server (which is certainly running) but without any success, the error
message "Unable to connect to server xxxxxx: SQL Server doesnot exist or
access denied." always will appear.
Maybe there is something wrong with my PC as only following ports are opened
there: 80, 135, 139, 445, 1025
I think that also the port 1434 should be opened but it is not and I cannot
open it.
Please help
Mark
If you are connecting to a default instance then, try to use the follwing
for your server name
tcp:<servername>,1433
replace <servername> with your server name.
and make sure the port 1433 is open.
This way we are forcing it to use the tcpip protocol on the specified port.
Be default the default instance listens on port 1433.
hth
Vikram Vamshi
Eclipsys Corporation
"Marcello" <marcello@.inetcom.cz> wrote in message
news:%23Ufg2GFIFHA.2860@.TK2MSFTNGP12.phx.gbl...
> Hello, I am new to SQL and I would like to connect to a remote sql server.
> I have Win 2k Professional installed at my PC and I have installation CD
> of
> SQL Server 2000 Developer Edition.
> I have chosen following options during installation:
> SQL Server 2000 Components --> Install Database Server --> Local
> Computer --> Create a new instance of SQL Server, or install Client
> tools --> Client tools only
> All installation process has looked good, no error message during it.
> Now I am running SQL Query Analyzer and I am trying to connect to our
> remote
> SQL server (which is certainly running) but without any success, the error
> message "Unable to connect to server xxxxxx: SQL Server doesnot exist or
> access denied." always will appear.
> Maybe there is something wrong with my PC as only following ports are
> opened
> there: 80, 135, 139, 445, 1025
> I think that also the port 1434 should be opened but it is not and I
> cannot
> open it.
> Please help
> Mark
>

Cannot Connect to SQL Server

I have been unable to connect since Sat to a SQL 2000 Server. Get the following error when trying to connect through Query Analyzer across the network:

Unable to connect to server
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General Network Error

In my Event Log I have the following error:

17310: process_loginread: Process 2548 genertaed ftal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Sevrer is terminating the process

When I try to connect through Query Analyzer locally, it locks up when I type in the sa password

Any help would be appreciatedRE:
I have been unable to connect since Sat to a SQL 2000 Server. Get the following error when trying to connect through Query Analyzer across the network:
Unable to connect to server
Server: Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General Network Error
When I try to connect through Query Analyzer locally (at the Server Console??) , it locks up when I type in the sa password

Q1 Any help would be appreciated

A1 Some things to consider and / or check may include:

Verify that the Sql Service is running. Is security (still) configured for the connection (sa = standard login) being attempted? Verify that the correct protocol, port, etc. is being accessed.

{More detailed information should make it easier for others to provide more useful / helpful feedback.}|||SQL Server is running. SQL Server Agent Locks Up when you try to start it.|||RE:
SQL Server is running.

Q2 SQL Server Agent Locks Up when you try to start it.

Some issues are apparently now resolved?

A2 Consider trying to:

Verify that the Sql Agent Service security context is configured with valid account information, or try using a local system account. Check the logs (incl. agent logs) for errors. Again, in general the more information available, the easier it is for others to provide helpful feedback.|||Didn't you apply patch against Slammer on version prior to SP2?|||Hi I'm learning SQL on the fly but I hope I might be able to help a bit, even if it's a little bit.
1. Are the computers talking? Can you see the other computer on the network?
2. Were any programs installed recently? It might've replaced a DLL that SQL Server might've needed to logon.
3. Are you sure about the SA password and user? If not, check the user and password.
4. What's the login mode? Might be a good idea to check it out.
5. Hard disk might be dued for final rites.

Good luck.

All the best,

Ka Kwok|||Originally posted by ispaleny
Didn't you apply patch against Slammer on version prior to SP2?

What did this virus do? I have the same problem.|||Originally posted by adrian320
What did this virus do? I have the same problem.

From memory it's a DOS attack. It makes a massive amount of requests to the server.
Regards,
Ka.|||http://www.microsoft.com/sql/techinfo/administration/2000/security/slammer.asp take help to combat the issue.|||Thank you for all the input,

I applied the hotfix for the virus to the 2000 sql servers we have running and they seem to work fine know.

Thanks.

Cannot connect to Server through Visual Studio .NET and Query Analyzer

Good day. I was able to connect to a database server using SQL Server
Enterprise Manager. The Server name specified on the tree is
JOMARGON(Windows NT). But no server was detected using either Visual
Studio .NET and SQL Server's query analyzer.

I highlighted one database (master) on the SQL Server Enterprise
Manager and chose 'SQL Query Analyzer' under the 'Tools' menu. It
worked. The Title of the Query Analyzer window is

SQL Server Analyzer - [Query- JOMARGON.master.JOMARGON\JM Gonzalez

and below on the status bar, I can see

JOMARGON(8.0) and JOMARGON\JM Gonzalez(52)

But again, I cannot connect manually using Query Analyzer as nothing is
listed in the SQL Server drop-down list

ThanksI am able to connect to the server using query analyzer. All I did was
restart my PC. The server name was JOMARGON.

But the only problem is, I still cannot connect to the server using
Visual Studio .NET's Server Explorer. Please help.

Thanks.|||JM (jomargon@.gmail.com) writes:
> But again, I cannot connect manually using Query Analyzer as nothing is
> listed in the SQL Server drop-down list

Just type in the name of the server.

> But the only problem is, I still cannot connect to the server using
> Visual Studio .NET's Server Explorer. Please help.

So what happens when you specify the server name?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Did that already and still cannot connect. By the way, I'm using
Windows NT Integrated Security. Pleae help.

Cannot connect to Query Analyzer

Just a few days ago, we changed the password on our server. After that, I
noticed that I could not open Query Analyzer from within Enterprise Manager.
I can open Query Analyzer from the start menu and login that way, but can
someone help in where to look to make it be able to open from with in
Enterprise Manager again. Also, I have a local SQL Server on my laptop and
when I tried to change the password to it, through the edit registration
section, I could not. Any thoughts on what where to look, or what I am
supposed to do, to be able to change the password on my local sql server?And what happens if while you are in Enterprise Manager, you
go to the menu to Tools and then select Query Analyzer? What
doesn't work? Does Query Analyzer not show up in the menu or
are you getting an error? If it's an error, what is the
exact error and error number?
To change the password for the service account from
Enterprise Manager, select the server, right click and
select Properties. Click on the Security tab. You can change
the password or account used for the service from this
screen.
-Sue
On Fri, 11 Aug 2006 05:32:02 -0700, Mike Collins
<MikeCollins@.discussions.microsoft.com> wrote:

>Just a few days ago, we changed the password on our server. After that, I
>noticed that I could not open Query Analyzer from within Enterprise Manager
.
>I can open Query Analyzer from the start menu and login that way, but can
>someone help in where to look to make it be able to open from with in
>Enterprise Manager again. Also, I have a local SQL Server on my laptop and
>when I tried to change the password to it, through the edit registration
>section, I could not. Any thoughts on what where to look, or what I am
>supposed to do, to be able to change the password on my local sql server?|||When I go to tools and select query analyzer, I get an hour glass cursor for
a second, or two, and then nothing.
I check the security tab and if you are talking about the startup service
account section, system account is currentlly selected, so I do not have the
option to type in an account and password. Should I be using a certain
account?
Thanks
"Sue Hoegemeier" wrote:

> And what happens if while you are in Enterprise Manager, you
> go to the menu to Tools and then select Query Analyzer? What
> doesn't work? Does Query Analyzer not show up in the menu or
> are you getting an error? If it's an error, what is the
> exact error and error number?
> To change the password for the service account from
> Enterprise Manager, select the server, right click and
> select Properties. Click on the Security tab. You can change
> the password or account used for the service from this
> screen.
> -Sue
> On Fri, 11 Aug 2006 05:32:02 -0700, Mike Collins
> <MikeCollins@.discussions.microsoft.com> wrote:
>
>|||A few things to check on the issue with Query Analyzer:
First make sure you don't have tracing turned on. I don't
think this is your issue as you can open QA from the menu
but you would want to check to make sure. Open the Data
Sources (ODBC) tool from Administrative Tools. Go to the
tracing tab and make sure all tracing is turned off - the
buttons would display "Start <tool name> Tracing" if it's
turned off.
Try replacing the MMC app for SQL Server from the original
media. Find the file on your PC named SQL Server Enterprise
Manager.MSC. Rename it and replace it in the same location
with the original MSC file of the same name from the
original installation media.
In terms of the startup account, you wouldn't change the
password if it's running under a system account. Passwords
for those are managed by the operating system. It's
generally a better idea to run SQL Server under domain
accounts rather than system accounts. If your local SQL
Server doesn't need access to network resources in your
domain, you can create a local account on your PC and just
use that to run SQL Server. You want to change services
accounts from that security tab you saw in Enterprise
Manager. When you change the service accounts through
Enterprise Manager, the security and permissions necessary
on your PC for the service account would automatically be
handled, properly set when using Enterprise Manager.
-Sue
On Fri, 11 Aug 2006 14:03:02 -0700, Mike Collins
<MikeCollins@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>When I go to tools and select query analyzer, I get an hour glass cursor fo
r
>a second, or two, and then nothing.
>I check the security tab and if you are talking about the startup service
>account section, system account is currentlly selected, so I do not have th
e
>option to type in an account and password. Should I be using a certain
>account?
>Thanks
>"Sue Hoegemeier" wrote:
>|||Ok...I tried what you suggested with no luck. I'm thinking of maybe
reinstalling SQL Server.
For Query Analyzer, I tried replacing the file as you suggested but had the
same results (Enterprise Manager starts up fine, but still cannot start QA
from within Enterprise Manager).
Changing the password. I created an account on my laptop and changed SQL
Server from the system account to a local one and got the following message:
"Unable to detect the status of Full Text Search service or unable to start
the service. Continuing to change the account might affect Full Text Search
service later. Would you like to continue?". I wasn't sure what to do from
there, so I cancelled.
Any suggestions?
"Sue Hoegemeier" wrote:

> A few things to check on the issue with Query Analyzer:
> First make sure you don't have tracing turned on. I don't
> think this is your issue as you can open QA from the menu
> but you would want to check to make sure. Open the Data
> Sources (ODBC) tool from Administrative Tools. Go to the
> tracing tab and make sure all tracing is turned off - the
> buttons would display "Start <tool name> Tracing" if it's
> turned off.
> Try replacing the MMC app for SQL Server from the original
> media. Find the file on your PC named SQL Server Enterprise
> Manager.MSC. Rename it and replace it in the same location
> with the original MSC file of the same name from the
> original installation media.
> In terms of the startup account, you wouldn't change the
> password if it's running under a system account. Passwords
> for those are managed by the operating system. It's
> generally a better idea to run SQL Server under domain
> accounts rather than system accounts. If your local SQL
> Server doesn't need access to network resources in your
> domain, you can create a local account on your PC and just
> use that to run SQL Server. You want to change services
> accounts from that security tab you saw in Enterprise
> Manager. When you change the service accounts through
> Enterprise Manager, the security and permissions necessary
> on your PC for the service account would automatically be
> handled, properly set when using Enterprise Manager.
> -Sue
> On Fri, 11 Aug 2006 14:03:02 -0700, Mike Collins
> <MikeCollins@.discussions.microsoft.com> wrote:
>
>|||On the Query Analyzer issue, try reinstalling the client
tools. If that still doesn't work, I have no idea how it
broke. Check that isqlw.exe has not been moved from the
default installation location, make sure the tools directory
is in your environment path, make sure you can access Query
Analyzer by typing isqlw from the run command, etc. But for
all of those issues, you should be getting a file not found
error. So I'd just try reinstalling the client and
reapplying the last service pack.
On the account, Try adding the local account you created to
the local administrators on your PC and make sure to add it
to the sysadmins server role on your PC. Then try changing
the service account in Enterprise Manager.
-Sue
On Tue, 15 Aug 2006 06:07:01 -0700, Mike Collins
<MikeCollins@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Ok...I tried what you suggested with no luck. I'm thinking of maybe
>reinstalling SQL Server.
>For Query Analyzer, I tried replacing the file as you suggested but had the
>same results (Enterprise Manager starts up fine, but still cannot start QA
>from within Enterprise Manager).
>Changing the password. I created an account on my laptop and changed SQL
>Server from the system account to a local one and got the following message
:
>"Unable to detect the status of Full Text Search service or unable to start
>the service. Continuing to change the account might affect Full Text Search
>service later. Would you like to continue?". I wasn't sure what to do from
>there, so I cancelled.
>Any suggestions?
>"Sue Hoegemeier" wrote:
>|||Thanks. I got the login issue to work, and I will reinstall client tools whe
n
I get a chance. Thanks again for your help.
"Sue Hoegemeier" wrote:

> On the Query Analyzer issue, try reinstalling the client
> tools. If that still doesn't work, I have no idea how it
> broke. Check that isqlw.exe has not been moved from the
> default installation location, make sure the tools directory
> is in your environment path, make sure you can access Query
> Analyzer by typing isqlw from the run command, etc. But for
> all of those issues, you should be getting a file not found
> error. So I'd just try reinstalling the client and
> reapplying the last service pack.
> On the account, Try adding the local account you created to
> the local administrators on your PC and make sure to add it
> to the sysadmins server role on your PC. Then try changing
> the service account in Enterprise Manager.
> -Sue
> On Tue, 15 Aug 2006 06:07:01 -0700, Mike Collins
> <MikeCollins@.discussions.microsoft.com> wrote:
>
>