Changing the (local) SQL Server registration name

Hi,
When we install SQL server, it creates a (local) SQL
Server registration. How can we change this name from
(local) to computer's name?
Thank you.
You should be able to access the server via (local), servername or ..
If you are talking about enterprise manager then just delete the registration and add one with the servername.
Check @.@.server_name you may have to add it via sp_addserver.
"anonymous@.discussions.microsoft.com" wrote:

> Hi,
> When we install SQL server, it creates a (local) SQL
> Server registration. How can we change this name from
> (local) to computer's name?
> Thank you.
>
|||I tried deleting the (local) registration but it created
a lot of problem. After deleting the (local) registration
I wasn't able to add it back. SQLAgent service wasn't
showing up in the service list.

>--Original Message--
>You should be able to access the server via (local),
servername or ..
>If you are talking about enterprise manager then just
delete the registration and add one with the servername.
>Check @.@.server_name you may have to add it via
sp_addserver.
>"anonymous@.discussions.microsoft.com" wrote:
>.
>
|||?
Are you talking about enterprise manager?
It's just a client and deleting a registration won't affect services running on the m/c.
The agent service is separate from the server and may have not been started.
See if the mssqlserver service is running - if so you should be able to regidter in enterprise manager.
"anonymous@.discussions.microsoft.com" wrote:

> I tried deleting the (local) registration but it created
> a lot of problem. After deleting the (local) registration
> I wasn't able to add it back. SQLAgent service wasn't
> showing up in the service list.
>
> servername or ..
> delete the registration and add one with the servername.
> sp_addserver.
>

Changing the (local) SQL Server registration name

Hi,
When we install SQL server, it creates a (local) SQL
Server registration. How can we change this name from
(local) to computer's name?
Thank you.You should be able to access the server via (local), servername or ..
If you are talking about enterprise manager then just delete the registration and add one with the servername.
Check @.@.server_name you may have to add it via sp_addserver.
"anonymous@.discussions.microsoft.com" wrote:
> Hi,
> When we install SQL server, it creates a (local) SQL
> Server registration. How can we change this name from
> (local) to computer's name?
> Thank you.
>|||I tried deleting the (local) registration but it created
a lot of problem. After deleting the (local) registration
I wasn't able to add it back. SQLAgent service wasn't
showing up in the service list.
>--Original Message--
>You should be able to access the server via (local),
servername or ..
>If you are talking about enterprise manager then just
delete the registration and add one with the servername.
>Check @.@.server_name you may have to add it via
sp_addserver.
>"anonymous@.discussions.microsoft.com" wrote:
>> Hi,
>> When we install SQL server, it creates a (local) SQL
>> Server registration. How can we change this name from
>> (local) to computer's name?
>> Thank you.
>.
>|||?
Are you talking about enterprise manager?
It's just a client and deleting a registration won't affect services running on the m/c.
The agent service is separate from the server and may have not been started.
See if the mssqlserver service is running - if so you should be able to regidter in enterprise manager.
"anonymous@.discussions.microsoft.com" wrote:
> I tried deleting the (local) registration but it created
> a lot of problem. After deleting the (local) registration
> I wasn't able to add it back. SQLAgent service wasn't
> showing up in the service list.
>
> >--Original Message--
> >You should be able to access the server via (local),
> servername or ..
> >If you are talking about enterprise manager then just
> delete the registration and add one with the servername.
> >
> >Check @.@.server_name you may have to add it via
> sp_addserver.
> >
> >"anonymous@.discussions.microsoft.com" wrote:
> >
> >> Hi,
> >>
> >> When we install SQL server, it creates a (local) SQL
> >> Server registration. How can we change this name from
> >> (local) to computer's name?
> >>
> >> Thank you.
> >>
> >.
> >
>

Changing the (local) SQL Server registration name

