I am hoping that some of you better versed in MS-SQL and CF could clear this up for me.
Is there an issue with multiple users accidentally hitting the same data set that is contained in either a local(#tbl_name) or global(##tbl_name) temporary table? Books Online says that a local temp table is local to the current "session", but how does a session relate to the connections that CF maintains, ie connection pooling? If we have, say 5 "select into"s, one after another in a stored proc, and while user 1 is on the 3'rd select into, user2 is on the first, and both are "selecting into" the same global/local table, based upon different where clauses, will this cause "bad" data, ie data that doesn't meet the where clauses per user, to enter the temp table? And thus the resulting record set returned would be incorrect? I know that this has a slim margin of happening, but I'm thinking concurrent access, same as the old insert new user, select max id problem. I would like to avoid a transactional lock because of the bottle neck, I would prefer a more "proper" approach. My feeling is that this is an issue, my dba doesn't, but both of us don't really know for sure. I hope I made sense, let me know if I didn't. Thanks. Matthew P. Smith Web Developer, Object Oriented Naval Education & Training Professional Development & Technology Center (NETPDTC) (850)452-1001 ext. 1245 [EMAIL PROTECTED] ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
