January 5, 2016 at 10:35 am
I'm debugging a SSIS package running on SQL Server 2008 R2. It reads from a staging table (in a staging db) and writes to one of two tables (in the destination db). New rows get written directly to a destination table; modified rows get written to an update table that is used later on to update the destination table.
While monitoring this package in action on a large staging table, I noticed that there are two active connections:
1. to the staging table, which lives in a staging database on the same instance as the destination table.
2. to the destination table, which is on the same instance as the staging database but in a different database
I was surprised to see that the connections are using TCP instead of Shared Memory. Any clues as to why this might be and how to change it?
Gerald Britton, Pluralsight courses
January 5, 2016 at 11:19 am
What is your connection string?
January 5, 2016 at 11:53 am
My connection string server name was a FQDN. Turned out that was the issue. SQL (apparently) doesn't parse the server name to extract the leftmost value and compare that to the local host name. I changed the connection string and now I'm using Shared Memory as expected.
Gerald Britton, Pluralsight courses
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply