Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
prpball
Starting Member
19 Posts |
 Posted - 2007-03-14 : 16:05:59
|
| When I change the tcp/ip port to anything other than 1433 my SSIS nor DTS packages run successfully. Does the tcp/ip port have to be on 1433 for the SSIS or DTS packages to run successfully? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-03-14 : 16:33:20
|
| No. But you may need to create an alias on the client to tell the client exactly how to connect to the SQL Server. You can create an alias using the SQL Server Configuration Manager tool.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
prpball
Starting Member
19 Posts |
Posted - 2007-03-15 : 09:14:06
|
| thanks, but how do I get my packages to use the alias and not the default tcp/ip port? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-03-15 : 13:17:22
|
| The alias can be the same name as the SQL Server.For instance, we've got an instance named SDSQL01\QTW. It listens on port 32456 (not the real port number as you never should post that on the Internet). My alias is like this:String Value: SDSQL01\QTWData Value: DBMSSOCN,SDSQL01,32456I'm showing you the raw data that makes it into the registry. DBMSSOCN is the dll to use for TCP/IP. So my alias is named SDSQL01\QTW and my SQL Server is named SDSQL01\QTW. The alias is there so that the client knows to use TCP/IP to connect to SDSQL01\QTW and to use 32456. I could have named the alias Alias1 and then had the data value be what I have above. I would then need to say Alias1 anywhere I would have normally said SDSQL01\QTW. I prefer to name my aliases the exact same name as the SQL Server names.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
Changing SQL Server 2005 Tcp/IP port