October 19, 2011 at 8:53 am
Let's hope there is a solution to this weird problem.
I have several DNS aliases set up on my local machine. When the packages that I am working on get moved to development - staging - live environments, they need DNS aliases otherwise I gotta fill out paperwork. Ok, fair enough and easy enough to do.
Originally, I had the packages configured with OLE DB connection managers with the server name directly referenced. Each package worked fine. Found out I had to go the DNS alias route, made them, changed the connection managers accordingly and all was going swimmingly. The last package I am working on decides to throw a "Login Timeout Expired" error when I use the DNS alias. If I use the server name direct, it run fines. Alias results in timeout. There are two tasks in this package, an Execute SQL Task that truncates the table being loaded and a Data Flow task that just pulls data from one table to another, no transformations. The result set ~28,000,000 records. Maybe someone could shed some light on something I am missing? Thanks!
October 19, 2011 at 9:12 am
Is it a named instance it is trying to connect to?
CEWII
October 19, 2011 at 9:20 am
No just the default server name. I.e. server name is Server1 my DNS alias is Members. I can see the tables on Server1 using the alias in SSIS. I can connect to Database Engine in SSMS using Members.
October 21, 2011 at 8:49 am
Problem fixed. Completely unrelated to what I was asking. Thanks though!
October 21, 2011 at 9:49 am
Wonderful news, glad to hear it.
CEWII
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply