1433 has been changed to 14000, then what should the
connectionstring in as ASP page look like so that it uses
the correct port in order to make the connection?
object.ConnectionString(
"Provider=SQLOLEDB.1;
Data Source=MyServer;
Catalog=MyDB;
Persist Security Info=False;
UID=MyUID;
PWD=MyPWD;"
)Create an alias in the client network utility and specify the port there.
This approach is better because if the port/server changes then you don't
have to change your code.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Michael" <anonymous@.discussions.microsoft.com> wrote in message
news:577801c3e502$311a2c40$a601280a@.phx.gbl...
quote:|||Thank you Carlos. I'll give it a shot.
> If SQL2K is not listening to the standard ports because
> 1433 has been changed to 14000, then what should the
> connectionstring in as ASP page look like so that it uses
> the correct port in order to make the connection?
> object.ConnectionString(
> "Provider=SQLOLEDB.1;
> Data Source=MyServer;
> Catalog=MyDB;
> Persist Security Info=False;
> UID=MyUID;
> PWD=MyPWD;"
> )
>
quote:
>--Original Message--
>Create an alias in the client network utility and specify
the port there.
quote:
>This approach is better because if the port/server
changes then you don't
quote:
>have to change your code.
>--
>Carlos E. Rojas
>SQL Server MVP
>Co-Author SQL Server 2000 programming by Example
>
>"Michael" <anonymous@.discussions.microsoft.com> wrote in
message
quote:
>news:577801c3e502$311a2c40$a601280a@.phx.gbl...
uses[QUOTE]
>
>.
>
No comments:
Post a Comment