Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: "Callahan, Barry" <callahan at UU dot NET>
Subject: RE: sp_serverinfo error and MS SQL 7.0
Date: Oct 26 1999 8:38PM

sp_server_info is a Catalog Stored Procedure. I believe 
these procs were originally added in Sybase to support ODBC.

It's been a Long time since i messed w/MS SQL server
but there use to be a separate SQL install script for
'ODBC'.  It was in that backend script that these procs
were created.  Does your MS SQL 7 install have the
other catalog procs? (ie: sp_columns, sp_column_privileges, 
sp_tables, etc...)


> -----Original Message-----
> From: Michael Peppler []
> Sent: Tuesday, October 26, 1999 4:25 PM
> To: SybPerl Discussion List
> Subject: Re: sp_serverinfo error and MS SQL 7.0
> Wechsler, Steven M wrote:
> > 
> > OK, we've been successfully connecting to SQL Server 7.0 
> for several months
> > now, using DB-Library with Sybperl (we're using the patched 
> MS-SQL Server
> > rather than the fixed version of Sybperl).
> > 
> > However, whenever we connect, we get an error message saying:
> > 
> > Msg 2812, Level 16, State 62
> > Server 'servername',
> >         Could not find stored procedure 'sp_serverinfo'.
> > 
> > It appears that either DB-Library or Sybperl is running 
> this sp_serverinfo
> > command.  However, even without a successful run of sp_serverinfo,
> > everything elase appears to work fine.
> > 
> > Sybooks makes two mentions of sp_serverinfo, but only in 
> passing (i.e. when
> > it is mentioning what stored procedures access a different 
> procedure).  A
> > search of Usenet turned up similarly useless information.
> > 
> > Any idea what causes this error, and if there's a way to 
> suppress it?  I
> > know, I could modify the error handler to specifically 
> ignore this message
> > on connecting, but sometimes I prefer to use nsql's 
> built-in error handlers.
> I don't know where in sybperl this proc would get called...
> My guess would be that something else is calling this proc, 
> but I don't
> know where that would happen (or if it should happen on login...???)
> Michael