I just realized that for some time I have been robotically using SET QUOTED_IDENTIFIER ON SET ANSI_NULLS OFF prior to my stored procedures (dervied from the microsoft standard stored procedure template) and SET QUOTED_IDENTIFIER OFF SET ANSI_NULLS ON after them. I understand the implications of both these options on a piece of SQL but I realized I don't really understand the implications for stored procedures. There are two potential outcomes I can see but don't know which is true: 1. Setting them will "bake" these options into the compiled stored procedure such that they will override the database defaults or 2. Setting them means the stored procedure applies the options to the interpretation and compilation of the stored procedures but whenever the stored procedure executes it uses the database default.
The implications of this are rather large on a database with many stored procedures and it could make debugging a bear. Any thoughts would be greatly appreciated, Adam Howitt http://www.webdevref.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:203818 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