Hi,
When we install SQL server, it creates a (local) SQL
Server registration. How can we change this name from
(local) to computer's name?
Thank you.You should be able to access the server via (local), servername or ..
If you are talking about enterprise manager then just delete the registratio
n and add one with the servername.
Check @.@.server_name you may have to add it via sp_addserver.
"anonymous@.discussions.microsoft.com" wrote:

> Hi,
> When we install SQL server, it creates a (local) SQL
> Server registration. How can we change this name from
> (local) to computer's name?
> Thank you.
>|||I tried deleting the (local) registration but it created
a lot of problem. After deleting the (local) registration
I wasn't able to add it back. SQLAgent service wasn't
showing up in the service list.

>--Original Message--
>You should be able to access the server via (local),
servername or ..
>If you are talking about enterprise manager then just
delete the registration and add one with the servername.
>Check @.@.server_name you may have to add it via
sp_addserver.
>"anonymous@.discussions.microsoft.com" wrote:
>
>.
>|||?
Are you talking about enterprise manager?
It's just a client and deleting a registration won't affect services running
on the m/c.
The agent service is separate from the server and may have not been started.
See if the mssqlserver service is running - if so you should be able to regi
dter in enterprise manager.
"anonymous@.discussions.microsoft.com" wrote:

> I tried deleting the (local) registration but it created
> a lot of problem. After deleting the (local) registration
> I wasn't able to add it back. SQLAgent service wasn't
> showing up in the service list.
>
> servername or ..
> delete the registration and add one with the servername.
> sp_addserver.
>sql

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 enterprise to sql standard edition.

Hi, now we have a server that is running in sql server2000 enterprise
edition. For licenses problems we need to desinstall this edition and
install the standard edition.
Do somebody know if there is a problem in attach the databases that were
created in the enterprise edition on the new standard edition server'
What do you recommend to me to do this migration?
Thanks a lot for your help!!!
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!You can attach databases from EE to SE (in fact, you can attach across all editions).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"MariaGuzman" <marisa@.devdex.com> wrote in message news:uet9BdaHFHA.3376@.TK2MSFTNGP14.phx.gbl...
> Hi, now we have a server that is running in sql server2000 enterprise
> edition. For licenses problems we need to desinstall this edition and
> install the standard edition.
> Do somebody know if there is a problem in attach the databases that were
> created in the enterprise edition on the new standard edition server'
> What do you recommend to me to do this migration?
> Thanks a lot for your help!!!
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||> You can attach databases from EE to SE (in fact, you can attach across all
editions).
Well, except a > 2GB database to MSDE... :-)|||Good point, Aaron. :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ejmYeIbHFHA.2456@.TK2MSFTNGP09.phx.gbl...
>> You can attach databases from EE to SE (in fact, you can attach across all
> editions).
> Well, except a > 2GB database to MSDE... :-)
>|||Functionaly, the database should be equivalent. Unless you were doing
esoteric Distributed Partitioned Views or some such, you should run into any
problems.
Take a look at the product features of both editions to see if any of these
match thing you've been doing.
Also consider that if you had purchased Developer Edition to build your
systems, you would have been using Enterprise Edition and it would have been
likely that many users have deployed such systems to production level
Standard Edition. The only difference between DE and EE is the EULA.
Sincerely,
Anthony Thomas
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uet9BdaHFHA.3376@.TK2MSFTNGP14.phx.gbl...
Hi, now we have a server that is running in sql server2000 enterprise
edition. For licenses problems we need to desinstall this edition and
install the standard edition.
Do somebody know if there is a problem in attach the databases that were
created in the enterprise edition on the new standard edition server'
What do you recommend to me to do this migration?
Thanks a lot for your help!!!
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Changing smtp and from values

