Changing the IP address of a SQL 2000 SP3a server

What is the proper procedure for changing the IP address of a SQL 2000
Server?
Are there any gotchas, or is it as straight forward as just changing the
IP address?
Hi,
Rob Gordon
No procedures to follow to change the IP address. You can do straight away.
Nothing will happen.
"Rob Gordon" wrote:

> What is the proper procedure for changing the IP address of a SQL 2000
> Server?
> Are there any gotchas, or is it as straight forward as just changing the
> IP address?
>
|||Only impact will be if any clients/programs, etc. find it via the IP address
instead of the server name.. or is that changing, also.
Regards,
Hank Arnold
"Rob Gordon" <Robert.Gordon@.nospam.yosemitetech.com> wrote in message
news:ufFgHjCBFHA.3824@.TK2MSFTNGP10.phx.gbl...
> What is the proper procedure for changing the IP address of a SQL 2000
> Server?
> Are there any gotchas, or is it as straight forward as just changing the
> IP address?
|||You will need to stop/start the service after the address change. SQL binds
to whatever IP addresses exist at service startup time.
If you are running a cluster, that is an entirely different proposition.
You should repost the question in the .clustering newsgroup.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Rob Gordon" <Robert.Gordon@.nospam.yosemitetech.com> wrote in message
news:ufFgHjCBFHA.3824@.TK2MSFTNGP10.phx.gbl...
> What is the proper procedure for changing the IP address of a SQL 2000
> Server?
> Are there any gotchas, or is it as straight forward as just changing the
> IP address?
|||On Wed, 26 Jan 2005 20:26:03 -0800, Rob Gordon
<Robert.Gordon@.nospam.yosemitetech.com> wrote:

>What is the proper procedure for changing the IP address of a SQL 2000
>Server?
Change the IP.

>Are there any gotchas, or is it as straight forward as just changing the
>IP address?
Remember to update any DNS records you may need to, and if a client
connects via the IP address, it will need changing as well.
Jeff

Changing the IP address of a SQL 2000 SP3a server

What is the proper procedure for changing the IP address of a SQL 2000
Server?
Are there any gotchas, or is it as straight forward as just changing the
IP address?Hi,
Rob Gordon
No procedures to follow to change the IP address. You can do straight away.
Nothing will happen.
"Rob Gordon" wrote:

> What is the proper procedure for changing the IP address of a SQL 2000
> Server?
> Are there any gotchas, or is it as straight forward as just changing the
> IP address?
>|||Only impact will be if any clients/programs, etc. find it via the IP address
instead of the server name.. or is that changing, also.
--
Regards,
Hank Arnold
"Rob Gordon" <Robert.Gordon@.nospam.yosemitetech.com> wrote in message
news:ufFgHjCBFHA.3824@.TK2MSFTNGP10.phx.gbl...
> What is the proper procedure for changing the IP address of a SQL 2000
> Server?
> Are there any gotchas, or is it as straight forward as just changing the
> IP address?|||You will need to stop/start the service after the address change. SQL binds
to whatever IP addresses exist at service startup time.
If you are running a cluster, that is an entirely different proposition.
You should repost the question in the .clustering newsgroup.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Rob Gordon" <Robert.Gordon@.nospam.yosemitetech.com> wrote in message
news:ufFgHjCBFHA.3824@.TK2MSFTNGP10.phx.gbl...
> What is the proper procedure for changing the IP address of a SQL 2000
> Server?
> Are there any gotchas, or is it as straight forward as just changing the
> IP address?|||On Wed, 26 Jan 2005 20:26:03 -0800, Rob Gordon
<Robert.Gordon@.nospam.yosemitetech.com> wrote:

>What is the proper procedure for changing the IP address of a SQL 2000
>Server?
Change the IP.

>Are there any gotchas, or is it as straight forward as just changing the
>IP address?
Remember to update any DNS records you may need to, and if a client
connects via the IP address, it will need changing as well.
Jeff

Changing the IP address of a SQL 2000 SP3a server

What is the proper procedure for changing the IP address of a SQL 2000
Server?
Are there any gotchas, or is it as straight forward as just changing the
IP address?Hi,
Rob Gordon
No procedures to follow to change the IP address. You can do straight away.
Nothing will happen.
"Rob Gordon" wrote:
> What is the proper procedure for changing the IP address of a SQL 2000
> Server?
> Are there any gotchas, or is it as straight forward as just changing the
> IP address?
>|||Only impact will be if any clients/programs, etc. find it via the IP address
instead of the server name.. or is that changing, also.
--
Regards,
Hank Arnold
"Rob Gordon" <Robert.Gordon@.nospam.yosemitetech.com> wrote in message
news:ufFgHjCBFHA.3824@.TK2MSFTNGP10.phx.gbl...
> What is the proper procedure for changing the IP address of a SQL 2000
> Server?
> Are there any gotchas, or is it as straight forward as just changing the
> IP address?|||You will need to stop/start the service after the address change. SQL binds
to whatever IP addresses exist at service startup time.
If you are running a cluster, that is an entirely different proposition.
You should repost the question in the .clustering newsgroup.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Rob Gordon" <Robert.Gordon@.nospam.yosemitetech.com> wrote in message
news:ufFgHjCBFHA.3824@.TK2MSFTNGP10.phx.gbl...
> What is the proper procedure for changing the IP address of a SQL 2000
> Server?
> Are there any gotchas, or is it as straight forward as just changing the
> IP address?|||On Wed, 26 Jan 2005 20:26:03 -0800, Rob Gordon
<Robert.Gordon@.nospam.yosemitetech.com> wrote:
>What is the proper procedure for changing the IP address of a SQL 2000
>Server?
Change the IP. :)
>Are there any gotchas, or is it as straight forward as just changing the
>IP address?
Remember to update any DNS records you may need to, and if a client
connects via the IP address, it will need changing as well.
Jeff

