Changing the SQL Server Name

I have SQL 2000 std installed on a win2000 box with latest svc packs and box
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thks
Did SQL Server start with an error along the lines of "has beeen tampered
with?"
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.
In order to fix the jobs you will 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
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>
|||Some info here: http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and box
> was originally designated with a development name which SQL also inherited.
> Now the server box name has been changed but the server still indicates the
> old box name.
> What are the implications if I leave as is and how difficult is it to change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan and
> had to be re-defined.
> thks
>

Changing the SQL Server Name

I have SQL 2000 std installed on a win2000 box with latest svc packs and box
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thksDid SQL Server start with an error along the lines of "has beeen tampered
with?"
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.
In order to fix the jobs you will 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
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>|||Some info here: http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and bo
x
> was originally designated with a development name which SQL also inherited
.
> Now the server box name has been changed but the server still indicates th
e
> old box name.
> What are the implications if I leave as is and how difficult is it to chan
ge
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan an
d
> had to be re-defined.
> thks
>

Changing the SQL Server Name

I have SQL 2000 std installed on a win2000 box with latest svc packs and box
was originally designated with a development name which SQL also inherited.
Now the server box name has been changed but the server still indicates the
old box name.
What are the implications if I leave as is and how difficult is it to change
it?
Can I just update sysserver in the master db through sp_addserver or are
there other steps?
Any registry impaacts? I noticed that some maintenance jobs I had defined
within SQL became orphaned after making changes to the maintenance plan and
had to be re-defined.
thksDid SQL Server start with an error along the lines of "has beeen tampered
with?"
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.
In order to fix the jobs you will 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
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
> I have SQL 2000 std installed on a win2000 box with latest svc packs and
box
> was originally designated with a development name which SQL also
inherited.
> Now the server box name has been changed but the server still indicates
the
> old box name.
> What are the implications if I leave as is and how difficult is it to
change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan
and
> had to be re-defined.
> thks
>|||Some info here: http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"tom frost" <tomfrost@.discussions.microsoft.com> wrote in message
news:82A1DBBE-53DA-4349-A122-32B5BD6571E6@.microsoft.com...
>I have SQL 2000 std installed on a win2000 box with latest svc packs and box
> was originally designated with a development name which SQL also inherited.
> Now the server box name has been changed but the server still indicates the
> old box name.
> What are the implications if I leave as is and how difficult is it to change
> it?
> Can I just update sysserver in the master db through sp_addserver or are
> there other steps?
> Any registry impaacts? I noticed that some maintenance jobs I had defined
> within SQL became orphaned after making changes to the maintenance plan and
> had to be re-defined.
> thks
>

changing datasource to SQL Server

Greetings,
I have a set of reports that were created using the report designer in
Visual Studio. They were originally written to run against an Informix
database, but I now need to change them to run against an SQL Server
DB. I added a new datasource for the SQL Server DB, but couldn't find
*any* way to change the reports to point to this new datasource. I've
worked around this problem by changing the properties of the existing
(Informix) datasource to point to the SQL Server DB, but if anyone
knows how to change *just* the datasource of a report, I'd be very
grateful if they'd let me know.
The queries that the reports execute currently use '?' to indicate an
Informix SQL parameter, but I believe SQL Server uses '@.param_name'
instead. If I replace each ? with @.param_name (in the 'SQL' pane of
the 'Data' tab) and map each @.param_name to the corresponding
ReportParameter, will this work, or is there something else I need to
do?
Thanks in Advance,
DonThe way you change the datasource is by going to the dataset, click on the
... and change the datasource. Or you can edit the rdl. Yes, changing and
remapping the parameters should work. One problem you will have is that RS
will try to create the report parameters so you very well will end up with
extra report parameters that you have to remove. Or, do this. Make sure you
have a copy of the rdl. Open up the report into the designer and go into
code view. Edit the xml with the parameter mapping, save, go to layout and
preview and see if it works.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Don" <donalmurtagh@.yahoo.co.uk> wrote in message
news:aa1c6f54.0504290857.60998e06@.posting.google.com...
> Greetings,
> I have a set of reports that were created using the report designer in
> Visual Studio. They were originally written to run against an Informix
> database, but I now need to change them to run against an SQL Server
> DB. I added a new datasource for the SQL Server DB, but couldn't find
> *any* way to change the reports to point to this new datasource. I've
> worked around this problem by changing the properties of the existing
> (Informix) datasource to point to the SQL Server DB, but if anyone
> knows how to change *just* the datasource of a report, I'd be very
> grateful if they'd let me know.
> The queries that the reports execute currently use '?' to indicate an
> Informix SQL parameter, but I believe SQL Server uses '@.param_name'
> instead. If I replace each ? with @.param_name (in the 'SQL' pane of
> the 'Data' tab) and map each @.param_name to the corresponding
> ReportParameter, will this work, or is there something else I need to
> do?
> Thanks in Advance,
> Don|||Hi Bruce,
Thanks very much for your response. I thought about editing the .rdl
directly in order to change the datasource, but the autogenerated IDs
scared me off - what exactly are these used for?
I'm aware that RS adds report parameters whenever you change an SQL
parameters - it's an annoying "feature", but not catastrophic. Are you
saying that if I replace every reference to the '?' parameters with a
'@.param' in the XML code then I won't have to deal with this?
Thanks Again,
Don|||Yep. I also do this sometimes when I am modifying a complicated SQL
Statement because sometimes with ODBC datasource it loses all the mappings
and I have to remap so I will go in and modify the SQL so the helpful IDE
doesn't mess everything up. Again, make a copy because it is easy to mess up
the xml.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<donalmurtagh@.yahoo.co.uk> wrote in message
news:1114946322.881807.132260@.g14g2000cwa.googlegroups.com...
> Hi Bruce,
> Thanks very much for your response. I thought about editing the .rdl
> directly in order to change the datasource, but the autogenerated IDs
> scared me off - what exactly are these used for?
> I'm aware that RS adds report parameters whenever you change an SQL
> parameters - it's an annoying "feature", but not catastrophic. Are you
> saying that if I replace every reference to the '?' parameters with a
> '@.param' in the XML code then I won't have to deal with this?
> Thanks Again,
> Don
>