During the install wizard prompts where presented for a
SMTP address and a FROM value. I want to change these
values now, How do I do this?Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config
Be sure to make a copy first :)
Bruce L-C
"Jim Abel" <jim.abel@.lmco.com> wrote in message
news:268801c47030$1efc9f70$a501280a@.phx.gbl...
> During the install wizard prompts where presented for a
> SMTP address and a FROM value. I want to change these
> values now, How do I do this?|||Edit the RSReportServer.config file found in %PROGRAMFILES%\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer\ folder:
<RSEmailDPConfiguration>
<SMTPServer></SMTPServer>
<SMTPServerPort></SMTPServerPort>
<SMTPAccountName></SMTPAccountName>
<SMTPConnectionTimeout></SMTPConnectionTimeout>
<SMTPServerPickupDirectory></SMTPServerPickupDirectory>
<SMTPUseSSL></SMTPUseSSL>
<SendUsing></SendUsing>
<SMTPAuthenticate></SMTPAuthenticate>
<From></From>
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jim Abel" <jim.abel@.lmco.com> wrote in message
news:268801c47030$1efc9f70$a501280a@.phx.gbl...
> During the install wizard prompts where presented for a
> SMTP address and a FROM value. I want to change these
> values now, How do I do this?

Changing port numbers

On an active/active cluster what is the proper way of changing the port # on
the named instance after an install is complete and in use.
Use the Server Network Utility to assign a new port number. The utility is
not cluster-aware so make the changes on all nodes in the cluster
individually. SQL server requires a service stop-start to change port
numbers.
Geoff N, Hiten
Microsoft SQL Server MVP
"zach_john" <zach_john@.discussions.microsoft.com> wrote in message
news:01F5E155-2002-4C8A-8549-80DA732C7B7F@.microsoft.com...
> On an active/active cluster what is the proper way of changing the port #
> on
> the named instance after an install is complete and in use.
|||Thanks Geoff - just wanted to hear that confirmation.
Cheers,
Zach
"Geoff N. Hiten" wrote:

> Use the Server Network Utility to assign a new port number. The utility is
> not cluster-aware so make the changes on all nodes in the cluster
> individually. SQL server requires a service stop-start to change port
> numbers.
> Geoff N, Hiten
> Microsoft SQL Server MVP
> "zach_john" <zach_john@.discussions.microsoft.com> wrote in message
> news:01F5E155-2002-4C8A-8549-80DA732C7B7F@.microsoft.com...
>
>
|||It's always easier to learn from someone else's mistakes.
GNH
"zach_john" <zach_john@.discussions.microsoft.com> wrote in message
news:9C40F75E-2E21-4026-9A34-CF4857CF78DD@.microsoft.com...[vbcol=seagreen]
> Thanks Geoff - just wanted to hear that confirmation.
> Cheers,
> Zach
> "Geoff N. Hiten" wrote:

Changing Machine Names MSDE

I have a local install of MSDE on my workstation. I have also defined a
linked server with another SQL Server on our network. I accepted all the
defaults when I installed MSDE and the server got named my machine name.
Everything is working great.

Our IT department now needs to change my machine name. What effect will
this have on my current SQL installation?

Help and suggestions appreciated.

Thanks,
Frank

*** Sent via Developersdex http://www.developersdex.com ***Frank Bishop (fbishop@.viper.com) writes:
> I have a local install of MSDE on my workstation. I have also defined a
> linked server with another SQL Server on our network. I accepted all the
> defaults when I installed MSDE and the server got named my machine name.
> Everything is working great.
> Our IT department now needs to change my machine name. What effect will
> this have on my current SQL installation?

If memory serves, the server name changes automatically. However,
@.@.servername usually gets messed up.

To this end to:

exec sp_dropserver 'oldname'
exec sp_addserver 'newname', 'local'

Then stop and restart SQL Server.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Changing directory where database files are stored

Hi

After install the mdf and log files are stored in the Program Files directory tree.

How do I change the place were they are stored to a path of my own choice, so that new DBs get created there too?

I've looked though the docs, but I can't find this.

Thanks

John

You cna change this using Management Studio Express in the Server Properties dialog.

Mike