Restore to different version of 2003 OS

Hello,
I have a client with a database and want to use a second server as warm spare.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:
> Hello,
> I have a client with a database and want to use a second server as warm spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
> > Hello,
> > I have a client with a database and want to use a second server as warm spare.
> > Primary server is 2003 Std and the spare is 2003Ent.
> > I've heard that the OS must be the same to restore.
> > I can understand the SQL needs the same version 2000 and service pack level
> > on each server but what about the OS?
> >
> > Thanks in advance
> >
> > Kevin

Restore to different version of 2003 OS

Hello,
I have a client with a database and want to use a second server as warm spare.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David
|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin
|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:

> Hello,
> I have a client with a database and want to use a second server as warm spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack level
> on each server but what about the OS?
> Thanks in advance
> Kevin
|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
[vbcol=seagreen]
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:

Restore to different version of 2003 OS

Hello,
I have a client with a database and want to use a second server as warm spar
e.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:

> Hello,
> I have a client with a database and want to use a second server as warm sp
are.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack leve
l
> on each server but what about the OS?
> Thanks in advance
> Kevin|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
[vbcol=seagreen]
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
>

Restore of Publication Database caused error

Dear All,
We are currently using Transactional Replication for a Warm Standby.
We needed to perform a restore of out Publication Database last night and
now we are getting the error :-
DATE/TIME:07/04/2005 09:50:29
DESCRIPTION:Error: 14151, Severity: 18, State: 1
Replication-Replication Transaction-Log Reader Subsystem: agent
INVEST1-ParisProduction-12 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'INVEST1'.
COMMENT:One of the replications has failed, sort it out
JOB RUN:(None)
My normal fix for this would be to re-synchronise, but as the publication is
rather big I was wondering if there was a better way of doing it.
Thanks
Peter
try sp_replrestart or sp_repldone (EXEC sp_repldone @.xactid = NULL,
@.xact_segno = NULL, @.numtrans = 0, @.time = 0, @.reset = 1)
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
|||Thanks Guys,
Peter
"Peter Nolan" wrote:

> Dear All,
> We are currently using Transactional Replication for a Warm Standby.
> We needed to perform a restore of out Publication Database last night and
> now we are getting the error :-
> DATE/TIME:07/04/2005 09:50:29
> DESCRIPTION:Error: 14151, Severity: 18, State: 1
> Replication-Replication Transaction-Log Reader Subsystem: agent
> INVEST1-ParisProduction-12 failed. The process could not execute
> 'sp_repldone/sp_replcounters' on 'INVEST1'.
> COMMENT:One of the replications has failed, sort it out
> JOB RUN:(None)
> My normal fix for this would be to re-synchronise, but as the publication is
> rather big I was wondering if there was a better way of doing it.
> Thanks
> Peter