Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Stored Procedure Naming Restriction?

2 posts in General Discussion Last posting was on 2003-05-29 15:18:54.0Z
philb Posted on 2003-05-29 15:18:54.0Z
From: philb
Date: Thu, 29 May 2003 11:18:54 -0400
Newsgroups: ianywhere.public.general
Subject: Stored Procedure Naming Restriction?
Message-ID: <A009954C4B78D5B3005420BF85256D35.005420D285256D35@webforums>
Lines: 16
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub ianywhere.public.general:1113
Article PK: 3042

We preface our stored procedures with sp_
(e.g. create procedure sp_xxx()...)

Someone said that was a bad idea because the sp_ was somehow "reserved" for
database use and that by using that prefix we would slow things down
because it had to scan for a system procedure of that neame first.

I had never heard this, and in ianywhere system procedures tend to be
sa_xxxx anyway.

Has anyone ever heard of this in Sybase (or any other db, for that matter?)

We're always happy to up performance with minor tweeks, but renaming some
300 procs may not be 'minor'!

TIA


Chris Keating (iAnywhere Solutions) Posted on 2003-05-29 14:59:17.0Z
From: "Chris Keating \(iAnywhere Solutions\)" <keating@iAnywhere.com>
References: <A009954C4B78D5B3005420BF85256D35.005420D285256D35@webforums>
Subject: Re: Stored Procedure Naming Restriction?
Date: Thu, 29 May 2003 10:59:17 -0400
Lines: 36
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <uxZhjNfJDHA.311@forums-1-dub>
Newsgroups: ianywhere.public.general
NNTP-Posting-Host: keating-xp.sybase.com 172.31.140.19
Path: forums-1-dub!forums-master.sybase.com!forums-1-dub.sybase.com
Xref: forums-1-dub ianywhere.public.general:1114
Article PK: 3377

Whoever told you that was incorrect as there is no restriction on naming in
this context.
--

Chris Keating
Sybase Adaptive Server Anywhere Professional Version 8
iAnywhere Solutions http://www.iAnywhere.com

** Please only post to the newsgroup

** Whitepapers can be found at http://www.iAnywhere.com/developer
** EBFs can be found at http://downloads.sybase.com/swx/sdmain.stm
** Use CaseXpress to report bugs http://casexpress.sybase.com

<philb> wrote in message
news:A009954C4B78D5B3005420BF85256D35.005420D285256D35@webforums...
> We preface our stored procedures with sp_
> (e.g. create procedure sp_xxx()...)
>
> Someone said that was a bad idea because the sp_ was somehow "reserved"
for
> database use and that by using that prefix we would slow things down
> because it had to scan for a system procedure of that neame first.
>
> I had never heard this, and in ianywhere system procedures tend to be
> sa_xxxx anyway.
>
> Has anyone ever heard of this in Sybase (or any other db, for that
matter?)
>
> We're always happy to up performance with minor tweeks, but renaming some
> 300 procs may not be 'minor'!
>
> TIA