changing connection string from one sql server to another using vb .net

I have developed numerous reports in a vb .net app (Windows Database App)
that is
soon to go into production. When I built each report, CR connected to sql
server on my development platform. The connection string is different than
it will be at my client.
How can I change the connection string so that it recognizes my client's
server instead of mine for each of these reports? This is not technically a
sql server question, but I am hoping some of the sql developers who review
these posts will have run into the same issue,
Thanks for any help.
Bernie YaegerConnection String data is generally stored in a centralized location...
1) config File
2) Registry
3) INI
4) Global.ASAX
hope this helps
Greg J
PDX, Oregon

changing connection string from one sql server to another using vb .net

I have developed numerous reports in a vb .net app (Windows Database App)
that is
soon to go into production. When I built each report, CR connected to sql
server on my development platform. The connection string is different than
it will be at my client.
How can I change the connection string so that it recognizes my client's
server instead of mine for each of these reports? This is not technically a
sql server question, but I am hoping some of the sql developers who review
these posts will have run into the same issue,
Thanks for any help.
Bernie YaegerConnection String data is generally stored in a centralized location...
1) config File
2) Registry
3) INI
4) Global.ASAX
hope this helps
Greg J
PDX, Oregon

Changing Computer Name

Here's my situation. We have a production SQL server 2000 with about 18
different databases running on it. The lease is up on the server and now i
must roll everything over to the new server. What i need to do is join the
domain with the new server using a different ip address and name than the
current SQL server, get everything installed, test it, then take both servers
down, rename the new server and change it's ip address to what the old one
was, and put it into production. Does anyone know how painful this will be
and what obstacles i need to look out for? Also, if there's a step by step
guide somewhere that'd be pretty great too. The old server has windows 2000
on it, the new server will have windows 2003. Thanks.
See answer to "Moving SQL Server"
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:F61F754D-1967-4A67-BACE-136759C158D6@.microsoft.com...
> Here's my situation. We have a production SQL server 2000 with about 18
> different databases running on it. The lease is up on the server and now
i
> must roll everything over to the new server. What i need to do is join
the
> domain with the new server using a different ip address and name than the
> current SQL server, get everything installed, test it, then take both
servers
> down, rename the new server and change it's ip address to what the old one
> was, and put it into production. Does anyone know how painful this will
be
> and what obstacles i need to look out for? Also, if there's a step by
step
> guide somewhere that'd be pretty great too. The old server has windows
2000
> on it, the new server will have windows 2003. Thanks.
|||Double Post. Answered in "Moving SQL Server".
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:F61F754D-1967-4A67-BACE-136759C158D6@.microsoft.com...
> Here's my situation. We have a production SQL server 2000 with about 18
> different databases running on it. The lease is up on the server and now
i
> must roll everything over to the new server. What i need to do is join
the
> domain with the new server using a different ip address and name than the
> current SQL server, get everything installed, test it, then take both
servers
> down, rename the new server and change it's ip address to what the old one
> was, and put it into production. Does anyone know how painful this will
be
> and what obstacles i need to look out for? Also, if there's a step by
step
> guide somewhere that'd be pretty great too. The old server has windows
2000
> on it, the new server will have windows 2003. Thanks.
|||"get everything installed"
Install SQL Server, service packs, restore the databases...
"test it"
How are you going to test it? Can you just leave the new server name in
place and change the connection string to connect to the new computer? I
suppose not, or you would not have the question. Anyway, this is the
easiest option.
"rename the new server"
When the box is restarted SQL Server will display an error message on start.
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
If you have jobs defined on your server you might have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:F61F754D-1967-4A67-BACE-136759C158D6@.microsoft.com...
> Here's my situation. We have a production SQL server 2000 with about 18
> different databases running on it. The lease is up on the server and now
i
> must roll everything over to the new server. What i need to do is join
the
> domain with the new server using a different ip address and name than the
> current SQL server, get everything installed, test it, then take both
servers
> down, rename the new server and change it's ip address to what the old one
> was, and put it into production. Does anyone know how painful this will
be
> and what obstacles i need to look out for? Also, if there's a step by
step
> guide somewhere that'd be pretty great too. The old server has windows
2000
> on it, the new server will have windows 2003. Thanks.

Changing Computer Name

