July 20, 2009 at 8:30 am
Is there a port number property on the OLE Source?
July 20, 2009 at 8:48 am
I believe you can use a comma to specify the server.
So for the sales server here: sales.sqlservercentral.com, 1899
would connect on port 1899.
July 20, 2009 at 9:47 am
thanks Steve,
Also wondering if anyone does this for servers setup on a non-standard port. I've had intermittent connection problems and was curious if this could be an issue. At the same time I have other ETLs that don't have a problem.
July 20, 2009 at 9:54 am
This should either work, or not work. If it's intermittent, you likely have some network or resource issue.
I'm not sure what most people use, but I've used this for years, since SS2K for those machines set on non-standard ports.
Note that if you connect to a named instance, the SQL Browser on UDP 1434 should return the port number to the calling app.
July 20, 2009 at 3:20 pm
I have updated all my connection manager configs to include the port number in the connection string.
You mentioned the browser, on the this particular server we are not running the browser service.
When I enter an invalid port number I get the same error message I've gotten in the past without supplying a port.
BUT, I have packages that also run successfully without the port. Very confusing. Also we are running SQL on a VM.
July 20, 2009 at 3:21 pm
I have updated all my connection manager configs to include the port number in the connection string.
You mentioned the browser, on the this particular server we are not running the browser service.
When I enter an invalid port number I get the same error message I've gotten in the past without supplying a port.
BUT, I have packages that also run successfully without the port. Very confusing. Also we are running SQL on a VM.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply