Recent PostsRecent Posts Popular TopicsPopular Topics
 Home Search Members Calendar Who's On

 Single Quotation Marks in SQL Rate Topic Display Mode Topic Options
Author
 Message
 Posted Friday, January 4, 2013 10:19 AM
 SSCommitted Group: General Forum Members Last Login: 2 days ago @ 6:02 AM Points: 1,858, Visits: 2,652
 Steven Willis (1/4/2013)For anyone who really cares about proper typography The Chicago Manual of Style is the editor's Bible. Oh. I thought the Chicago Manual of Style was about pinstripes and fedoras. Thanks for clearing that up!
Post #1402993
 Posted Friday, January 4, 2013 10:36 AM
 SSC-Addicted Group: General Forum Members Last Login: Sunday, September 29, 2013 1:24 AM Points: 429, Visits: 1,721
 sknox (1/4/2013)Steven Willis (1/4/2013)For anyone who really cares about proper typography The Chicago Manual of Style is the editor's Bible. Oh. I thought the Chicago Manual of Style was about pinstripes and fedoras. Thanks for clearing that up! Maybe you were confused like Bela Oxmyx... A Piece of the Action.
Post #1403004
 Posted Sunday, January 6, 2013 6:33 AM
 SSCertifiable Group: General Forum Members Last Login: Today @ 2:30 PM Points: 6,545, Visits: 17,212
 Nice article and a classic subject. One workaround is to use tokens when writing dynamic SQL statements, especially if nested more than one level;`DECLARE @TOKEN NVARCHAR(1) = NCHAR(123)DECLARE @SQ NVARCHAR(1) = NCHAR(39)DECLARE @SQLSTR NVARCHAR(MAX) = N' DECLARE @TOKEN NVARCHAR(1) = NCHAR(124) DECLARE @SQ NVARCHAR(1) = NCHAR(39) DECLARE @SQLSTR NVARCHAR(MAX) = N{ DECLARE @TOKEN NVARCHAR(1) = NCHAR(125) DECLARE @SQ NVARCHAR(1) = NCHAR(39) DECLARE @SQLSTR NVARCHAR(MAX) = N| DECLARE @TOKEN NVARCHAR(1) = NCHAR(126) DECLARE @SQ NVARCHAR(1) = NCHAR(39) DECLARE @SQLSTR NVARCHAR(MAX) = N} DECLARE @quotedvar nvarchar(100) = N~O¡Neil~ SELECT @quotedvar = REPLACE(@quotedvar,NCHAR(161),NCHAR(39)) PRINT @quotedvar } PRINT @@NESTLEVEL SELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ) PRINT @SQLSTR EXEC sp_executesql @SQLSTR | PRINT @@NESTLEVEL SELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ) PRINT @SQLSTR EXEC sp_executesql @SQLSTR { PRINT @@NESTLEVEL SELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ) PRINT @SQLSTR EXEC sp_executesql @SQLSTR'PRINT @@NESTLEVELSELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ)PRINT @SQLSTREXEC sp_executesql @SQLSTR`Execution result;`0 DECLARE @TOKEN NVARCHAR(1) = NCHAR(124) DECLARE @SQ NVARCHAR(1) = NCHAR(39) DECLARE @SQLSTR NVARCHAR(MAX) = N' DECLARE @TOKEN NVARCHAR(1) = NCHAR(125) DECLARE @SQ NVARCHAR(1) = NCHAR(39) DECLARE @SQLSTR NVARCHAR(MAX) = N| DECLARE @TOKEN NVARCHAR(1) = NCHAR(126) DECLARE @SQ NVARCHAR(1) = NCHAR(39) DECLARE @SQLSTR NVARCHAR(MAX) = N} DECLARE @quotedvar nvarchar(100) = N~O¡Neil~ SELECT @quotedvar = REPLACE(@quotedvar,NCHAR(161),NCHAR(39)) PRINT @quotedvar } PRINT @@NESTLEVEL SELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ) PRINT @SQLSTR EXEC sp_executesql @SQLSTR | PRINT @@NESTLEVEL SELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ) PRINT @SQLSTR EXEC sp_executesql @SQLSTR ' PRINT @@NESTLEVEL SELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ) PRINT @SQLSTR EXEC sp_executesql @SQLSTR2 DECLARE @TOKEN NVARCHAR(1) = NCHAR(125) DECLARE @SQ NVARCHAR(1) = NCHAR(39) DECLARE @SQLSTR NVARCHAR(MAX) = N' DECLARE @TOKEN NVARCHAR(1) = NCHAR(126) DECLARE @SQ NVARCHAR(1) = NCHAR(39) DECLARE @SQLSTR NVARCHAR(MAX) = N} DECLARE @quotedvar nvarchar(100) = N~O¡Neil~ SELECT @quotedvar = REPLACE(@quotedvar,NCHAR(161),NCHAR(39)) PRINT @quotedvar } PRINT @@NESTLEVEL SELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ) PRINT @SQLSTR EXEC sp_executesql @SQLSTR ' PRINT @@NESTLEVEL SELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ) PRINT @SQLSTR EXEC sp_executesql @SQLSTR 4 DECLARE @TOKEN NVARCHAR(1) = NCHAR(126) DECLARE @SQ NVARCHAR(1) = NCHAR(39) DECLARE @SQLSTR NVARCHAR(MAX) = N' DECLARE @quotedvar nvarchar(100) = N~O¡Neil~ SELECT @quotedvar = REPLACE(@quotedvar,NCHAR(161),NCHAR(39)) PRINT @quotedvar ' PRINT @@NESTLEVEL SELECT @SQLSTR = REPLACE(@SQLSTR,@TOKEN,@SQ) PRINT @SQLSTR EXEC sp_executesql @SQLSTR 6 DECLARE @quotedvar nvarchar(100) = N'O¡Neil' SELECT @quotedvar = REPLACE(@quotedvar,NCHAR(161),NCHAR(39)) PRINT @quotedvar O'Neil`Eirikur