Changing SQL2K port no. on Windows 2003

Hi,
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
AyadThey dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Changing SQL2K port no. on Windows 2003

Hi,
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
Ayad
They dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Changing SQL authentication method

Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:

>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary

Changing SQL authentication method

Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi chaps
Thanks for the advice - thought as much, I'll give it a
whirl.
Gary|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary

Changing SQL authentication method

Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanks
On Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:

>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks
|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary

Changing sa password

Hi All,
I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
data bases on this server & the authentication type is mixed. I would like to
know what are the implications if I change the sa password. Also would like
to know what all the precautions to be taken to do so.
With Regards,
Ovin
Have a look at sp_password?
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would
like
> to know what all the precautions to be taken to do so.
> With Regards,
>
|||Hi,
There is no implications in changing the SA password. THe only thing is
check in your application for any hard coded password for sa.
If it is not there then you could change the password for SA.
Note: It is not recommended to use SA password from application. If used
create a new login with DB_owner prev. and access the application.
Thanks
Hari
SQL Server MVP
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
> 6
> data bases on this server & the authentication type is mixed. I would like
> to
> know what are the implications if I change the sa password. Also would
> like
> to know what all the precautions to be taken to do so.
> With Regards,
>
|||In SQL Server 6.5 and earlier, many tasks could only be down as the actual sa
and Windows Network Authenticated system administrators were actually mapped,
aliased, as the sa.
However, since SQL Server 7.0, the creation of the system roles removed this
rectriction. Any login, SQL Server Autenticate or Windows Authenticated, who
is also a member of the system_administrators system role will have the EXACT
same permissions as the sa account itself. The security issue here is that
EVERYONE knows that the sa account exists; thus, this is a huge security hole.
It is not only a good idea to reset this password but to do it often and
make it as complex as possible.
As far as the impact to the system is concerned, it should not as long as no
applications are using them. If you are the application developer, you
should know whether or not you are using this account and switch the
application's login to something else if it is. If you are but a lowly DBA,
you may not know, not have access, or be supporting ill-coded vendor
applications. Regardless, you can use the SQL Server Profiler and audit for
the sa account login. You will have to filter out legitamate system
operations that typically will use the sa account also. How long you run
this audit depends on the nature of the applications support but one work day
to a business week should be enough to identify those systems that may be
using this account.
If all else fails, you can extract out the encrypted password if you do not
already know it, and be prepared to reset the account's password to its
original if issues arise.
Sincerely,
Anthony Thomas
"Ovin Crasta" wrote:

> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>
|||You could run a Profiler trace to catch who logs in using the "sa" login and based on that determine
what you need to do. No-one should need to login as sa, but some (badly written) apps do, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>

Changing sa password

Hi All,
I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
data bases on this server & the authentication type is mixed. I would like to
know what are the implications if I change the sa password. Also would like
to know what all the precautions to be taken to do so.
With Regards,Ovin
Have a look at sp_password?
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would
like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||Hi,
There is no implications in changing the SA password. THe only thing is
check in your application for any hard coded password for sa.
If it is not there then you could change the password for SA.
Note: It is not recommended to use SA password from application. If used
create a new login with DB_owner prev. and access the application.
Thanks
Hari
SQL Server MVP
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
> 6
> data bases on this server & the authentication type is mixed. I would like
> to
> know what are the implications if I change the sa password. Also would
> like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||In SQL Server 6.5 and earlier, many tasks could only be down as the actual sa
and Windows Network Authenticated system administrators were actually mapped,
aliased, as the sa.
However, since SQL Server 7.0, the creation of the system roles removed this
rectriction. Any login, SQL Server Autenticate or Windows Authenticated, who
is also a member of the system_administrators system role will have the EXACT
same permissions as the sa account itself. The security issue here is that
EVERYONE knows that the sa account exists; thus, this is a huge security hole.
It is not only a good idea to reset this password but to do it often and
make it as complex as possible.
As far as the impact to the system is concerned, it should not as long as no
applications are using them. If you are the application developer, you
should know whether or not you are using this account and switch the
application's login to something else if it is. If you are but a lowly DBA,
you may not know, not have access, or be supporting ill-coded vendor
applications. Regardless, you can use the SQL Server Profiler and audit for
the sa account login. You will have to filter out legitamate system
operations that typically will use the sa account also. How long you run
this audit depends on the nature of the applications support but one work day
to a business week should be enough to identify those systems that may be
using this account.
If all else fails, you can extract out the encrypted password if you do not
already know it, and be prepared to reset the account's password to its
original if issues arise.
Sincerely,
Anthony Thomas
"Ovin Crasta" wrote:
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||You could run a Profiler trace to catch who logs in using the "sa" login and based on that determine
what you need to do. No-one should need to login as sa, but some (badly written) apps do, though...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>

