Hi
I restored msdb database successfully,
because of changing
the server and needed to restore all jobs
have been schaduled for periodical backup all
user batabases.
but when I want to change the text of step1
of every job to new drive in a new server
following error happened:
""
why? what's wrong?
any help would be greatly appreciated.RM,
Do you get an error number?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> Hi
> I restored msdb database successfully,
> because of changing
> the server and needed to restore all jobs
> have been schaduled for periodical backup all
> user batabases.
> but when I want to change the text of step1
> of every job to new drive in a new server
> following error happened:
> ""
> why? what's wrong?
> any help would be greatly appreciated.|||Also check SQL server error log and SQLAgent log for complete information on this behaviour.
--
--
Satya SKJ
"Mark Allison" wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
> > Hi
> >
> > I restored msdb database successfully,
> > because of changing
> > the server and needed to restore all jobs
> > have been schaduled for periodical backup all
> > user batabases.
> > but when I want to change the text of step1
> > of every job to new drive in a new server
> > following error happened:
> > ""
> >
> > why? what's wrong?
> > any help would be greatly appreciated.
>|||yeah,
error 14274
On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
> RM,
> Do you get an error number?
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.|||RM, I don't know why your error message text is not showing but it
should be this:
"Error 14274: Cannot add, update, or delete a job (or its steps or
schedules) that originated from an MSX server."
This means that the server has been renamed and the originating_server
column in the sysjobs table is referencing the old server name. Update
sysjobs and it should be fine.
Use this proc to do the rename:
http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
This proc assumes that @.@.SERVERNAME is correct, you might want to check
that first, and correct it if it's wrong using sp_dropserver, sp_addserver
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
RM wrote:
> yeah,
> error 14274
> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
> <marka@.no.tinned.meat.mvps.org> wrote:
>> RM,
>> Do you get an error number?
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.
>|||thanks alot,
I was suprised ,very useful help**
On Tue, 13 Jul 2004 09:24:57 +0100, Mark Allison
<marka@.no.tinned.meat.mvps.org> wrote:
> RM, I don't know why your error message text is not showing but it
> should be this:
> "Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules) that originated from an MSX server."
> This means that the server has been renamed and the originating_server
> column in the sysjobs table is referencing the old server name. Update
> sysjobs and it should be fine.
> Use this proc to do the rename:
> http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
> This proc assumes that @.@.SERVERNAME is correct, you might want to check
> that first, and correct it if it's wrong using sp_dropserver,
> sp_addserver
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> RM wrote:
>> yeah,
>> error 14274
>> On Mon, 12 Jul 2004 11:32:16 +0100, Mark Allison
>> <marka@.no.tinned.meat.mvps.org> wrote:
>> RM,
>> Do you get an error number?
>> -- Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> RM wrote:
>> Hi
>> I restored msdb database successfully,
>> because of changing
>> the server and needed to restore all jobs
>> have been schaduled for periodical backup all
>> user batabases.
>> but when I want to change the text of step1
>> of every job to new drive in a new server
>> following error happened:
>> ""
>> why? what's wrong?
>> any help would be greatly appreciated.
>>
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Tuesday, March 20, 2012
Restoring MSDB to another server
We moved a server from one box to another. I restored
MSDB to the new server and some of the jobs didn't run as
scheduled. What should I have done to avoid this? It
appears the timing was thrown off. Any experience with
this shared would be appreciated.
Thanks.
Hi,
1. Stop the SQL Agent service
2. Since you restored the MSDB from a differnt server you need to update
the SYSJOBS table wth current sql server name,
Because the servername in the table will be source server and all the jobs
will fail.
How to update:-
UPDATE MSDB..SYSJOBS
SET Originating Server = @.@.Servername
WHERE Originating Server <> @.@.Servername
3. start sql agent service
Thanks
Hari
MCDBA
"metoonyc" <metoonyc
"Sandi" <sandra_richardson@.harvardpilgrim.org> wrote in message
news:bc8f01c4895a$65be0370$a401280a@.phx.gbl...
> We moved a server from one box to another. I restored
> MSDB to the new server and some of the jobs didn't run as
> scheduled. What should I have done to avoid this? It
> appears the timing was thrown off. Any experience with
> this shared would be appreciated.
> Thanks.
|||We had already changed the name of the new server to what the server
name was. So this shouldn't apply to my problem. However, if I
restored msdb while SQL Server Agent service was still running, would
this have caused the problem?
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
MSDB to the new server and some of the jobs didn't run as
scheduled. What should I have done to avoid this? It
appears the timing was thrown off. Any experience with
this shared would be appreciated.
Thanks.
Hi,
1. Stop the SQL Agent service
2. Since you restored the MSDB from a differnt server you need to update
the SYSJOBS table wth current sql server name,
Because the servername in the table will be source server and all the jobs
will fail.
How to update:-
UPDATE MSDB..SYSJOBS
SET Originating Server = @.@.Servername
WHERE Originating Server <> @.@.Servername
3. start sql agent service
Thanks
Hari
MCDBA
"metoonyc" <metoonyc
"Sandi" <sandra_richardson@.harvardpilgrim.org> wrote in message
news:bc8f01c4895a$65be0370$a401280a@.phx.gbl...
> We moved a server from one box to another. I restored
> MSDB to the new server and some of the jobs didn't run as
> scheduled. What should I have done to avoid this? It
> appears the timing was thrown off. Any experience with
> this shared would be appreciated.
> Thanks.
|||We had already changed the name of the new server to what the server
name was. So this shouldn't apply to my problem. However, if I
restored msdb while SQL Server Agent service was still running, would
this have caused the problem?
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Restoring MSDB to another server
We moved a server from one box to another. I restored
MSDB to the new server and some of the jobs didn't run as
scheduled. What should I have done to avoid this? It
appears the timing was thrown off. Any experience with
this shared would be appreciated.
Thanks.Hi,
1. Stop the SQL Agent service
2. Since you restored the MSDB from a differnt server you need to update
the SYSJOBS table wth current sql server name,
Because the servername in the table will be source server and all the jobs
will fail.
How to update:-
UPDATE MSDB..SYSJOBS
SET Originating Server = @.@.Servername
WHERE Originating Server <> @.@.Servername
3. start sql agent service
Thanks
Hari
MCDBA
"metoonyc" <metoonyc
"Sandi" <sandra_richardson@.harvardpilgrim.org> wrote in message
news:bc8f01c4895a$65be0370$a401280a@.phx.gbl...
> We moved a server from one box to another. I restored
> MSDB to the new server and some of the jobs didn't run as
> scheduled. What should I have done to avoid this? It
> appears the timing was thrown off. Any experience with
> this shared would be appreciated.
> Thanks.|||We had already changed the name of the new server to what the server
name was. So this shouldn't apply to my problem. However, if I
restored msdb while SQL Server Agent service was still running, would
this have caused the problem?
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
MSDB to the new server and some of the jobs didn't run as
scheduled. What should I have done to avoid this? It
appears the timing was thrown off. Any experience with
this shared would be appreciated.
Thanks.Hi,
1. Stop the SQL Agent service
2. Since you restored the MSDB from a differnt server you need to update
the SYSJOBS table wth current sql server name,
Because the servername in the table will be source server and all the jobs
will fail.
How to update:-
UPDATE MSDB..SYSJOBS
SET Originating Server = @.@.Servername
WHERE Originating Server <> @.@.Servername
3. start sql agent service
Thanks
Hari
MCDBA
"metoonyc" <metoonyc
"Sandi" <sandra_richardson@.harvardpilgrim.org> wrote in message
news:bc8f01c4895a$65be0370$a401280a@.phx.gbl...
> We moved a server from one box to another. I restored
> MSDB to the new server and some of the jobs didn't run as
> scheduled. What should I have done to avoid this? It
> appears the timing was thrown off. Any experience with
> this shared would be appreciated.
> Thanks.|||We had already changed the name of the new server to what the server
name was. So this shouldn't apply to my problem. However, if I
restored msdb while SQL Server Agent service was still running, would
this have caused the problem?
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Restoring MSDB to another server
We moved a server from one box to another. I restored
MSDB to the new server and some of the jobs didn't run as
scheduled. What should I have done to avoid this? It
appears the timing was thrown off. Any experience with
this shared would be appreciated.
Thanks.Hi,
1. Stop the SQL Agent service
2. Since you restored the MSDB from a differnt server you need to update
the SYSJOBS table wth current sql server name,
Because the servername in the table will be source server and all the jobs
will fail.
How to update:-
UPDATE MSDB..SYSJOBS
SET Originating Server = @.@.Servername
WHERE Originating Server <> @.@.Servername
3. start sql agent service
Thanks
Hari
MCDBA
"metoonyc" <metoonyc
"Sandi" <sandra_richardson@.harvardpilgrim.org> wrote in message
news:bc8f01c4895a$65be0370$a401280a@.phx.gbl...
> We moved a server from one box to another. I restored
> MSDB to the new server and some of the jobs didn't run as
> scheduled. What should I have done to avoid this? It
> appears the timing was thrown off. Any experience with
> this shared would be appreciated.
> Thanks.
MSDB to the new server and some of the jobs didn't run as
scheduled. What should I have done to avoid this? It
appears the timing was thrown off. Any experience with
this shared would be appreciated.
Thanks.Hi,
1. Stop the SQL Agent service
2. Since you restored the MSDB from a differnt server you need to update
the SYSJOBS table wth current sql server name,
Because the servername in the table will be source server and all the jobs
will fail.
How to update:-
UPDATE MSDB..SYSJOBS
SET Originating Server = @.@.Servername
WHERE Originating Server <> @.@.Servername
3. start sql agent service
Thanks
Hari
MCDBA
"metoonyc" <metoonyc
"Sandi" <sandra_richardson@.harvardpilgrim.org> wrote in message
news:bc8f01c4895a$65be0370$a401280a@.phx.gbl...
> We moved a server from one box to another. I restored
> MSDB to the new server and some of the jobs didn't run as
> scheduled. What should I have done to avoid this? It
> appears the timing was thrown off. Any experience with
> this shared would be appreciated.
> Thanks.
restoring msdb of different server
Hi
Evironment: SQL Server 2000 SP3a
I want to restore master & msdb (which transfers login,
settings, jobs etc.) of old server to the new server. What
are the possible issues with this approach, if any? Is
UPDATE msdb.dbo.sysjobs
SET originating_server = 'NewServerName'
WHERE originating_server = 'OldServerName'
enough in case of msdb?
The old server is Windows 2000 Advanced Server SP4, HP
Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
with Ultra SCSI 320 15k RPM disks attached. The new server
is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
app/OS RAM, the same RAID setup as in the old server.
I haven't changed any SQL Server settings on the old
server, except CPU affinity mask to use just one virtual
CPU on each of the physical CPUs and max. degree of
paralellism to 1.
Is SQL Server Setup aware of more advanced hardware of the
new server to such an extent that it can automatically
produce more optimal SQL server settings (stored in master)
than they were produced for the old server?
I.e. will the auto-generated settings in master database
from old server hurt performance on the new server?
--
Many, many thanks,
OskSee if this helps:
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546
AMB
"Osk" wrote:
> Hi
> Evironment: SQL Server 2000 SP3a
> I want to restore master & msdb (which transfers login,
> settings, jobs etc.) of old server to the new server. What
> are the possible issues with this approach, if any? Is
> UPDATE msdb.dbo.sysjobs
> SET originating_server = 'NewServerName'
> WHERE originating_server = 'OldServerName'
> enough in case of msdb?
> The old server is Windows 2000 Advanced Server SP4, HP
> Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
> Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
> and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
> with Ultra SCSI 320 15k RPM disks attached. The new server
> is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
> with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
> app/OS RAM, the same RAID setup as in the old server.
> I haven't changed any SQL Server settings on the old
> server, except CPU affinity mask to use just one virtual
> CPU on each of the physical CPUs and max. degree of
> paralellism to 1.
> Is SQL Server Setup aware of more advanced hardware of the
> new server to such an extent that it can automatically
> produce more optimal SQL server settings (stored in master)
> than they were produced for the old server?
> I.e. will the auto-generated settings in master database
> from old server hurt performance on the new server?
>
> --
> Many, many thanks,
> Osk
>
Evironment: SQL Server 2000 SP3a
I want to restore master & msdb (which transfers login,
settings, jobs etc.) of old server to the new server. What
are the possible issues with this approach, if any? Is
UPDATE msdb.dbo.sysjobs
SET originating_server = 'NewServerName'
WHERE originating_server = 'OldServerName'
enough in case of msdb?
The old server is Windows 2000 Advanced Server SP4, HP
Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
with Ultra SCSI 320 15k RPM disks attached. The new server
is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
app/OS RAM, the same RAID setup as in the old server.
I haven't changed any SQL Server settings on the old
server, except CPU affinity mask to use just one virtual
CPU on each of the physical CPUs and max. degree of
paralellism to 1.
Is SQL Server Setup aware of more advanced hardware of the
new server to such an extent that it can automatically
produce more optimal SQL server settings (stored in master)
than they were produced for the old server?
I.e. will the auto-generated settings in master database
from old server hurt performance on the new server?
--
Many, many thanks,
OskSee if this helps:
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546
AMB
"Osk" wrote:
> Hi
> Evironment: SQL Server 2000 SP3a
> I want to restore master & msdb (which transfers login,
> settings, jobs etc.) of old server to the new server. What
> are the possible issues with this approach, if any? Is
> UPDATE msdb.dbo.sysjobs
> SET originating_server = 'NewServerName'
> WHERE originating_server = 'OldServerName'
> enough in case of msdb?
> The old server is Windows 2000 Advanced Server SP4, HP
> Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
> Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
> and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
> with Ultra SCSI 320 15k RPM disks attached. The new server
> is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
> with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
> app/OS RAM, the same RAID setup as in the old server.
> I haven't changed any SQL Server settings on the old
> server, except CPU affinity mask to use just one virtual
> CPU on each of the physical CPUs and max. degree of
> paralellism to 1.
> Is SQL Server Setup aware of more advanced hardware of the
> new server to such an extent that it can automatically
> produce more optimal SQL server settings (stored in master)
> than they were produced for the old server?
> I.e. will the auto-generated settings in master database
> from old server hurt performance on the new server?
>
> --
> Many, many thanks,
> Osk
>
restoring msdb of different server
Hi
Evironment: SQL Server 2000 SP3a
I want to restore master & msdb (which transfers login,
settings, jobs etc.) of old server to the new server. What
are the possible issues with this approach, if any? Is
UPDATE msdb.dbo.sysjobs
SET originating_server = 'NewServerName'
WHERE originating_server = 'OldServerName'
enough in case of msdb?
The old server is Windows 2000 Advanced Server SP4, HP
Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
with Ultra SCSI 320 15k RPM disks attached. The new server
is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
app/OS RAM, the same RAID setup as in the old server.
I haven't changed any SQL Server settings on the old
server, except CPU affinity mask to use just one virtual
CPU on each of the physical CPUs and max. degree of
paralellism to 1.
Is SQL Server Setup aware of more advanced hardware of the
new server to such an extent that it can automatically
produce more optimal SQL server settings (stored in master)
than they were produced for the old server?
I.e. will the auto-generated settings in master database
from old server hurt performance on the new server?
Many, many thanks,
Osk
See if this helps:
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default...b;en-us;314546
AMB
"Osk" wrote:
> Hi
> Evironment: SQL Server 2000 SP3a
> I want to restore master & msdb (which transfers login,
> settings, jobs etc.) of old server to the new server. What
> are the possible issues with this approach, if any? Is
> UPDATE msdb.dbo.sysjobs
> SET originating_server = 'NewServerName'
> WHERE originating_server = 'OldServerName'
> enough in case of msdb?
> The old server is Windows 2000 Advanced Server SP4, HP
> Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
> Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
> and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
> with Ultra SCSI 320 15k RPM disks attached. The new server
> is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
> with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
> app/OS RAM, the same RAID setup as in the old server.
> I haven't changed any SQL Server settings on the old
> server, except CPU affinity mask to use just one virtual
> CPU on each of the physical CPUs and max. degree of
> paralellism to 1.
> Is SQL Server Setup aware of more advanced hardware of the
> new server to such an extent that it can automatically
> produce more optimal SQL server settings (stored in master)
> than they were produced for the old server?
> I.e. will the auto-generated settings in master database
> from old server hurt performance on the new server?
>
> --
> Many, many thanks,
> Osk
>
Evironment: SQL Server 2000 SP3a
I want to restore master & msdb (which transfers login,
settings, jobs etc.) of old server to the new server. What
are the possible issues with this approach, if any? Is
UPDATE msdb.dbo.sysjobs
SET originating_server = 'NewServerName'
WHERE originating_server = 'OldServerName'
enough in case of msdb?
The old server is Windows 2000 Advanced Server SP4, HP
Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
with Ultra SCSI 320 15k RPM disks attached. The new server
is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
app/OS RAM, the same RAID setup as in the old server.
I haven't changed any SQL Server settings on the old
server, except CPU affinity mask to use just one virtual
CPU on each of the physical CPUs and max. degree of
paralellism to 1.
Is SQL Server Setup aware of more advanced hardware of the
new server to such an extent that it can automatically
produce more optimal SQL server settings (stored in master)
than they were produced for the old server?
I.e. will the auto-generated settings in master database
from old server hurt performance on the new server?
Many, many thanks,
Osk
See if this helps:
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/default...b;en-us;314546
AMB
"Osk" wrote:
> Hi
> Evironment: SQL Server 2000 SP3a
> I want to restore master & msdb (which transfers login,
> settings, jobs etc.) of old server to the new server. What
> are the possible issues with this approach, if any? Is
> UPDATE msdb.dbo.sysjobs
> SET originating_server = 'NewServerName'
> WHERE originating_server = 'OldServerName'
> enough in case of msdb?
> The old server is Windows 2000 Advanced Server SP4, HP
> Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
> Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
> and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
> with Ultra SCSI 320 15k RPM disks attached. The new server
> is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
> with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
> app/OS RAM, the same RAID setup as in the old server.
> I haven't changed any SQL Server settings on the old
> server, except CPU affinity mask to use just one virtual
> CPU on each of the physical CPUs and max. degree of
> paralellism to 1.
> Is SQL Server Setup aware of more advanced hardware of the
> new server to such an extent that it can automatically
> produce more optimal SQL server settings (stored in master)
> than they were produced for the old server?
> I.e. will the auto-generated settings in master database
> from old server hurt performance on the new server?
>
> --
> Many, many thanks,
> Osk
>
restoring msdb of different server
Hi
Evironment: SQL Server 2000 SP3a
I want to restore master & msdb (which transfers login,
settings, jobs etc.) of old server to the new server. What
are the possible issues with this approach, if any? Is
UPDATE msdb.dbo.sysjobs
SET originating_server = 'NewServerName'
WHERE originating_server = 'OldServerName'
enough in case of msdb?
The old server is Windows 2000 Advanced Server SP4, HP
Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
with Ultra SCSI 320 15k RPM disks attached. The new server
is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
app/OS RAM, the same RAID setup as in the old server.
I haven't changed any SQL Server settings on the old
server, except CPU affinity mask to use just one virtual
CPU on each of the physical CPUs and max. degree of
paralellism to 1.
Is SQL Server Setup aware of more advanced hardware of the
new server to such an extent that it can automatically
produce more optimal SQL server settings (stored in master)
than they were produced for the old server?
I.e. will the auto-generated settings in master database
from old server hurt performance on the new server?
Many, many thanks,
OskSee if this helps:
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/defaul...kb;en-us;314546
AMB
"Osk" wrote:
> Hi
> Evironment: SQL Server 2000 SP3a
> I want to restore master & msdb (which transfers login,
> settings, jobs etc.) of old server to the new server. What
> are the possible issues with this approach, if any? Is
> UPDATE msdb.dbo.sysjobs
> SET originating_server = 'NewServerName'
> WHERE originating_server = 'OldServerName'
> enough in case of msdb?
> The old server is Windows 2000 Advanced Server SP4, HP
> Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
> Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
> and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
> with Ultra SCSI 320 15k RPM disks attached. The new server
> is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
> with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
> app/OS RAM, the same RAID setup as in the old server.
> I haven't changed any SQL Server settings on the old
> server, except CPU affinity mask to use just one virtual
> CPU on each of the physical CPUs and max. degree of
> paralellism to 1.
> Is SQL Server Setup aware of more advanced hardware of the
> new server to such an extent that it can automatically
> produce more optimal SQL server settings (stored in master)
> than they were produced for the old server?
> I.e. will the auto-generated settings in master database
> from old server hurt performance on the new server?
>
> --
> Many, many thanks,
> Osk
>
Evironment: SQL Server 2000 SP3a
I want to restore master & msdb (which transfers login,
settings, jobs etc.) of old server to the new server. What
are the possible issues with this approach, if any? Is
UPDATE msdb.dbo.sysjobs
SET originating_server = 'NewServerName'
WHERE originating_server = 'OldServerName'
enough in case of msdb?
The old server is Windows 2000 Advanced Server SP4, HP
Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
with Ultra SCSI 320 15k RPM disks attached. The new server
is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
app/OS RAM, the same RAID setup as in the old server.
I haven't changed any SQL Server settings on the old
server, except CPU affinity mask to use just one virtual
CPU on each of the physical CPUs and max. degree of
paralellism to 1.
Is SQL Server Setup aware of more advanced hardware of the
new server to such an extent that it can automatically
produce more optimal SQL server settings (stored in master)
than they were produced for the old server?
I.e. will the auto-generated settings in master database
from old server hurt performance on the new server?
Many, many thanks,
OskSee if this helps:
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/defaul...kb;en-us;314546
AMB
"Osk" wrote:
> Hi
> Evironment: SQL Server 2000 SP3a
> I want to restore master & msdb (which transfers login,
> settings, jobs etc.) of old server to the new server. What
> are the possible issues with this approach, if any? Is
> UPDATE msdb.dbo.sysjobs
> SET originating_server = 'NewServerName'
> WHERE originating_server = 'OldServerName'
> enough in case of msdb?
> The old server is Windows 2000 Advanced Server SP4, HP
> Proliant DL 380 G3 with 2 x 2.4 GHz Intel Xeon
> Hyper-Threading CPUs, 4GB RAM, of which 2GB is for apps,
> and HP SmartArray 5300/256 Ultra SCSI 320 RAID controller
> with Ultra SCSI 320 15k RPM disks attached. The new server
> is Windows 2003 Server Standart SP1, HP ProLiant DL 380 G4
> with 2 x 3.6 GHz Intel Xeon Hyper-Threading CPUs, 3.5 GB of
> app/OS RAM, the same RAID setup as in the old server.
> I haven't changed any SQL Server settings on the old
> server, except CPU affinity mask to use just one virtual
> CPU on each of the physical CPUs and max. degree of
> paralellism to 1.
> Is SQL Server Setup aware of more advanced hardware of the
> new server to such an extent that it can automatically
> produce more optimal SQL server settings (stored in master)
> than they were produced for the old server?
> I.e. will the auto-generated settings in master database
> from old server hurt performance on the new server?
>
> --
> Many, many thanks,
> Osk
>
Subscribe to:
Posts (Atom)