Can't access linked server through Query Analyzer

Hi, i created a linked server and can see the tables shown in Enterprise Manager. When I log into Query Analyzer, I try to access the remote tables with the 4 part naming convention and i get
SELECT COUNT(*) FROM PGJE_06_sp.nodo_sp.bts.caso
Servidor: mensaje 208, nivel 16, estado 1, lXnea 1
El nombre de objeto 'nodo_sp.bts.caso' no es válido.
which means "Object name is invalid"
I've tried changing its case, login through windows authentication and sqlserver authentication, but I get the same problem.
I created a linked server "backwards", that is from server B to A, and it works fine. Other servers have a linked server to this same server B (PGJE_SP_06) and they work fine.
Thanks for your help
Israel,
1. Did you try selecting "Tools --> Query Analyzer" from the Enterprise Manager -- this should open the QA connection with the same credentials with which the Enterprise Manager is running.
2. Did you confirm that your FROM clause does not have any typos? (e.g., Is the linked server name correct? Did you check on your server "B" that "SELECT COUNT(*) FROM nodo_sp.bts.caso").
3. Did you try to use the OPENQUERY (LinkedServerName, 'Select count(*) from Table') syntax?
4. Can you double check your linked server settings match the settings (e.g. Provider) that you have on the servers which are able to execute the query successfully.
Thanks,
Tea C.
"Israel Perez" wrote:

> Hi, i created a linked server and can see the tables shown in Enterprise Manager. When I log into Query Analyzer, I try to access the remote tables with the 4 part naming convention and i get
> SELECT COUNT(*) FROM PGJE_06_sp.nodo_sp.bts.caso
> Servidor: mensaje 208, nivel 16, estado 1, lXnea 1
> El nombre de objeto 'nodo_sp.bts.caso' no es válido.
> which means "Object name is invalid"
> I've tried changing its case, login through windows authentication and sqlserver authentication, but I get the same problem.
> I created a linked server "backwards", that is from server B to A, and it works fine. Other servers have a linked server to this same server B (PGJE_SP_06) and they work fine.
> Thanks for your help

Can't access linked server through Query Analyzer

Hi, i created a linked server and can see the tables shown in Enterprise Man
ager. When I log into Query Analyzer, I try to access the remote tables with
the 4 part naming convention and i get
SELECT COUNT(*) FROM PGJE_06_sp.nodo_sp.bts.caso
Servidor: mensaje 208, nivel 16, estado 1, l_nea 1
El nombre de objeto 'nodo_sp.bts.caso' no es válido.
which means "Object name is invalid"
I've tried changing its case, login through windows authentication and sqlse
rver authentication, but I get the same problem.
I created a linked server "backwards", that is from server B to A, and it wo
rks fine. Other servers have a linked server to this same server B (PGJE_SP_
06) and they work fine.
Thanks for your helpIsrael,
1. Did you try selecting "Tools --> Query Analyzer" from the Enterprise Mana
ger -- this should open the QA connection with the same credentials with wh
ich the Enterprise Manager is running.
2. Did you confirm that your FROM clause does not have any typos? (e.g., Is
the linked server name correct? Did you check on your server "B" that "SELE
CT COUNT(*) FROM nodo_sp.bts.caso").
3. Did you try to use the OPENQUERY (LinkedServerName, 'Select count(*) from
Table') syntax?
4. Can you double check your linked server settings match the settings (e.g.
Provider) that you have on the servers which are able to execute the query
successfully.
Thanks,
Tea C.
"Israel Perez" wrote:

> Hi, i created a linked server and can see the tables shown in Enterprise M
anager. When I log into Query Analyzer, I try to access the remote tables wi
th the 4 part naming convention and i get
> SELECT COUNT(*) FROM PGJE_06_sp.nodo_sp.bts.caso
> Servidor: mensaje 208, nivel 16, estado 1, l_nea 1
> El nombre de objeto 'nodo_sp.bts.caso' no es válido.
> which means "Object name is invalid"
> I've tried changing its case, login through windows authentication and sql
server authentication, but I get the same problem.
> I created a linked server "backwards", that is from server B to A, and it
works fine. Other servers have a linked server to this same server B (PGJE_S
P_06) and they work fine.
> Thanks for your helpsql

Cannot use Enterprise Manager to browse database.

Dear.
In recently , I cannot use Enterprise Manager to browse
datase the database. Waiting are long long time.
However,when I use Query Analyzer that is ok, no problem.
Could you help me.
Thanks.Hi,
Can you please clear your Windows users profile and re- register the SQL
server.
Note: Take a beackup of profiler befire dropping.
Thanks
Hari.
MCDBA
"Raymond" <anonymous@.discussions.microsoft.com> wrote in message
news:12c9901c3f6b0$8f817990$a401280a@.phx
.gbl...
> Dear.
> In recently , I cannot use Enterprise Manager to browse
> datase the database. Waiting are long long time.
> However,when I use Query Analyzer that is ok, no problem.
> Could you help me.
> Thanks.
>|||Thanks your reply.
I want to ask ..? what is Windows users profile in SQL server.
Thanks.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OvAIYRr9DHA.1428@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Can you please clear your Windows users profile and re- register the SQL
> server.
> Note: Take a beackup of profiler befire dropping.
>
> Thanks
> Hari.
> MCDBA
> "Raymond" <anonymous@.discussions.microsoft.com> wrote in message
> news:12c9901c3f6b0$8f817990$a401280a@.phx
.gbl...
>

Cannot update the table in SQL Analyzer

I want to update the table
se.g update myTable set t1=0,t2= 0
However, i got the following error
Could not allocate space for object '(SYSTEM table id: -631615181)' in
database 'TEMPDB' because the 'DEFAULT' filegroup is full.Looks like you're either out of hard drive space on the SQL Server, or the
filegroup where your tempdb (and probably master, etc.) are. Check and make
sure you have enough drive space, and maybe run some dbcc on your database
once you're sure you have at least 10% hard drive space free.
- Nevyn
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:%23w1JmfNCFHA.3976@.tk2msftngp13.phx.gbl...
>I want to update the table
> se.g update myTable set t1=0,t2= 0
> However, i got the following error
> Could not allocate space for object '(SYSTEM table id: -631615181)' in
> database 'TEMPDB' because the 'DEFAULT' filegroup is full.
>|||Agnes
1) Restart SQL Server (It will create a new TEMPDB)
2) DBCC SHRINKFILE
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:%23w1JmfNCFHA.3976@.tk2msftngp13.phx.gbl...
> I want to update the table
> se.g update myTable set t1=0,t2= 0
> However, i got the following error
> Could not allocate space for object '(SYSTEM table id: -631615181)' in
> database 'TEMPDB' because the 'DEFAULT' filegroup is full.
>

