Parameter identifier naming rules

• Paul van der Eerden

  SSC Enthusiast

  Points: 148

  More actions

  January 10, 2007 at 5:31 pm

  #368718

  Here's another one that I think is valid (because it works and appears to comply with identifier naming), but maybe someone else can find evidence to the contrary:

  CREATE PROCEDURE sp_dumbParamName

   @INT int

  AS

   -- do something

  END

  Since the identifier is @INT it does not conflict with any reserved words.  It works in SQL Management Studio, but I have another app that doesn't like it.  Is the other app faulty?  SHould this be supported?

  Thanks,

   

  Paul

• MohammedU

  SSCoach

  Points: 19644

  More actions

  January 10, 2007 at 6:05 pm

  #682589

  INT is reserve word but not @int...when you add @ sign to a word it will be treated as local variable ... I think your application is the problem...

  Is the name of a variable of any type except cursor, text, ntext, image, or table. Variable names must start with one at sign (@). Variable names must comply with the rules for identifiers.

   

  MohammedU
  Microsoft SQL Server MVP

• Paul van der Eerden

  SSC Enthusiast

  Points: 148

  More actions

  January 10, 2007 at 6:09 pm

  #682591

  Thanks for your reply,

  No, my SP only takes the one parameter (not any of the types you mention above), so I suspect it is the app that is doing things incorrectly. I have a feeling it is removing the @ symbol for presentation purposes, and then getting confused because the parameter name suddenly becomes a data type...

  Paul