Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Linked Server problem

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2001-01-20 : 10:55:29
Ian writes "sql server 7.0 sp2, Nt4 SP5, on Compaq Proliant 7000 4GB ram

Problem 1

I have a two SQL Servers each set up with the other as a linked server using a specific sql login. Most of the time queries (simple select * from tablename usually) across the servers work fine but occasionally they return 7399 errors. Usually I can get the problem to disappear by refreshing the table list from enterprise manager, the select then works.

Why? What is going wrong and how do I fix it permanently.

Problem 2
On one of the servers I can run rpc calls but not select statements. The other one works fine.

e.g.
exec [e-db02].master.dbo.sp_who2 active
go
SELECT * FROM [e-db02].qbis.dbo.control
go

returns the following
SPID  Status                         Login                                                HostName                       BlkBy DBName Command          CPUTime DiskIO LastBatch      ProgramName                    SPID  
----- ------------------------------ ---------------------------------------------------- ------------------------------ ----- ------ ---------------- ------- ------ -------------- ------------------------------ -----
1 sleeping sa . . master SIGNAL HANDLER 31 0 12/07 12:15:49 1
2 BACKGROUND sa . . master LOCK MONITOR 0 0 12/07 12:15:49 2
3 BACKGROUND sa . . master LAZY WRITER 0 0 12/07 12:15:49 3
4 sleeping sa . . master LOG WRITER 0 0 12/07 12:15:49 4
6 BACKGROUND sa . . master AWAITING COMMAND 0 425048 12/07 12:15:49 6
16 RUNNABLE RBSA_DOMAIN_1\A_SQLServer7 E-DB02 . PBIS CREATE INDEX 0 145024 01/16 10:35:21 ISQL-32 16
26 RUNNABLE RBSA_DOMAIN_1\reidb E-WK106 . master EXECUTE 0 26 01/16 09:50:46 MS SQL Query Analyzer 26
31 RUNNABLE edb01proxy E-DB01 . master SELECT INTO 0 30 01/16 10:35:16 Microsoft SQL Server 31
36 sleeping RBSA_DOMAIN_1\SQLAdmin E-WK125 . OBIS SELECT 98157 36583 01/16 10:19:19 Microsoft SQL Server OLAP Serv 36
37 sleeping RBSA_DOMAIN_1\SQLAdmin AP01 . OBIS SELECT 0 1393 01/16 10:32:37 Microsoft SQL Server Analysis 37

(10 row(s) affected)


Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error. The provider ran out of memory.

Again why and how do I fix it."
   

- Advertisement -