Cannot start SQL Trace (Profiler) on Windows 2000 Professional

Hello all!
I have installed SQL Server 7 Client components on a Windows 2000
Professional machine.
I can start the Query analyzer and I can use it to connect to servers.
However, when I try to start SQL trace, I am getting the following
error message
"sqltrace.exe, not a valid win32 application."
Have any of you come across this problem? Please suggest a solution.
If you need any more information, please let me know.
Thank you,
Martin.
The file could have been corrupted. Have you checked your disk to see if
there are any errors?
You may be able to fix it by reinstalling the client utilities, if that is
not a problem.
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Martin Thomas" <martintms99@.yahoo.com> wrote in message
news:752207f2.0408090315.1eb0d689@.posting.google.c om...
> Hello all!
> I have installed SQL Server 7 Client components on a Windows 2000
> Professional machine.
> I can start the Query analyzer and I can use it to connect to servers.
> However, when I try to start SQL trace, I am getting the following
> error message
> "sqltrace.exe, not a valid win32 application."
> Have any of you come across this problem? Please suggest a solution.
> If you need any more information, please let me know.
> Thank you,
> Martin.

cannot run DTS Package from SQL Query Analyzer

I attemped to run dts package to transform data from AS400/DB2 by using Client Access ODBC ( Ms Windows 2000 Server, Ms SQL 2K, Client Access Driver 4.5)

but the result of testing has messed me up

because when i used this command via SQL Query Analyzer

exec master..xp_cmdshell 'DTSRun /S "MySVR" /U "sa" /N "dtsTEST" /G "{482209FD-0891-11D8-868C-00E0299B4BCF}" /A "G1":"8"="200310" /W "0"'

but it doesn't work

I wonder why.. because it can be executed in MS-Dos prompt successfully.
if I type

DTSRun /S "MySVR" /U "sa" /N "dtsTEST" /G "{482209FD-0891-11D8-868C-00E0299B4BCF}" /A "G1":"8"="200310" /W "0"

in the command line.

If somebody know please give me some advice (urgently!!).What is the error?

When run from dos it will be run on your client m/c. When from query analyser on the server using the sql server service account (probably)

Try logging on to the server as the sql server service account and running it in the designer and see what happens.|||I didn't run dos-command on Client M/C, I tested on Server M/C itself
and it success.

But when I tried to run by query analyzer, it takes much time (> 20 min and nothing happens) for executing and there was no error show on the screen. so I had to kill the process because it seemed not work .
And this process I tested on Server M/C also, by using Sql Admin (sa).

How could I solve this problem?|||It can be run properly in DTS Designer, but cannot run in Query analyzer.|||Does it have any user interaction - have you left in a debug msgbox?

I meant the account that the sql server service uses to logon - see services.
Maybe it needs access to something that this account doesn't have permission on.|||I checked already that the log on user-id has full permission, and the sign on user name and password for AS400 has been specify in DSN that use via client access express driver by setting the sign on information as 'use windows user name and password, no promping'.

If this problem is related to the security of sql server, why it can be run in DTS Designer(which has no pop up message box for user interface) with no popup error message and the result of transformation is correct.|||Because dts is a client application.
When you run it from query analyser the client is the server which gives it a different environment.

If you have already run it from the sql server service account then that limits the things that can be wrong.
Try turning on logging to see if any steps are run and what the error is.|||why i can run DTS Package in query analyzer if i change the source of DTS to be MsAccess file, on the server m/c not client. run in command line, no problem also.

why i cannot run in query analyzer if i specified source DSN as AS400/DB2, but run properly in command line by using same script.