Changing sa password

Hi All,
I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
data bases on this server & the authentication type is mixed. I would like t
o
know what are the implications if I change the sa password. Also would like
to know what all the precautions to be taken to do so.
With Regards,Ovin
Have a look at sp_password?
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would
like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||Hi,
There is no implications in changing the SA password. THe only thing is
check in your application for any hard coded password for sa.
If it is not there then you could change the password for SA.
Note: It is not recommended to use SA password from application. If used
create a new login with DB_owner prev. and access the application.
Thanks
Hari
SQL Server MVP
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
> 6
> data bases on this server & the authentication type is mixed. I would like
> to
> know what are the implications if I change the sa password. Also would
> like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||In SQL Server 6.5 and earlier, many tasks could only be down as the actual s
a
and Windows Network Authenticated system administrators were actually mapped
,
aliased, as the sa.
However, since SQL Server 7.0, the creation of the system roles removed this
rectriction. Any login, SQL Server Autenticate or Windows Authenticated, wh
o
is also a member of the system_administrators system role will have the EXAC
T
same permissions as the sa account itself. The security issue here is that
EVERYONE knows that the sa account exists; thus, this is a huge security hol
e.
It is not only a good idea to reset this password but to do it often and
make it as complex as possible.
As far as the impact to the system is concerned, it should not as long as no
applications are using them. If you are the application developer, you
should know whether or not you are using this account and switch the
application's login to something else if it is. If you are but a lowly DBA,
you may not know, not have access, or be supporting ill-coded vendor
applications. Regardless, you can use the SQL Server Profiler and audit for
the sa account login. You will have to filter out legitamate system
operations that typically will use the sa account also. How long you run
this audit depends on the nature of the applications support but one work da
y
to a business week should be enough to identify those systems that may be
using this account.
If all else fails, you can extract out the encrypted password if you do not
already know it, and be prepared to reset the account's password to its
original if issues arise.
Sincerely,
Anthony Thomas
"Ovin Crasta" wrote:

> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would lik
e
> to know what all the precautions to be taken to do so.
> With Regards,
>|||You could run a Profiler trace to catch who logs in using the "sa" login and
based on that determine
what you need to do. No-one should need to login as sa, but some (badly writ
ten) apps do, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would lik
e
> to know what all the precautions to be taken to do so.
> With Regards,
>

Changing database compatibility from 70 to 80

Hi all. I wanted to know if a database running on SQL Server 2000 SP3a
with a database compatibility level of 70 can be changed to 80 without
any problems. This is a database that was originally built with SQL
Server 7.0. I'm assuming that over time as the DB itself was moved to
SQL Server 2000, the compatibility level was never upgraded.
The reason that I want to change the compatibility level from 70 to 80
is because I need to use the LIKE statement in a table query. It turns
out the LIKE statement uses COLLATE behind the scenes, which is
specific to 80.
Based on what I've read in the SQL Server Books Online, it seems that I
should be able to change this without any problems. I wanted to see
what others think from personal experience (if possible) before I went
and did this.
Any help is greatly appreciated!I've seen many troubles on untidy applications and JDBC apps with regard to
this. Check this KB, just in case. Sorry if redundant:
http://support.microsoft.com/default.aspx?scid=kb;en-us;271566
Cheers
AD
"Don Kitchen" <donkitchen@.gmail.com> wrote in message
news:1110230850.065960.319130@.g14g2000cwa.googlegroups.com...
> Hi all. I wanted to know if a database running on SQL Server 2000 SP3a
> with a database compatibility level of 70 can be changed to 80 without
> any problems. This is a database that was originally built with SQL
> Server 7.0. I'm assuming that over time as the DB itself was moved to
> SQL Server 2000, the compatibility level was never upgraded.
> The reason that I want to change the compatibility level from 70 to 80
> is because I need to use the LIKE statement in a table query. It turns
> out the LIKE statement uses COLLATE behind the scenes, which is
> specific to 80.
> Based on what I've read in the SQL Server Books Online, it seems that I
> should be able to change this without any problems. I wanted to see
> what others think from personal experience (if possible) before I went
> and did this.
> Any help is greatly appreciated!
>