![]() I've changed our script to include the -I switch to see if that fixes our issues.ġ) Does the SET QUOTED_IDENTIFIER ON statement affect only the DDL CREATE PROCEDURE statement, or does it also affect the execution of the stored proc also? My quick test indicates the latter.Ģ) As the default for this switch is ON, I am presuming that by me setting the -I switch of my sqlcmd query will have no adverse affects. I've just read that here (search for Example: Executing SQLCMD) and here that sqlcmd executes with quoted identifier off. Our scripts are all deployed as drop and create scripts and run via sqlcmd. ![]() I would have thought that this affected the CREATE PROCEDURE statement, but wouldn't have affected anything to do with the execution of that procedure. ![]() The thing is, I did this prior to the CREATE PROCEDURE call. I fixed it by modifiying the stored proc and setting the quoted identifier to ON. We just ran into a problem with one of our stored procs throwing an error SELECT failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |