Is it possible to perform log shipping between a server running SQL 2000
Enterprise and another server running SQL 2005 Enterprise?
What would be the purpose of the secondary database?
Since you can restore SQL Server 2000 databases into SQL Server 2005
technically you can do log shipping to SQL Server 2005. But the opposite is
not possible because you can not restore SQL Server 2005 databases into SQL
Server 2000.
So, if you lose your SQL Server 2000 database and you only have the 2005
database. Do you plan to continue with 2005 only?
Ben Nevarez
Senior Database Administrator
"KnightFall1" wrote:
> Is it possible to perform log shipping between a server running SQL 2000
> Enterprise and another server running SQL 2005 Enterprise?
|||Hi Ben,
The original question relates to a work situation where we have a SQL 2000
Enterprise production database that needs to be replicated (for reporting
purposes) to an environment that has SQL 2005 running.
So I was curious if we could perform log shipping between the 2 servers to
replicate the database (assuming this is supported between these 2 versions
of SQL Server). This also brings up the question about whether transactional
replication is permitted between SQL 2000 and SQL 2005.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> What would be the purpose of the secondary database?
> Since you can restore SQL Server 2000 databases into SQL Server 2005
> technically you can do log shipping to SQL Server 2005. But the opposite is
> not possible because you can not restore SQL Server 2005 databases into SQL
> Server 2000.
> So, if you lose your SQL Server 2000 database and you only have the 2005
> database. Do you plan to continue with 2005 only?
> Ben Nevarez
> Senior Database Administrator
>
> "KnightFall1" wrote:
|||You say that you want to use the Secondary Server (in Log Shipping) for
reporting purposes. Then you should set its recovery state as STANDBY to
query against it. However then your users will be disconnected for the
coming Transaction Log to be applied to your Secondary Server. So your users
would experience disconnections.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...[vbcol=seagreen]
> Hi Ben,
> The original question relates to a work situation where we have a SQL 2000
> Enterprise production database that needs to be replicated (for reporting
> purposes) to an environment that has SQL 2005 running.
> So I was curious if we could perform log shipping between the 2 servers to
> replicate the database (assuming this is supported between these 2
> versions
> of SQL Server). This also brings up the question about whether
> transactional
> replication is permitted between SQL 2000 and SQL 2005.
> "Ben Nevarez" wrote:
|||Hi Ekrem,
The log shipping will be on a set schedule. Currently the business
requirement is once a day (we are still in the process of establishing a
specific time of day) for this process. So even if there is a disconnection,
the users on that end will know when the log shipping is occurring, so there
shouldn't be a problem.
Wouldn't you agree?
"Ekrem ?nsoy" wrote:
> You say that you want to use the Secondary Server (in Log Shipping) for
> reporting purposes. Then you should set its recovery state as STANDBY to
> query against it. However then your users will be disconnected for the
> coming Transaction Log to be applied to your Secondary Server. So your users
> would experience disconnections.
> --
> Ekrem ?nsoy
>
> "KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
> news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
>
|||Then your users would be querying a database which is older between 0-24
hours than the original one.
If this would not make any trouble and if you set up the Restore job (on the
Secondary Server) to start at a time when your users would be asleep then I
don't think there would be any problem with this setup.
P.S.
You know that your users will be able to use only SELECT against your
Secondary Database right? I just wanted to be sure you know about this.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:1F9B7D48-BCC2-4086-8CC5-CE2E01DE9959@.microsoft.com...[vbcol=seagreen]
> Hi Ekrem,
> The log shipping will be on a set schedule. Currently the business
> requirement is once a day (we are still in the process of establishing a
> specific time of day) for this process. So even if there is a
> disconnection,
> the users on that end will know when the log shipping is occurring, so
> there
> shouldn't be a problem.
> Wouldn't you agree?
>
> "Ekrem ?nsoy" wrote:
Showing posts with label versions. Show all posts
Showing posts with label versions. Show all posts
Wednesday, March 7, 2012
Log Shipping between SQL Server versions
Is it possible to perform log shipping between a server running SQL 2000
Enterprise and another server running SQL 2005 Enterprise?What would be the purpose of the secondary database?
Since you can restore SQL Server 2000 databases into SQL Server 2005
technically you can do log shipping to SQL Server 2005. But the opposite is
not possible because you can not restore SQL Server 2005 databases into SQL
Server 2000.
So, if you lose your SQL Server 2000 database and you only have the 2005
database. Do you plan to continue with 2005 only?
Ben Nevarez
Senior Database Administrator
"KnightFall1" wrote:
> Is it possible to perform log shipping between a server running SQL 2000
> Enterprise and another server running SQL 2005 Enterprise?|||Hi Ben,
The original question relates to a work situation where we have a SQL 2000
Enterprise production database that needs to be replicated (for reporting
purposes) to an environment that has SQL 2005 running.
So I was curious if we could perform log shipping between the 2 servers to
replicate the database (assuming this is supported between these 2 versions
of SQL Server). This also brings up the question about whether transactional
replication is permitted between SQL 2000 and SQL 2005.
"Ben Nevarez" wrote:
> What would be the purpose of the secondary database?
> Since you can restore SQL Server 2000 databases into SQL Server 2005
> technically you can do log shipping to SQL Server 2005. But the opposite is
> not possible because you can not restore SQL Server 2005 databases into SQL
> Server 2000.
> So, if you lose your SQL Server 2000 database and you only have the 2005
> database. Do you plan to continue with 2005 only?
> Ben Nevarez
> Senior Database Administrator
>
> "KnightFall1" wrote:
> > Is it possible to perform log shipping between a server running SQL 2000
> > Enterprise and another server running SQL 2005 Enterprise?|||You say that you want to use the Secondary Server (in Log Shipping) for
reporting purposes. Then you should set its recovery state as STANDBY to
query against it. However then your users will be disconnected for the
coming Transaction Log to be applied to your Secondary Server. So your users
would experience disconnections.
--
Ekrem Ã?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
> Hi Ben,
> The original question relates to a work situation where we have a SQL 2000
> Enterprise production database that needs to be replicated (for reporting
> purposes) to an environment that has SQL 2005 running.
> So I was curious if we could perform log shipping between the 2 servers to
> replicate the database (assuming this is supported between these 2
> versions
> of SQL Server). This also brings up the question about whether
> transactional
> replication is permitted between SQL 2000 and SQL 2005.
> "Ben Nevarez" wrote:
>> What would be the purpose of the secondary database?
>> Since you can restore SQL Server 2000 databases into SQL Server 2005
>> technically you can do log shipping to SQL Server 2005. But the opposite
>> is
>> not possible because you can not restore SQL Server 2005 databases into
>> SQL
>> Server 2000.
>> So, if you lose your SQL Server 2000 database and you only have the 2005
>> database. Do you plan to continue with 2005 only?
>> Ben Nevarez
>> Senior Database Administrator
>>
>> "KnightFall1" wrote:
>> > Is it possible to perform log shipping between a server running SQL
>> > 2000
>> > Enterprise and another server running SQL 2005 Enterprise?|||Hi Ekrem,
The log shipping will be on a set schedule. Currently the business
requirement is once a day (we are still in the process of establishing a
specific time of day) for this process. So even if there is a disconnection,
the users on that end will know when the log shipping is occurring, so there
shouldn't be a problem.
Wouldn't you agree?
"Ekrem Ã?nsoy" wrote:
> You say that you want to use the Secondary Server (in Log Shipping) for
> reporting purposes. Then you should set its recovery state as STANDBY to
> query against it. However then your users will be disconnected for the
> coming Transaction Log to be applied to your Secondary Server. So your users
> would experience disconnections.
> --
> Ekrem Ã?nsoy
>
> "KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
> news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
> > Hi Ben,
> >
> > The original question relates to a work situation where we have a SQL 2000
> > Enterprise production database that needs to be replicated (for reporting
> > purposes) to an environment that has SQL 2005 running.
> >
> > So I was curious if we could perform log shipping between the 2 servers to
> > replicate the database (assuming this is supported between these 2
> > versions
> > of SQL Server). This also brings up the question about whether
> > transactional
> > replication is permitted between SQL 2000 and SQL 2005.
> >
> > "Ben Nevarez" wrote:
> >
> >>
> >> What would be the purpose of the secondary database?
> >>
> >> Since you can restore SQL Server 2000 databases into SQL Server 2005
> >> technically you can do log shipping to SQL Server 2005. But the opposite
> >> is
> >> not possible because you can not restore SQL Server 2005 databases into
> >> SQL
> >> Server 2000.
> >>
> >> So, if you lose your SQL Server 2000 database and you only have the 2005
> >> database. Do you plan to continue with 2005 only?
> >>
> >> Ben Nevarez
> >> Senior Database Administrator
> >>
> >>
> >>
> >> "KnightFall1" wrote:
> >>
> >> > Is it possible to perform log shipping between a server running SQL
> >> > 2000
> >> > Enterprise and another server running SQL 2005 Enterprise?
>|||Then your users would be querying a database which is older between 0-24
hours than the original one.
If this would not make any trouble and if you set up the Restore job (on the
Secondary Server) to start at a time when your users would be asleep then I
don't think there would be any problem with this setup.
P.S.
You know that your users will be able to use only SELECT against your
Secondary Database right? I just wanted to be sure you know about this.
--
Ekrem Ã?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:1F9B7D48-BCC2-4086-8CC5-CE2E01DE9959@.microsoft.com...
> Hi Ekrem,
> The log shipping will be on a set schedule. Currently the business
> requirement is once a day (we are still in the process of establishing a
> specific time of day) for this process. So even if there is a
> disconnection,
> the users on that end will know when the log shipping is occurring, so
> there
> shouldn't be a problem.
> Wouldn't you agree?
>
> "Ekrem Ã?nsoy" wrote:
>> You say that you want to use the Secondary Server (in Log Shipping) for
>> reporting purposes. Then you should set its recovery state as STANDBY to
>> query against it. However then your users will be disconnected for the
>> coming Transaction Log to be applied to your Secondary Server. So your
>> users
>> would experience disconnections.
>> --
>> Ekrem Ã?nsoy
>>
>> "KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
>> news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
>> > Hi Ben,
>> >
>> > The original question relates to a work situation where we have a SQL
>> > 2000
>> > Enterprise production database that needs to be replicated (for
>> > reporting
>> > purposes) to an environment that has SQL 2005 running.
>> >
>> > So I was curious if we could perform log shipping between the 2 servers
>> > to
>> > replicate the database (assuming this is supported between these 2
>> > versions
>> > of SQL Server). This also brings up the question about whether
>> > transactional
>> > replication is permitted between SQL 2000 and SQL 2005.
>> >
>> > "Ben Nevarez" wrote:
>> >
>> >>
>> >> What would be the purpose of the secondary database?
>> >>
>> >> Since you can restore SQL Server 2000 databases into SQL Server 2005
>> >> technically you can do log shipping to SQL Server 2005. But the
>> >> opposite
>> >> is
>> >> not possible because you can not restore SQL Server 2005 databases
>> >> into
>> >> SQL
>> >> Server 2000.
>> >>
>> >> So, if you lose your SQL Server 2000 database and you only have the
>> >> 2005
>> >> database. Do you plan to continue with 2005 only?
>> >>
>> >> Ben Nevarez
>> >> Senior Database Administrator
>> >>
>> >>
>> >>
>> >> "KnightFall1" wrote:
>> >>
>> >> > Is it possible to perform log shipping between a server running SQL
>> >> > 2000
>> >> > Enterprise and another server running SQL 2005 Enterprise?
>>
Enterprise and another server running SQL 2005 Enterprise?What would be the purpose of the secondary database?
Since you can restore SQL Server 2000 databases into SQL Server 2005
technically you can do log shipping to SQL Server 2005. But the opposite is
not possible because you can not restore SQL Server 2005 databases into SQL
Server 2000.
So, if you lose your SQL Server 2000 database and you only have the 2005
database. Do you plan to continue with 2005 only?
Ben Nevarez
Senior Database Administrator
"KnightFall1" wrote:
> Is it possible to perform log shipping between a server running SQL 2000
> Enterprise and another server running SQL 2005 Enterprise?|||Hi Ben,
The original question relates to a work situation where we have a SQL 2000
Enterprise production database that needs to be replicated (for reporting
purposes) to an environment that has SQL 2005 running.
So I was curious if we could perform log shipping between the 2 servers to
replicate the database (assuming this is supported between these 2 versions
of SQL Server). This also brings up the question about whether transactional
replication is permitted between SQL 2000 and SQL 2005.
"Ben Nevarez" wrote:
> What would be the purpose of the secondary database?
> Since you can restore SQL Server 2000 databases into SQL Server 2005
> technically you can do log shipping to SQL Server 2005. But the opposite is
> not possible because you can not restore SQL Server 2005 databases into SQL
> Server 2000.
> So, if you lose your SQL Server 2000 database and you only have the 2005
> database. Do you plan to continue with 2005 only?
> Ben Nevarez
> Senior Database Administrator
>
> "KnightFall1" wrote:
> > Is it possible to perform log shipping between a server running SQL 2000
> > Enterprise and another server running SQL 2005 Enterprise?|||You say that you want to use the Secondary Server (in Log Shipping) for
reporting purposes. Then you should set its recovery state as STANDBY to
query against it. However then your users will be disconnected for the
coming Transaction Log to be applied to your Secondary Server. So your users
would experience disconnections.
--
Ekrem Ã?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
> Hi Ben,
> The original question relates to a work situation where we have a SQL 2000
> Enterprise production database that needs to be replicated (for reporting
> purposes) to an environment that has SQL 2005 running.
> So I was curious if we could perform log shipping between the 2 servers to
> replicate the database (assuming this is supported between these 2
> versions
> of SQL Server). This also brings up the question about whether
> transactional
> replication is permitted between SQL 2000 and SQL 2005.
> "Ben Nevarez" wrote:
>> What would be the purpose of the secondary database?
>> Since you can restore SQL Server 2000 databases into SQL Server 2005
>> technically you can do log shipping to SQL Server 2005. But the opposite
>> is
>> not possible because you can not restore SQL Server 2005 databases into
>> SQL
>> Server 2000.
>> So, if you lose your SQL Server 2000 database and you only have the 2005
>> database. Do you plan to continue with 2005 only?
>> Ben Nevarez
>> Senior Database Administrator
>>
>> "KnightFall1" wrote:
>> > Is it possible to perform log shipping between a server running SQL
>> > 2000
>> > Enterprise and another server running SQL 2005 Enterprise?|||Hi Ekrem,
The log shipping will be on a set schedule. Currently the business
requirement is once a day (we are still in the process of establishing a
specific time of day) for this process. So even if there is a disconnection,
the users on that end will know when the log shipping is occurring, so there
shouldn't be a problem.
Wouldn't you agree?
"Ekrem Ã?nsoy" wrote:
> You say that you want to use the Secondary Server (in Log Shipping) for
> reporting purposes. Then you should set its recovery state as STANDBY to
> query against it. However then your users will be disconnected for the
> coming Transaction Log to be applied to your Secondary Server. So your users
> would experience disconnections.
> --
> Ekrem Ã?nsoy
>
> "KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
> news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
> > Hi Ben,
> >
> > The original question relates to a work situation where we have a SQL 2000
> > Enterprise production database that needs to be replicated (for reporting
> > purposes) to an environment that has SQL 2005 running.
> >
> > So I was curious if we could perform log shipping between the 2 servers to
> > replicate the database (assuming this is supported between these 2
> > versions
> > of SQL Server). This also brings up the question about whether
> > transactional
> > replication is permitted between SQL 2000 and SQL 2005.
> >
> > "Ben Nevarez" wrote:
> >
> >>
> >> What would be the purpose of the secondary database?
> >>
> >> Since you can restore SQL Server 2000 databases into SQL Server 2005
> >> technically you can do log shipping to SQL Server 2005. But the opposite
> >> is
> >> not possible because you can not restore SQL Server 2005 databases into
> >> SQL
> >> Server 2000.
> >>
> >> So, if you lose your SQL Server 2000 database and you only have the 2005
> >> database. Do you plan to continue with 2005 only?
> >>
> >> Ben Nevarez
> >> Senior Database Administrator
> >>
> >>
> >>
> >> "KnightFall1" wrote:
> >>
> >> > Is it possible to perform log shipping between a server running SQL
> >> > 2000
> >> > Enterprise and another server running SQL 2005 Enterprise?
>|||Then your users would be querying a database which is older between 0-24
hours than the original one.
If this would not make any trouble and if you set up the Restore job (on the
Secondary Server) to start at a time when your users would be asleep then I
don't think there would be any problem with this setup.
P.S.
You know that your users will be able to use only SELECT against your
Secondary Database right? I just wanted to be sure you know about this.
--
Ekrem Ã?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:1F9B7D48-BCC2-4086-8CC5-CE2E01DE9959@.microsoft.com...
> Hi Ekrem,
> The log shipping will be on a set schedule. Currently the business
> requirement is once a day (we are still in the process of establishing a
> specific time of day) for this process. So even if there is a
> disconnection,
> the users on that end will know when the log shipping is occurring, so
> there
> shouldn't be a problem.
> Wouldn't you agree?
>
> "Ekrem Ã?nsoy" wrote:
>> You say that you want to use the Secondary Server (in Log Shipping) for
>> reporting purposes. Then you should set its recovery state as STANDBY to
>> query against it. However then your users will be disconnected for the
>> coming Transaction Log to be applied to your Secondary Server. So your
>> users
>> would experience disconnections.
>> --
>> Ekrem Ã?nsoy
>>
>> "KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
>> news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
>> > Hi Ben,
>> >
>> > The original question relates to a work situation where we have a SQL
>> > 2000
>> > Enterprise production database that needs to be replicated (for
>> > reporting
>> > purposes) to an environment that has SQL 2005 running.
>> >
>> > So I was curious if we could perform log shipping between the 2 servers
>> > to
>> > replicate the database (assuming this is supported between these 2
>> > versions
>> > of SQL Server). This also brings up the question about whether
>> > transactional
>> > replication is permitted between SQL 2000 and SQL 2005.
>> >
>> > "Ben Nevarez" wrote:
>> >
>> >>
>> >> What would be the purpose of the secondary database?
>> >>
>> >> Since you can restore SQL Server 2000 databases into SQL Server 2005
>> >> technically you can do log shipping to SQL Server 2005. But the
>> >> opposite
>> >> is
>> >> not possible because you can not restore SQL Server 2005 databases
>> >> into
>> >> SQL
>> >> Server 2000.
>> >>
>> >> So, if you lose your SQL Server 2000 database and you only have the
>> >> 2005
>> >> database. Do you plan to continue with 2005 only?
>> >>
>> >> Ben Nevarez
>> >> Senior Database Administrator
>> >>
>> >>
>> >>
>> >> "KnightFall1" wrote:
>> >>
>> >> > Is it possible to perform log shipping between a server running SQL
>> >> > 2000
>> >> > Enterprise and another server running SQL 2005 Enterprise?
>>
Log Shipping between SQL Server versions
Is it possible to perform log shipping between a server running SQL 2000
Enterprise and another server running SQL 2005 Enterprise?What would be the purpose of the secondary database?
Since you can restore SQL Server 2000 databases into SQL Server 2005
technically you can do log shipping to SQL Server 2005. But the opposite is
not possible because you can not restore SQL Server 2005 databases into SQL
Server 2000.
So, if you lose your SQL Server 2000 database and you only have the 2005
database. Do you plan to continue with 2005 only?
Ben Nevarez
Senior Database Administrator
"KnightFall1" wrote:
> Is it possible to perform log shipping between a server running SQL 2000
> Enterprise and another server running SQL 2005 Enterprise?|||Hi Ben,
The original question relates to a work situation where we have a SQL 2000
Enterprise production database that needs to be replicated (for reporting
purposes) to an environment that has SQL 2005 running.
So I was curious if we could perform log shipping between the 2 servers to
replicate the database (assuming this is supported between these 2 versions
of SQL Server). This also brings up the question about whether transactional
replication is permitted between SQL 2000 and SQL 2005.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> What would be the purpose of the secondary database?
> Since you can restore SQL Server 2000 databases into SQL Server 2005
> technically you can do log shipping to SQL Server 2005. But the opposite i
s
> not possible because you can not restore SQL Server 2005 databases into SQ
L
> Server 2000.
> So, if you lose your SQL Server 2000 database and you only have the 2005
> database. Do you plan to continue with 2005 only?
> Ben Nevarez
> Senior Database Administrator
>
> "KnightFall1" wrote:
>|||You say that you want to use the Secondary Server (in Log Shipping) for
reporting purposes. Then you should set its recovery state as STANDBY to
query against it. However then your users will be disconnected for the
coming Transaction Log to be applied to your Secondary Server. So your users
would experience disconnections.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...[vbcol=seagreen]
> Hi Ben,
> The original question relates to a work situation where we have a SQL 2000
> Enterprise production database that needs to be replicated (for reporting
> purposes) to an environment that has SQL 2005 running.
> So I was curious if we could perform log shipping between the 2 servers to
> replicate the database (assuming this is supported between these 2
> versions
> of SQL Server). This also brings up the question about whether
> transactional
> replication is permitted between SQL 2000 and SQL 2005.
> "Ben Nevarez" wrote:
>|||Hi Ekrem,
The log shipping will be on a set schedule. Currently the business
requirement is once a day (we are still in the process of establishing a
specific time of day) for this process. So even if there is a disconnection,
the users on that end will know when the log shipping is occurring, so there
shouldn't be a problem.
Wouldn't you agree?
"Ekrem ?nsoy" wrote:
> You say that you want to use the Secondary Server (in Log Shipping) for
> reporting purposes. Then you should set its recovery state as STANDBY to
> query against it. However then your users will be disconnected for the
> coming Transaction Log to be applied to your Secondary Server. So your use
rs
> would experience disconnections.
> --
> Ekrem ?nsoy
>
> "KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
> news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
>|||Then your users would be querying a database which is older between 0-24
hours than the original one.
If this would not make any trouble and if you set up the Restore job (on the
Secondary Server) to start at a time when your users would be asleep then I
don't think there would be any problem with this setup.
P.S.
You know that your users will be able to use only SELECT against your
Secondary Database right? I just wanted to be sure you know about this.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:1F9B7D48-BCC2-4086-8CC5-CE2E01DE9959@.microsoft.com...[vbcol=seagreen]
> Hi Ekrem,
> The log shipping will be on a set schedule. Currently the business
> requirement is once a day (we are still in the process of establishing a
> specific time of day) for this process. So even if there is a
> disconnection,
> the users on that end will know when the log shipping is occurring, so
> there
> shouldn't be a problem.
> Wouldn't you agree?
>
> "Ekrem ?nsoy" wrote:
>
Enterprise and another server running SQL 2005 Enterprise?What would be the purpose of the secondary database?
Since you can restore SQL Server 2000 databases into SQL Server 2005
technically you can do log shipping to SQL Server 2005. But the opposite is
not possible because you can not restore SQL Server 2005 databases into SQL
Server 2000.
So, if you lose your SQL Server 2000 database and you only have the 2005
database. Do you plan to continue with 2005 only?
Ben Nevarez
Senior Database Administrator
"KnightFall1" wrote:
> Is it possible to perform log shipping between a server running SQL 2000
> Enterprise and another server running SQL 2005 Enterprise?|||Hi Ben,
The original question relates to a work situation where we have a SQL 2000
Enterprise production database that needs to be replicated (for reporting
purposes) to an environment that has SQL 2005 running.
So I was curious if we could perform log shipping between the 2 servers to
replicate the database (assuming this is supported between these 2 versions
of SQL Server). This also brings up the question about whether transactional
replication is permitted between SQL 2000 and SQL 2005.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> What would be the purpose of the secondary database?
> Since you can restore SQL Server 2000 databases into SQL Server 2005
> technically you can do log shipping to SQL Server 2005. But the opposite i
s
> not possible because you can not restore SQL Server 2005 databases into SQ
L
> Server 2000.
> So, if you lose your SQL Server 2000 database and you only have the 2005
> database. Do you plan to continue with 2005 only?
> Ben Nevarez
> Senior Database Administrator
>
> "KnightFall1" wrote:
>|||You say that you want to use the Secondary Server (in Log Shipping) for
reporting purposes. Then you should set its recovery state as STANDBY to
query against it. However then your users will be disconnected for the
coming Transaction Log to be applied to your Secondary Server. So your users
would experience disconnections.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...[vbcol=seagreen]
> Hi Ben,
> The original question relates to a work situation where we have a SQL 2000
> Enterprise production database that needs to be replicated (for reporting
> purposes) to an environment that has SQL 2005 running.
> So I was curious if we could perform log shipping between the 2 servers to
> replicate the database (assuming this is supported between these 2
> versions
> of SQL Server). This also brings up the question about whether
> transactional
> replication is permitted between SQL 2000 and SQL 2005.
> "Ben Nevarez" wrote:
>|||Hi Ekrem,
The log shipping will be on a set schedule. Currently the business
requirement is once a day (we are still in the process of establishing a
specific time of day) for this process. So even if there is a disconnection,
the users on that end will know when the log shipping is occurring, so there
shouldn't be a problem.
Wouldn't you agree?
"Ekrem ?nsoy" wrote:
> You say that you want to use the Secondary Server (in Log Shipping) for
> reporting purposes. Then you should set its recovery state as STANDBY to
> query against it. However then your users will be disconnected for the
> coming Transaction Log to be applied to your Secondary Server. So your use
rs
> would experience disconnections.
> --
> Ekrem ?nsoy
>
> "KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
> news:C8170C24-90E5-47C6-ABA0-5139B920FB1C@.microsoft.com...
>|||Then your users would be querying a database which is older between 0-24
hours than the original one.
If this would not make any trouble and if you set up the Restore job (on the
Secondary Server) to start at a time when your users would be asleep then I
don't think there would be any problem with this setup.
P.S.
You know that your users will be able to use only SELECT against your
Secondary Database right? I just wanted to be sure you know about this.
Ekrem ?nsoy
"KnightFall1" <KnightFall1@.discussions.microsoft.com> wrote in message
news:1F9B7D48-BCC2-4086-8CC5-CE2E01DE9959@.microsoft.com...[vbcol=seagreen]
> Hi Ekrem,
> The log shipping will be on a set schedule. Currently the business
> requirement is once a day (we are still in the process of establishing a
> specific time of day) for this process. So even if there is a
> disconnection,
> the users on that end will know when the log shipping is occurring, so
> there
> shouldn't be a problem.
> Wouldn't you agree?
>
> "Ekrem ?nsoy" wrote:
>
log shipping between 64 and 32 bit servers...
Hi,
I am just wondering if you can do log shipping with 2005 between a 64
and 32 bit versions. We have a 32 bit server now that will become the
backup and are looking at purchasing 64bit server to make use of oodles
of cheap ram.
Thanks,
TrevorI have never actually done any log shipping between 64-bit and 32-bit, but
I'm pretty certain it would work because we have been copying/restoring
backups between 64-bit and 32-bit.
Linchi
"TrevorD" wrote:
> Hi,
> I am just wondering if you can do log shipping with 2005 between a 64
> and 32 bit versions. We have a 32 bit server now that will become the
> backup and are looking at purchasing 64bit server to make use of oodles
> of cheap ram.
> Thanks,
> Trevor
>
I am just wondering if you can do log shipping with 2005 between a 64
and 32 bit versions. We have a 32 bit server now that will become the
backup and are looking at purchasing 64bit server to make use of oodles
of cheap ram.
Thanks,
TrevorI have never actually done any log shipping between 64-bit and 32-bit, but
I'm pretty certain it would work because we have been copying/restoring
backups between 64-bit and 32-bit.
Linchi
"TrevorD" wrote:
> Hi,
> I am just wondering if you can do log shipping with 2005 between a 64
> and 32 bit versions. We have a 32 bit server now that will become the
> backup and are looking at purchasing 64bit server to make use of oodles
> of cheap ram.
> Thanks,
> Trevor
>
log shipping between 64 and 32 bit servers...
Hi,
I am just wondering if you can do log shipping with 2005 between a 64
and 32 bit versions. We have a 32 bit server now that will become the
backup and are looking at purchasing 64bit server to make use of oodles
of cheap ram.
Thanks,
Trevor
I have never actually done any log shipping between 64-bit and 32-bit, but
I'm pretty certain it would work because we have been copying/restoring
backups between 64-bit and 32-bit.
Linchi
"TrevorD" wrote:
> Hi,
> I am just wondering if you can do log shipping with 2005 between a 64
> and 32 bit versions. We have a 32 bit server now that will become the
> backup and are looking at purchasing 64bit server to make use of oodles
> of cheap ram.
> Thanks,
> Trevor
>
I am just wondering if you can do log shipping with 2005 between a 64
and 32 bit versions. We have a 32 bit server now that will become the
backup and are looking at purchasing 64bit server to make use of oodles
of cheap ram.
Thanks,
Trevor
I have never actually done any log shipping between 64-bit and 32-bit, but
I'm pretty certain it would work because we have been copying/restoring
backups between 64-bit and 32-bit.
Linchi
"TrevorD" wrote:
> Hi,
> I am just wondering if you can do log shipping with 2005 between a 64
> and 32 bit versions. We have a 32 bit server now that will become the
> backup and are looking at purchasing 64bit server to make use of oodles
> of cheap ram.
> Thanks,
> Trevor
>
log shipping between 64 and 32 bit servers...
Hi,
I am just wondering if you can do log shipping with 2005 between a 64
and 32 bit versions. We have a 32 bit server now that will become the
backup and are looking at purchasing 64bit server to make use of oodles
of cheap ram.
Thanks,
TrevorI have never actually done any log shipping between 64-bit and 32-bit, but
I'm pretty certain it would work because we have been copying/restoring
backups between 64-bit and 32-bit.
Linchi
"TrevorD" wrote:
> Hi,
> I am just wondering if you can do log shipping with 2005 between a 64
> and 32 bit versions. We have a 32 bit server now that will become the
> backup and are looking at purchasing 64bit server to make use of oodles
> of cheap ram.
> Thanks,
> Trevor
>
I am just wondering if you can do log shipping with 2005 between a 64
and 32 bit versions. We have a 32 bit server now that will become the
backup and are looking at purchasing 64bit server to make use of oodles
of cheap ram.
Thanks,
TrevorI have never actually done any log shipping between 64-bit and 32-bit, but
I'm pretty certain it would work because we have been copying/restoring
backups between 64-bit and 32-bit.
Linchi
"TrevorD" wrote:
> Hi,
> I am just wondering if you can do log shipping with 2005 between a 64
> and 32 bit versions. We have a 32 bit server now that will become the
> backup and are looking at purchasing 64bit server to make use of oodles
> of cheap ram.
> Thanks,
> Trevor
>
Monday, February 20, 2012
Log Shipping (SQL 2000) btwn OS versions?
Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
Thanks!yellowbug wrote:
> Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
> environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
> Thanks!
>
Care to be more specific? What sort of problems?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are doing a data center migration to a new location and I was hoping
to upgrade our disaster recovery servers to windows 2003 during this
migration. However the front end machines will be on Windows 2000 for
at least a few more months. So I thought I'd throw a feeler out there
and see if anyone has had any problems with this type of configuration.
Thanks
|||yellowbug wrote:
> We are doing a data center migration to a new location and I was hoping
> to upgrade our disaster recovery servers to windows 2003 during this
> migration. However the front end machines will be on Windows 2000 for
> at least a few more months. So I thought I'd throw a feeler out there
> and see if anyone has had any problems with this type of configuration.
> Thanks
>
SQL backups are just files to the OS, nor does the OS have anything to
do with the restore of those backups. Are you using a home-grown log
shipping method, or the wizard-driven stuff that SQL provides? Either
way, I don't foresee that you'd have any problems due to the different
OS versions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
Thanks!yellowbug wrote:
> Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
> environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
> Thanks!
>
Care to be more specific? What sort of problems?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are doing a data center migration to a new location and I was hoping
to upgrade our disaster recovery servers to windows 2003 during this
migration. However the front end machines will be on Windows 2000 for
at least a few more months. So I thought I'd throw a feeler out there
and see if anyone has had any problems with this type of configuration.
Thanks
|||yellowbug wrote:> We are doing a data center migration to a new location and I was hoping
> to upgrade our disaster recovery servers to windows 2003 during this
> migration. However the front end machines will be on Windows 2000 for
> at least a few more months. So I thought I'd throw a feeler out there
> and see if anyone has had any problems with this type of configuration.
> Thanks
>
SQL backups are just files to the OS, nor does the OS have anything to
do with the restore of those backups. Are you using a home-grown log
shipping method, or the wizard-driven stuff that SQL provides? Either
way, I don't foresee that you'd have any problems due to the different
OS versions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Log Shipping (SQL 2000) btwn OS versions?
Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
Thanks!yellowbug wrote:
> Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
> environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
> Thanks!
>
Care to be more specific? What sort of problems?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are doing a data center migration to a new location and I was hoping
to upgrade our disaster recovery servers to windows 2003 during this
migration. However the front end machines will be on windows 2000 for
at least a few more months. So I thought I'd throw a feeler out there
and see if anyone has had any problems with this type of configuration.
Thanks :)|||yellowbug wrote:
> We are doing a data center migration to a new location and I was hoping
> to upgrade our disaster recovery servers to windows 2003 during this
> migration. However the front end machines will be on windows 2000 for
> at least a few more months. So I thought I'd throw a feeler out there
> and see if anyone has had any problems with this type of configuration.
> Thanks :)
>
SQL backups are just files to the OS, nor does the OS have anything to
do with the restore of those backups. Are you using a home-grown log
shipping method, or the wizard-driven stuff that SQL provides? Either
way, I don't foresee that you'd have any problems due to the different
OS versions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
Thanks!yellowbug wrote:
> Has anyone noticed any problems logshipping in a SQL 2k Ent. Ed.
> environment with Windows 2k to a SQL 2k Ent. Ed. with Windows 2003?
> Thanks!
>
Care to be more specific? What sort of problems?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||We are doing a data center migration to a new location and I was hoping
to upgrade our disaster recovery servers to windows 2003 during this
migration. However the front end machines will be on windows 2000 for
at least a few more months. So I thought I'd throw a feeler out there
and see if anyone has had any problems with this type of configuration.
Thanks :)|||yellowbug wrote:
> We are doing a data center migration to a new location and I was hoping
> to upgrade our disaster recovery servers to windows 2003 during this
> migration. However the front end machines will be on windows 2000 for
> at least a few more months. So I thought I'd throw a feeler out there
> and see if anyone has had any problems with this type of configuration.
> Thanks :)
>
SQL backups are just files to the OS, nor does the OS have anything to
do with the restore of those backups. Are you using a home-grown log
shipping method, or the wizard-driven stuff that SQL provides? Either
way, I don't foresee that you'd have any problems due to the different
OS versions.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
Subscribe to:
Posts (Atom)