Yep. That does it. So I've created a new internal standard to format all SQL Receive Location URIs as:
SQL://<host>/<database>/<application>/ That should save us any grief in the future. Peter ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bradley, Peter Sent: 21 August 2007 13:13 To: BizTalker@listserver.readify.net Subject: RE: [BizTalker] Reusing a SQL Adapter Hi Scott, You may well be correct. I'll need to wait an hour or so before I can try it, but it looks good in the BizTalk Admin console (i.e. I don't get any errors and the connection string is still correct). I saw something similar on (msdn kb842449), which didn't work for me. It said: "... manually change the Address (URI) property to a unique name. For example, if you have two receive locations that each have an Address (URI) property value that is set to SQL://./Northwind/, change the second Address (URI) property value to SQL://./NorthwindSecondary/" This doesn't work because it changes the connection string Initial Catalog to "NorthwindSecondary" (in the case of Microsoft's example). Since this database doesn't exist, BTS can't connect to the database. In my case, the URI for the first application is: SQL://cimislivedb/cimis/ Changing 'cimis' to 'cimistocams' in the second receive location fails as I explain above; but changing it to: SQL://cimislivedb/cimis/cimistocams ... looks better. At least, the connection string stays as it was. I'll post again in an hour or so with the result. Thanks a lot (and I agree with your convention, too). Peter ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Colestock Sent: 21 August 2007 12:54 To: BizTalker@listserver.readify.net Subject: RE: [BizTalker] Reusing a SQL Adapter >From docs: "The workaround is to edit the URI in the receive location to be of the form SQL:://host//database/ID, where ID is anything added to the URI. The example the SQL Adapter Sample uses is SQL://localhost/BTS2004_SQL_Adapter_Loans/Report." Might be interesting to use a convention that would tack on "#sproc_name" to the end (instead of /ID), similar to POP3 URLs and the like. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bradley, Peter Sent: Tuesday, August 21, 2007 6:33 AM To: BizTalker@listserver.readify.net Subject: [BizTalker] Reusing a SQL Adapter I've also posted this to microsoft.public.biztalk.general. So apologies for the cross posting, but I really need an answer quickly to this one, if possible. We recently implemented a BTS 2006 application that obtained data via a stored procedure from a particular remote SQL Server 2000 database via a SQL adapter. We are now on the point of implementing another application that gets data from the same database (using a different stored procedure, of course), but when I point it to the live data it will not create the receive location because it says that there is already one using the same connection string. How can I connect two or more SQL adapter receive locations to a database, and how can I configure them each to use a different stored procedure? The error message I'm getting is: "Address should be unique for receive location 'CimisSqlReceive Location'. Address 'SQL://cimislivedb/cimis' is already present for 'ItregSqlReceiveLocation'. (Microsoft.BizTalk.ExplorerOM)" Cheers Peter to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net