Post #1403328
 Posted Sunday, January 6, 2013 2:22 PM
 SSC-Addicted Group: General Forum Members Last Login: Sunday, September 29, 2013 1:24 AM Points: 429, Visits: 1,721
 Eirikur Eiriksson (1/6/2013)One workaround is to use tokens when writing dynamic SQL statements, especially if nested more than one level;That sounds like a great idea. I've never seen the problem dealt with like that before. Thumbs up!
Post #1403355
 Posted Monday, January 7, 2013 11:46 PM
 SSC-Enthusiastic Group: General Forum Members Last Login: Saturday, May 21, 2016 11:48 PM Points: 151, Visits: 713
 Since our apps are primarily web pages we step around the problem by converting the problem characters to unicode. The single quote character is converted to "'". It no longer is in the way, there is no special coding necessary and it displays properly in a browser.
Post #1403986
 Posted Sunday, January 13, 2013 3:16 PM
 Valued Member Group: General Forum Members Last Login: Friday, July 29, 2016 8:05 AM Points: 54, Visits: 322
 IMHO dynamic SQL outside of database is a recepie for a disaster. Anybody hear about SQL injection in last 15+ years? Why not use parameterised stored procedures/user-defined functions. I would use dynamic SQL only for Sql script generation or Within stored procedure (in exceptional cases when nothing Else could work).
Post #1406517
 Posted Sunday, January 13, 2013 4:10 PM
 Hall of Fame Group: General Forum Members Last Login: Today @ 10:54 AM Points: 3,486, Visits: 2,016
 I would tend to agree. Dynamic SQL is a very powerful tool. But it's just one tool of many and should only be used when it's appropriate and with appropriate attention paid to security. For that matter combining parameters and dynamic sql can be particularly powerful. Kenneth FisherI strive to live in a world where a chicken can cross the road without being questioned about its motives.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/Link to my Blog Post --> www.SQLStudies.com
Post #1406526
 Posted Sunday, January 13, 2013 4:18 PM
 Hall of Fame Group: General Forum Members Last Login: Today @ 10:54 AM Points: 3,486, Visits: 2,016
 Sorry I'm a little bit late posting my answer to the "homework". Lot's of people had posted correct answers already so I didn't feel all that rushed to post my answer .`DECLARE @topsql nvarchar(200)SET @topsql = 'DECLARE @quotedvar nvarchar(100) ' + char(13) + 'DECLARE @sql nvarchar(1000) ' + char(13) + '' + char(13) + 'SET @quotedvar = ''O''''Neil''' + char(13) + '' + char(13) + 'SET @sql = ''PRINT '''''' + REPLACE(@quotedvar,'''''''','''''''''''') + ''''''''' + char(13) + '' + char(13) + 'PRINT @sql' + char(13) + '' + char(13) + 'EXEC sp_executesql @sql' PRINT @topsqlPRINT '-------'EXEC sp_executesql @topsql`The best test for the correct answer is of course to run it and see if the output works :) Kenneth FisherI strive to live in a world where a chicken can cross the road without being questioned about its motives.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/Link to my Blog Post --> www.SQLStudies.com
Post #1406528
 Posted Friday, July 11, 2014 1:18 AM
 SSC Veteran Group: General Forum Members Last Login: Wednesday, November 23, 2016 7:56 AM Points: 275, Visits: 383
 I know the article is this simple to highlight the issue but I assert in real life you would not do this.If you are doing dynamic SQL then unless you want to be laughed at for introducing SQL injection into your work you are going to always uses parameterised SQL in which case quoting is not a problem in the exact same way it would not be a problem using a parameter that wasn't dynamic SQL.
Post #1591466
 Posted Friday, July 11, 2014 3:40 AM
 SSCertifiable Group: General Forum Members Last Login: Today @ 2:39 PM Points: 7,946, Visits: 19,037