Jim Lawrence
accessd at shaw.ca
Wed May 16 10:32:04 CDT 2007
Hi john: This type of statement 'IN' may grind a network of users to a stand still but you are the only user so who cares but... Maybe it was a time-out issue.... but to lock it up?? Wow, never heard of that happening. Have you tried nested queries? Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Wednesday, May 16, 2007 7:39 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Processing diverse where clauses I can tell you that at the very end it locked up my dual proc machine as it pulls the results all together. I have never seen that happen before. Aside from that, what does the network have to do with anything? This is running in SQL Server 2005, using tables / drives on the same machine. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Wednesday, May 16, 2007 10:29 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Processing diverse where clauses Hi Arthur: The performance with the IN statement in this condition is not going to be an issue as there is only one person on the network. Jim _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com