Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

The identifier that starts with....is too long. Maximum length is 128. Expand / Collapse
Author
Message
Posted Tuesday, August 9, 2005 8:33 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, January 7, 2008 11:38 AM
Points: 74, Visits: 2

I have a SP that recieves parameters except that when sending down one parameter I get the following error.

The identifier that starts with....is too long. Maximum length is 128.

I have one parameter that is passing a length of 140.

Is there a way to increase this size pass 128?

Thanks

 




Post #208737
Posted Tuesday, August 9, 2005 8:38 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, January 9, 2014 3:33 AM
Points: 1,559, Visits: 672

AFAIK, nope.

BOL states the max identifier length as 128 characters. Can't go beyond that.

/Kenneth




Post #208739
Posted Tuesday, August 9, 2005 9:08 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, November 7, 2014 9:20 AM
Points: 2,555, Visits: 607
here're some links that could provide you with workarounds....


source 1
source 2
source 3
sql 7.0








**ASCII stupid question, get a stupid ANSI !!!**
Post #208762
Posted Tuesday, August 9, 2005 10:52 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, January 9, 2014 3:33 AM
Points: 1,559, Visits: 672

Ah, now I understand the problem (duh)

Don't use double quotes around strings, use single quotes. This is the most bulletproof solution, since then it doesn't matter if QUOTED_IDENTIFIER is set to either OFF or ON. Remember, in Transact-SQL, always use single quotes, never double quotes.

If, somehow you can't avoid to use double quotes denoting strings, then you must ensure that for the connection QUOTED_IDENTIFIER is set to OFF. It's a bit more hassle this way, since each connection can override the serversetting - you have to enforce this everywhere in the clientcode making the connection...

/Kenneth




Post #208813
Posted Wednesday, June 25, 2008 3:46 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, March 9, 2011 4:50 AM
Points: 2, Visits: 15
Single quote should be used when passing String to a query or Stroed Procedure in Transact SQL
Post #523124
Posted Thursday, January 27, 2011 6:55 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, December 17, 2011 5:16 PM
Points: 1, Visits: 11
Thanks guys! the single quote idea worked for me.
Post #1055042
Posted Tuesday, March 20, 2012 9:56 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Saturday, June 7, 2014 8:55 PM
Points: 19, Visits: 201
I am getting the exact same error. I have a huge binary file and I want to pass the binary content (as is) from Visual FoxPro to SQL Server using insert command or update command. I am getting this error. Is there a way to bypass this error?

My SQL command looks like this

insert into Settings (SettingVal) values (cast (long binary string here as varbinary(max)) -- tried using image with the same result.
May be I should try adding single quotes around the varbinary value?
Post #1269681
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse