Using QUOTENAME()

Question

Using QUOTENAME()

Steve Jones - SSC Editor

SSC Guru

Points: 738043
More actions
August 19, 2018 at 11:28 pm

#77370

Comments posted to this topic are about the item Using QUOTENAME()

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Stewart "Arturius" Campbell SSC Guru Points: 72716 More actions · Answer 1

Nice question to start the week on, thanks Steve

____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”

Eirikur Eiriksson SSC Guru Points: 182947 More actions · Answer 2

Two points on the quotename function, the second parameter is the optional quote character and the function implicitly converts any input into nvarchar(258), except the XML data type.

Shayn Thomas SSCertifiable Points: 5863 More actions · Answer 3

nice question steve
ta

---------------------------------------------------------------------------------------
The more you know, the more you know that you dont know

Kevin3NF SSCarpal Tunnel Points: 4765 More actions · Answer 4

I only got this because Ken Fisher talked about at the North Texas SQL User group last Thursday

------------------------------------------------------------------------------------------------Standing in the gap between Consultant and ContractorKevin3NF DallasDBAs.com/Blog Why is my SQL Log File HUGE?!?![/url]The future of the DBA role...[/url]SQL Security Model in Plain English[/url]

cs_troyk SSCertifiable Points: 5383 More actions · Answer 5

One other important point (and, to me, the best reason to use QUOTENAME), is the built-in escaping of certain characters, which helps to prevent SQL Injection attacks in certain scenarios.

SELECT QUOTENAME('[]"''');

Using QUOTENAME()

Cookies on SQLServerCentral