Here's my situation. We have a production SQL server 2000 with about 18
different databases running on it. The lease is up on the server and now i
must roll everything over to the new server. What i need to do is join the
domain with the new server using a different ip address and name than the
current SQL server, get everything installed, test it, then take both server
s
down, rename the new server and change it's ip address to what the old one
was, and put it into production. Does anyone know how painful this will be
and what obstacles i need to look out for? Also, if there's a step by step
guide somewhere that'd be pretty great too. The old server has windows 2000
on it, the new server will have windows 2003. Thanks.See answer to "Moving SQL Server"
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:F61F754D-1967-4A67-BACE-136759C158D6@.microsoft.com...
> Here's my situation. We have a production SQL server 2000 with about 18
> different databases running on it. The lease is up on the server and now
i
> must roll everything over to the new server. What i need to do is join
the
> domain with the new server using a different ip address and name than the
> current SQL server, get everything installed, test it, then take both
servers
> down, rename the new server and change it's ip address to what the old one
> was, and put it into production. Does anyone know how painful this will
be
> and what obstacles i need to look out for? Also, if there's a step by
step
> guide somewhere that'd be pretty great too. The old server has windows
2000
> on it, the new server will have windows 2003. Thanks.|||Double Post. Answered in "Moving SQL Server".
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:F61F754D-1967-4A67-BACE-136759C158D6@.microsoft.com...
> Here's my situation. We have a production SQL server 2000 with about 18
> different databases running on it. The lease is up on the server and now
i
> must roll everything over to the new server. What i need to do is join
the
> domain with the new server using a different ip address and name than the
> current SQL server, get everything installed, test it, then take both
servers
> down, rename the new server and change it's ip address to what the old one
> was, and put it into production. Does anyone know how painful this will
be
> and what obstacles i need to look out for? Also, if there's a step by
step
> guide somewhere that'd be pretty great too. The old server has windows
2000
> on it, the new server will have windows 2003. Thanks.|||"get everything installed"
Install SQL Server, service packs, restore the databases...
"test it"
How are you going to test it? Can you just leave the new server name in
place and change the connection string to connect to the new computer? I
suppose not, or you would not have the question. Anyway, this is the
easiest option.
"rename the new server"
When the box is restarted SQL Server will display an error message on start.
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
If you have jobs defined on your server you might have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
Keith
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:F61F754D-1967-4A67-BACE-136759C158D6@.microsoft.com...
> Here's my situation. We have a production SQL server 2000 with about 18
> different databases running on it. The lease is up on the server and now
i
> must roll everything over to the new server. What i need to do is join
the
> domain with the new server using a different ip address and name than the
> current SQL server, get everything installed, test it, then take both
servers
> down, rename the new server and change it's ip address to what the old one
> was, and put it into production. Does anyone know how painful this will
be
> and what obstacles i need to look out for? Also, if there's a step by
step
> guide somewhere that'd be pretty great too. The old server has windows
2000
> on it, the new server will have windows 2003. Thanks.

Changing Computer Name

Here's my situation. We have a production SQL server 2000 with about 18
different databases running on it. The lease is up on the server and now i
must roll everything over to the new server. What i need to do is join the
domain with the new server using a different ip address and name than the
current SQL server, get everything installed, test it, then take both servers
down, rename the new server and change it's ip address to what the old one
was, and put it into production. Does anyone know how painful this will be
and what obstacles i need to look out for? Also, if there's a step by step
guide somewhere that'd be pretty great too. The old server has windows 2000
on it, the new server will have windows 2003. Thanks.See answer to "Moving SQL Server"
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:F61F754D-1967-4A67-BACE-136759C158D6@.microsoft.com...
> Here's my situation. We have a production SQL server 2000 with about 18
> different databases running on it. The lease is up on the server and now
i
> must roll everything over to the new server. What i need to do is join
the
> domain with the new server using a different ip address and name than the
> current SQL server, get everything installed, test it, then take both
servers
> down, rename the new server and change it's ip address to what the old one
> was, and put it into production. Does anyone know how painful this will
be
> and what obstacles i need to look out for? Also, if there's a step by
step
> guide somewhere that'd be pretty great too. The old server has windows
2000
> on it, the new server will have windows 2003. Thanks.|||Double Post. Answered in "Moving SQL Server".
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:F61F754D-1967-4A67-BACE-136759C158D6@.microsoft.com...
> Here's my situation. We have a production SQL server 2000 with about 18
> different databases running on it. The lease is up on the server and now
i
> must roll everything over to the new server. What i need to do is join
the
> domain with the new server using a different ip address and name than the
> current SQL server, get everything installed, test it, then take both
servers
> down, rename the new server and change it's ip address to what the old one
> was, and put it into production. Does anyone know how painful this will
be
> and what obstacles i need to look out for? Also, if there's a step by
step
> guide somewhere that'd be pretty great too. The old server has windows
2000
> on it, the new server will have windows 2003. Thanks.|||"get everything installed"
Install SQL Server, service packs, restore the databases...
"test it"
How are you going to test it? Can you just leave the new server name in
place and change the connection string to connect to the new computer? I
suppose not, or you would not have the question. Anyway, this is the
easiest option.
"rename the new server"
When the box is restarted SQL Server will display an error message on start.
You will have to pop in the SQL Server CD and choose install. This step
will not actually install SQL Server...it will just fix up some registry
entries.
If you have jobs defined on your server you might have to update the value
as stored within the originating_server column.
SELECT originating_server FROM msdb..sysjobs
If @.@.servername is incorrect you will have to drop and add server using the
stored procedures listed below:
sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName', 'local'
--
Keith
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:F61F754D-1967-4A67-BACE-136759C158D6@.microsoft.com...
> Here's my situation. We have a production SQL server 2000 with about 18
> different databases running on it. The lease is up on the server and now
i
> must roll everything over to the new server. What i need to do is join
the
> domain with the new server using a different ip address and name than the
> current SQL server, get everything installed, test it, then take both
servers
> down, rename the new server and change it's ip address to what the old one
> was, and put it into production. Does anyone know how painful this will
be
> and what obstacles i need to look out for? Also, if there's a step by
step
> guide somewhere that'd be pretty great too. The old server has windows
2000
> on it, the new server will have windows 2003. Thanks.

change tracking for SQL Server

Has anyone come across a change tracking tool for SQL Server. Specifically
the scenario I want is the following :

A Production DB needs some modifications to its content.
This tool will copy the DB to a dev environment.
The Dev environment will be 2 copies of the DB, 1 as a control set and the
other the change DB.
The developer makes their changes in the Change DB. They test them out and
then when they decide the changes are ready to pushto production they hit
the "go" button on the tool.
The tool calculates the delta between the Control and the Change DB and then
pushes the changes to produciton

Any ideas

Thanks

s"Steve Mew" <steve_mew@.hotmail.com> wrote in message news:<wWnib.8720$843.5779@.nwrddc03.gnilink.net>...
> Has anyone come across a change tracking tool for SQL Server. Specifically
> the scenario I want is the following :
> A Production DB needs some modifications to its content.
> This tool will copy the DB to a dev environment.
> The Dev environment will be 2 copies of the DB, 1 as a control set and the
> other the change DB.
> The developer makes their changes in the Change DB. They test them out and
> then when they decide the changes are ready to pushto production they hit
> the "go" button on the tool.
> The tool calculates the delta between the Control and the Change DB and then
> pushes the changes to produciton
> Any ideas
> Thanks
> s

I'm not aware of a single tool that would do exactly what you want,
however you could start by looking at the Red Gate SQL tools
(http://www.red-gate.com), which can compare two databases and
generate scripts to synchronize them. There are similar tools from
other vendors.

Copying the databases is easily automated (backup/restore, SQLDMO,
DTS), but you might want to consider the permissions involved. Many
sites do not allow developers to backup/restore databases or push code
directly to production (although to be fair, there are certainly many
that do).

Simon|||Steve Mew (steve_mew@.hotmail.com) writes:
> Has anyone come across a change tracking tool for SQL Server. Specifically
> the scenario I want is the following :
> A Production DB needs some modifications to its content.
> This tool will copy the DB to a dev environment.
> The Dev environment will be 2 copies of the DB, 1 as a control set and the
> other the change DB.
> The developer makes their changes in the Change DB. They test them out and
> then when they decide the changes are ready to pushto production they hit
> the "go" button on the tool.
> The tool calculates the delta between the Control and the Change DB and
> then pushes the changes to produciton

For the scenario you describe it sounds like SQL Compare from Red Gate
is the tool to use. However, I have never used this tool myself.

I cannot escape to take the occassion to point out that the best strategy
would be have all your source in a version control system, and then have
controlled procedures from building update scrtips from the version-
control system.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

change the look of Report Manager

I would like to change the look of the Report Manager. I have Reporting
Services on both developement and production servers. I would like to
be able to change the color or font etc. so that I can tell without
having to look in the address box to figure out what server I am on.
Is there a value I can change somewhere that will do this for me?Hi Lou,
you could just edit the style sheet
\Reporting Services\ReportManager\Styles\ReportingServices.css
regards
Matt
"Lou" <lbonnes@.yahoo.com> wrote in message
news:1105847715.370619.296730@.f14g2000cwb.googlegroups.com...
> I would like to change the look of the Report Manager. I have Reporting
> Services on both developement and production servers. I would like to
> be able to change the color or font etc. so that I can tell without
> having to look in the address box to figure out what server I am on.
> Is there a value I can change somewhere that will do this for me?
>

Change SA Password

Been asking about changing the SA password, and still have another question.
I have confirmed that our production database is not using SA for anything.
I need to change the SA password.
After I change the SA password, do I need to restart SQL? or any services to
verify that SQL is going to work after the password change?
TIA
RandyH wrote:
> Been asking about changing the SA password, and still have another
> question.
> I have confirmed that our production database is not using SA for anything.
> I need to change the SA password.
> After I change the SA password, do I need to restart SQL? or any
No

> services to verify that SQL is going to work after the password change?
Unless the SQL Agent uses sa (not the best idea anyway,) no.
|||Thank you, just making sure I don't break anything before I do this.
"Yura Shalak" <yuras@.nospam.nospam> wrote in message
news:ublBITRqHHA.3372@.TK2MSFTNGP03.phx.gbl...
> RandyH wrote:
> No
>
> Unless the SQL Agent uses sa (not the best idea anyway,) no.
|||Thank you, just making sure I don't break anything before I do this.
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:%23%23F5eTRqHHA.484@.TK2MSFTNGP06.phx.gbl...
> Hi
> to change the sa password
> use sp_password or you can do it through EM
> After I change the SA password, do I need to restart SQL? or any services
> to
> verify that SQL is going to work after the password change?
> NO
>
> Regards
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "RandyH" <RHollaw@.HOTmail.com> wrote in message
> news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
>
|||No need to restart sql server. Since SA username is not used internally by
SQL Server for any thing there is no need to verify anything. But
make sure that all the applications connecting to sql server which used the
SA user name and password needs to be updated and tested.
Thanks
Hari
"RandyH" <RHollaw@.HOTmail.com> wrote in message
news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
> Been asking about changing the SA password, and still have another
> question.
> I have confirmed that our production database is not using SA for
> anything.
> I need to change the SA password.
> After I change the SA password, do I need to restart SQL? or any services
> to verify that SQL is going to work after the password change?
> TIA
|||Thanks Hari!
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OYPhu2WqHHA.3356@.TK2MSFTNGP03.phx.gbl...
> No need to restart sql server. Since SA username is not used internally by
> SQL Server for any thing there is no need to verify anything. But
> make sure that all the applications connecting to sql server which used
> the SA user name and password needs to be updated and tested.
> Thanks
> Hari
> "RandyH" <RHollaw@.HOTmail.com> wrote in message
> news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
>

Change SA Password

Been asking about changing the SA password, and still have another question.
I have confirmed that our production database is not using SA for anything.
I need to change the SA password.
After I change the SA password, do I need to restart SQL? or any services to
verify that SQL is going to work after the password change?
TIARandyH wrote:
> Been asking about changing the SA password, and still have another
> question.
> I have confirmed that our production database is not using SA for anything
.
> I need to change the SA password.
> After I change the SA password, do I need to restart SQL? or any
No

> services to verify that SQL is going to work after the password change?
Unless the SQL Agent uses sa (not the best idea anyway,) no.|||Hi
to change the sa password
use sp_password or you can do it through EM
After I change the SA password, do I need to restart SQL? or any services to
verify that SQL is going to work after the password change?
NO
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"RandyH" <RHollaw@.HOTmail.com> wrote in message
news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
> Been asking about changing the SA password, and still have another
> question.
> I have confirmed that our production database is not using SA for
> anything.
> I need to change the SA password.
> After I change the SA password, do I need to restart SQL? or any services
> to verify that SQL is going to work after the password change?
> TIA|||Thank you, just making sure I don't break anything before I do this.
"Yura Shalak" <yuras@.nospam.nospam> wrote in message
news:ublBITRqHHA.3372@.TK2MSFTNGP03.phx.gbl...
> RandyH wrote:
> No
>
> Unless the SQL Agent uses sa (not the best idea anyway,) no.|||Thank you, just making sure I don't break anything before I do this.
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:%23%23F5eTRqHHA.484@.TK2MSFTNGP06.phx.gbl...
> Hi
> to change the sa password
> use sp_password or you can do it through EM
> After I change the SA password, do I need to restart SQL? or any services
> to
> verify that SQL is going to work after the password change?
> NO
>
> Regards
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "RandyH" <RHollaw@.HOTmail.com> wrote in message
> news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
>|||No need to restart sql server. Since SA username is not used internally by
SQL Server for any thing there is no need to verify anything. But
make sure that all the applications connecting to sql server which used the
SA user name and password needs to be updated and tested.
Thanks
Hari
"RandyH" <RHollaw@.HOTmail.com> wrote in message
news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
> Been asking about changing the SA password, and still have another
> question.
> I have confirmed that our production database is not using SA for
> anything.
> I need to change the SA password.
> After I change the SA password, do I need to restart SQL? or any services
> to verify that SQL is going to work after the password change?
> TIA|||Thanks Hari!
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OYPhu2WqHHA.3356@.TK2MSFTNGP03.phx.gbl...
> No need to restart sql server. Since SA username is not used internally by
> SQL Server for any thing there is no need to verify anything. But
> make sure that all the applications connecting to sql server which used
> the SA user name and password needs to be updated and tested.
> Thanks
> Hari
> "RandyH" <RHollaw@.HOTmail.com> wrote in message
> news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
>

Change SA Password

Been asking about changing the SA password, and still have another question.
I have confirmed that our production database is not using SA for anything.
I need to change the SA password.
After I change the SA password, do I need to restart SQL? or any services to
verify that SQL is going to work after the password change?
TIARandyH wrote:
> Been asking about changing the SA password, and still have another
> question.
> I have confirmed that our production database is not using SA for anything.
> I need to change the SA password.
> After I change the SA password, do I need to restart SQL? or any
No
> services to verify that SQL is going to work after the password change?
Unless the SQL Agent uses sa (not the best idea anyway,) no.|||Hi
to change the sa password
use sp_password or you can do it through EM
After I change the SA password, do I need to restart SQL? or any services to
verify that SQL is going to work after the password change?
NO
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"RandyH" <RHollaw@.HOTmail.com> wrote in message
news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
> Been asking about changing the SA password, and still have another
> question.
> I have confirmed that our production database is not using SA for
> anything.
> I need to change the SA password.
> After I change the SA password, do I need to restart SQL? or any services
> to verify that SQL is going to work after the password change?
> TIA|||Thank you, just making sure I don't break anything before I do this.
"Yura Shalak" <yuras@.nospam.nospam> wrote in message
news:ublBITRqHHA.3372@.TK2MSFTNGP03.phx.gbl...
> RandyH wrote:
>> Been asking about changing the SA password, and still have another
>> question.
>> I have confirmed that our production database is not using SA for
>> anything.
>> I need to change the SA password.
>> After I change the SA password, do I need to restart SQL? or any
> No
>> services to verify that SQL is going to work after the password change?
> Unless the SQL Agent uses sa (not the best idea anyway,) no.|||Thank you, just making sure I don't break anything before I do this.
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:%23%23F5eTRqHHA.484@.TK2MSFTNGP06.phx.gbl...
> Hi
> to change the sa password
> use sp_password or you can do it through EM
> After I change the SA password, do I need to restart SQL? or any services
> to
> verify that SQL is going to work after the password change?
> NO
>
> Regards
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "RandyH" <RHollaw@.HOTmail.com> wrote in message
> news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
>> Been asking about changing the SA password, and still have another
>> question.
>> I have confirmed that our production database is not using SA for
>> anything.
>> I need to change the SA password.
>> After I change the SA password, do I need to restart SQL? or any services
>> to verify that SQL is going to work after the password change?
>> TIA
>|||No need to restart sql server. Since SA username is not used internally by
SQL Server for any thing there is no need to verify anything. But
make sure that all the applications connecting to sql server which used the
SA user name and password needs to be updated and tested.
Thanks
Hari
"RandyH" <RHollaw@.HOTmail.com> wrote in message
news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
> Been asking about changing the SA password, and still have another
> question.
> I have confirmed that our production database is not using SA for
> anything.
> I need to change the SA password.
> After I change the SA password, do I need to restart SQL? or any services
> to verify that SQL is going to work after the password change?
> TIA|||Thanks Hari!
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OYPhu2WqHHA.3356@.TK2MSFTNGP03.phx.gbl...
> No need to restart sql server. Since SA username is not used internally by
> SQL Server for any thing there is no need to verify anything. But
> make sure that all the applications connecting to sql server which used
> the SA user name and password needs to be updated and tested.
> Thanks
> Hari
> "RandyH" <RHollaw@.HOTmail.com> wrote in message
> news:FA60C602-ABF6-4503-AB48-8BCF64CF4CC3@.microsoft.com...
>> Been asking about changing the SA password, and still have another
>> question.
>> I have confirmed that our production database is not using SA for
>> anything.
>> I need to change the SA password.
>> After I change the SA password, do I need to restart SQL? or any services
>> to verify that SQL is going to work after the password change?
>> TIA
>