Hi.
Are there limits in SQL Server on how you can change the metadata when users
are connected? I know that with some other platforms it is not possible to
create/drop foreign keys without exclusive access (for instance our current
platform Interbase 6.0.2, which we are finding very frustrating). Does SQL
Server 2000 suffer from similar limitations? Or does the number of
connected users make no difference? This is a pivotal issue for us on
deciding our upgrade strategy.
MikeSQL Server 2000 does not have any such limitations. There are some commands
that can hamper performance when run during high-user activity. Other than
that, adding constraints, indexes etc will not pose a problem. You will
of-course need to have relevant permissions to run the commands themselves.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"Mike" <noone@.hotmail.com> wrote in message
news:eSFHst%23rDHA.2148@.TK2MSFTNGP12.phx.gbl...
> Hi.
> Are there limits in SQL Server on how you can change the metadata when
users
> are connected? I know that with some other platforms it is not possible
to
> create/drop foreign keys without exclusive access (for instance our
current
> platform Interbase 6.0.2, which we are finding very frustrating). Does
SQL
> Server 2000 suffer from similar limitations? Or does the number of
> connected users make no difference? This is a pivotal issue for us on
> deciding our upgrade strategy.
> Mike
>
Showing posts with label connected. Show all posts
Showing posts with label connected. Show all posts
Saturday, February 25, 2012
Tuesday, February 14, 2012
Changing default listening port
Hi,
I need to change the default listening port on sql server from 1433 to
another port. The server is being connected to by multiple web sites some
using DSN connections and others not and also via a number of connections
using Enterprise Manager. I'm worried that if I change the port, the
websites will not be able to connect. Can anyone give me some advice on what
will need to be changed to make this update smooth.
Many thanks,
Luke.You can create an alias on the client using "Client Network Utility" and there specify the port
number. Or, you can specify the port number in the server name/connection string. From memory, you
do like SERVERNAME;portnumber, I.e.:
MYSERVER;1067
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Luke Fields" <lfields228@.hotmaik.com> wrote in message
news:egS7UeluDHA.2520@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I need to change the default listening port on sql server from 1433 to
> another port. The server is being connected to by multiple web sites some
> using DSN connections and others not and also via a number of connections
> using Enterprise Manager. I'm worried that if I change the port, the
> websites will not be able to connect. Can anyone give me some advice on what
> will need to be changed to make this update smooth.
> Many thanks,
> Luke.
>|||You can change the port SQL Server is listening on use the Server Network
Utility in the SQL Server program group. If there are firewalls between the
server and the clients you will need to open the new port on the firewall
so the traffic can get through.
Also if you are using dynamic discovery of the SQL Server on the network
UDP port 1434 will need to be opened as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I need to change the default listening port on sql server from 1433 to
another port. The server is being connected to by multiple web sites some
using DSN connections and others not and also via a number of connections
using Enterprise Manager. I'm worried that if I change the port, the
websites will not be able to connect. Can anyone give me some advice on what
will need to be changed to make this update smooth.
Many thanks,
Luke.You can create an alias on the client using "Client Network Utility" and there specify the port
number. Or, you can specify the port number in the server name/connection string. From memory, you
do like SERVERNAME;portnumber, I.e.:
MYSERVER;1067
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Luke Fields" <lfields228@.hotmaik.com> wrote in message
news:egS7UeluDHA.2520@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I need to change the default listening port on sql server from 1433 to
> another port. The server is being connected to by multiple web sites some
> using DSN connections and others not and also via a number of connections
> using Enterprise Manager. I'm worried that if I change the port, the
> websites will not be able to connect. Can anyone give me some advice on what
> will need to be changed to make this update smooth.
> Many thanks,
> Luke.
>|||You can change the port SQL Server is listening on use the Server Network
Utility in the SQL Server program group. If there are firewalls between the
server and the clients you will need to open the new port on the firewall
so the traffic can get through.
Also if you are using dynamic discovery of the SQL Server on the network
UDP port 1434 will need to be opened as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Changing default listening port
Hi,
I need to change the default listening port on sql server from 1433 to
another port. The server is being connected to by multiple web sites some
using DSN connections and others not and also via a number of connections
using Enterprise Manager. I'm worried that if I change the port, the
websites will not be able to connect. Can anyone give me some advice on what
will need to be changed to make this update smooth.
Many thanks,
Luke.You can create an alias on the client using "Client Network Utility" and the
re specify the port
number. Or, you can specify the port number in the server name/connection st
ring. From memory, you
do like SERVERNAME;portnumber, I.e.:
MYSERVER;1067
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Luke Fields" <lfields228@.hotmaik.com> wrote in message
news:egS7UeluDHA.2520@.TK2MSFTNGP10.phx.gbl...
I need to change the default listening port on sql server from 1433 to
another port. The server is being connected to by multiple web sites some
using DSN connections and others not and also via a number of connections
using Enterprise Manager. I'm worried that if I change the port, the
websites will not be able to connect. Can anyone give me some advice on what
will need to be changed to make this update smooth.
Many thanks,
Luke.You can create an alias on the client using "Client Network Utility" and the
re specify the port
number. Or, you can specify the port number in the server name/connection st
ring. From memory, you
do like SERVERNAME;portnumber, I.e.:
MYSERVER;1067
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Luke Fields" <lfields228@.hotmaik.com> wrote in message
news:egS7UeluDHA.2520@.TK2MSFTNGP10.phx.gbl...
quote:
> Hi,
> I need to change the default listening port on sql server from 1433 to
> another port. The server is being connected to by multiple web sites some
> using DSN connections and others not and also via a number of connections
> using Enterprise Manager. I'm worried that if I change the port, the
> websites will not be able to connect. Can anyone give me some advice on wh
at
> will need to be changed to make this update smooth.
> Many thanks,
> Luke.
>
Subscribe to:
Posts (Atom)