Hi,
I have two servers with MS SQL Server 2000 Enterprise Edition
installed on it. These two servers are on different networks, means you
can say that these two servers are having two different network
segments.
Now, i want to configure Log Shipping on these two servers. Here
my doubt is can we setup Log Shipping on these servers.
Thanks & Regards,
MS SQL DBA.I believe so, as it's all based on tcp/ip and filesharing.
We log ship over a wan to a 3rd party data centre. We are using custom
scripts are we are using SqlLiteSpeed to compress the logs.
We have a BDC at the remote site to handle authentication.
Paul
<csajid@.gmail.com> wrote in message
news:1162464539.029111.215840@.h54g2000cwb.googlegroups.com...
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>|||csajid@.gmail.com wrote:
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>
If you can copy files between the two servers, you can log ship between
them. Log shipping is nothing more than doing a backup on Server A,
copying that backup to Server B, then restoring it on Server B.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> > Hi,
> >
> > I have two servers with MS SQL Server 2000 Enterprise Edition
> > installed on it. These two servers are on different networks, means you
> > can say that these two servers are having two different network
> > segments.
> >
> > Now, i want to configure Log Shipping on these two servers. Here
> > my doubt is can we setup Log Shipping on these servers.
> >
> >
> >
> > Thanks & Regards,
> > MS SQL DBA.
> >
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> > Hi,
> >
> > I have two servers with MS SQL Server 2000 Enterprise Edition
> > installed on it. These two servers are on different networks, means you
> > can say that these two servers are having two different network
> > segments.
> >
> > Now, i want to configure Log Shipping on these two servers. Here
> > my doubt is can we setup Log Shipping on these servers.
> >
> >
> >
> > Thanks & Regards,
> > MS SQL DBA.
> >
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||I believe file sharing in over
TCP 139
TCP 445
UDP 137
UDP 138
Make sure you can see the shared folders.
As our log shipping is based on exec'ing remote stored procs I need port
1433 for Sql Server.
Paul
<csajid@.gmail.com> wrote in message
news:1162549383.086499.183990@.h48g2000cwc.googlegroups.com...
> Hi All,
> Thanks for your reply.
> One of my concern is that, there is any need to open specific
> port to do the Log Shipping.
>
> Thanks & Regards,
> Sajid C.
> Tracy McKibben wrote:
>> csajid@.gmail.com wrote:
>> > Hi,
>> >
>> > I have two servers with MS SQL Server 2000 Enterprise Edition
>> > installed on it. These two servers are on different networks, means you
>> > can say that these two servers are having two different network
>> > segments.
>> >
>> > Now, i want to configure Log Shipping on these two servers. Here
>> > my doubt is can we setup Log Shipping on these servers.
>> >
>> >
>> >
>> > Thanks & Regards,
>> > MS SQL DBA.
>> >
>> If you can copy files between the two servers, you can log ship between
>> them. Log shipping is nothing more than doing a backup on Server A,
>> copying that backup to Server B, then restoring it on Server B.
>>
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com
>|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegroups.com...
> > Hi All,
> >
> > Thanks for your reply.
> >
> > One of my concern is that, there is any need to open specific
> > port to do the Log Shipping.
> >
> >
> > Thanks & Regards,
> > Sajid C.
> >
> > Tracy McKibben wrote:
> >> csajid@.gmail.com wrote:
> >> > Hi,
> >> >
> >> > I have two servers with MS SQL Server 2000 Enterprise Edition
> >> > installed on it. These two servers are on different networks, means you
> >> > can say that these two servers are having two different network
> >> > segments.
> >> >
> >> > Now, i want to configure Log Shipping on these two servers. Here
> >> > my doubt is can we setup Log Shipping on these servers.
> >> >
> >> >
> >> >
> >> > Thanks & Regards,
> >> > MS SQL DBA.
> >> >
> >>
> >> If you can copy files between the two servers, you can log ship between
> >> them. Log shipping is nothing more than doing a backup on Server A,
> >> copying that backup to Server B, then restoring it on Server B.
> >>
> >>
> >> --
> >> Tracy McKibben
> >> MCDBA
> >> http://www.realsqlguy.com
> >|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegroups.com...
> > Hi All,
> >
> > Thanks for your reply.
> >
> > One of my concern is that, there is any need to open specific
> > port to do the Log Shipping.
> >
> >
> > Thanks & Regards,
> > Sajid C.
> >
> > Tracy McKibben wrote:
> >> csajid@.gmail.com wrote:
> >> > Hi,
> >> >
> >> > I have two servers with MS SQL Server 2000 Enterprise Edition
> >> > installed on it. These two servers are on different networks, means you
> >> > can say that these two servers are having two different network
> >> > segments.
> >> >
> >> > Now, i want to configure Log Shipping on these two servers. Here
> >> > my doubt is can we setup Log Shipping on these servers.
> >> >
> >> >
> >> >
> >> > Thanks & Regards,
> >> > MS SQL DBA.
> >> >
> >>
> >> If you can copy files between the two servers, you can log ship between
> >> them. Log shipping is nothing more than doing a backup on Server A,
> >> copying that backup to Server B, then restoring it on Server B.
> >>
> >>
> >> --
> >> Tracy McKibben
> >> MCDBA
> >> http://www.realsqlguy.com
> >sql
Showing posts with label means. Show all posts
Showing posts with label means. Show all posts
Wednesday, March 21, 2012
Log Shipping on two different networks.
Hi,
I have two servers with MS SQL Server 2000 Enterprise Edition
installed on it. These two servers are on different networks, means you
can say that these two servers are having two different network
segments.
Now, i want to configure Log Shipping on these two servers. Here
my doubt is can we setup Log Shipping on these servers.
Thanks & Regards,
MS SQL DBA.
I believe so, as it's all based on tcp/ip and filesharing.
We log ship over a wan to a 3rd party data centre. We are using custom
scripts are we are using SqlLiteSpeed to compress the logs.
We have a BDC at the remote site to handle authentication.
Paul
<csajid@.gmail.com> wrote in message
news:1162464539.029111.215840@.h54g2000cwb.googlegr oups.com...
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>
|||csajid@.gmail.com wrote:
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>
If you can copy files between the two servers, you can log ship between
them. Log shipping is nothing more than doing a backup on Server A,
copying that backup to Server B, then restoring it on Server B.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||I believe file sharing in over
TCP 139
TCP 445
UDP 137
UDP 138
Make sure you can see the shared folders.
As our log shipping is based on exec'ing remote stored procs I need port
1433 for Sql Server.
Paul
<csajid@.gmail.com> wrote in message
news:1162549383.086499.183990@.h48g2000cwc.googlegr oups.com...
> Hi All,
> Thanks for your reply.
> One of my concern is that, there is any need to open specific
> port to do the Log Shipping.
>
> Thanks & Regards,
> Sajid C.
> Tracy McKibben wrote:
>
|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:[vbcol=seagreen]
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegr oups.com...
|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:[vbcol=seagreen]
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegr oups.com...
I have two servers with MS SQL Server 2000 Enterprise Edition
installed on it. These two servers are on different networks, means you
can say that these two servers are having two different network
segments.
Now, i want to configure Log Shipping on these two servers. Here
my doubt is can we setup Log Shipping on these servers.
Thanks & Regards,
MS SQL DBA.
I believe so, as it's all based on tcp/ip and filesharing.
We log ship over a wan to a 3rd party data centre. We are using custom
scripts are we are using SqlLiteSpeed to compress the logs.
We have a BDC at the remote site to handle authentication.
Paul
<csajid@.gmail.com> wrote in message
news:1162464539.029111.215840@.h54g2000cwb.googlegr oups.com...
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>
|||csajid@.gmail.com wrote:
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>
If you can copy files between the two servers, you can log ship between
them. Log shipping is nothing more than doing a backup on Server A,
copying that backup to Server B, then restoring it on Server B.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||I believe file sharing in over
TCP 139
TCP 445
UDP 137
UDP 138
Make sure you can see the shared folders.
As our log shipping is based on exec'ing remote stored procs I need port
1433 for Sql Server.
Paul
<csajid@.gmail.com> wrote in message
news:1162549383.086499.183990@.h48g2000cwc.googlegr oups.com...
> Hi All,
> Thanks for your reply.
> One of my concern is that, there is any need to open specific
> port to do the Log Shipping.
>
> Thanks & Regards,
> Sajid C.
> Tracy McKibben wrote:
>
|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:[vbcol=seagreen]
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegr oups.com...
|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:[vbcol=seagreen]
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegr oups.com...
Log Shipping on two different networks.
Hi,
I have two servers with MS SQL Server 2000 Enterprise Edition
installed on it. These two servers are on different networks, means you
can say that these two servers are having two different network
segments.
Now, i want to configure Log Shipping on these two servers. Here
my doubt is can we setup Log Shipping on these servers.
Thanks & Regards,
MS SQL DBA.I believe so, as it's all based on tcp/ip and filesharing.
We log ship over a wan to a 3rd party data centre. We are using custom
scripts are we are using SqlLiteSpeed to compress the logs.
We have a BDC at the remote site to handle authentication.
Paul
<csajid@.gmail.com> wrote in message
news:1162464539.029111.215840@.h54g2000cwb.googlegroups.com...
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>|||csajid@.gmail.com wrote:
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>
If you can copy files between the two servers, you can log ship between
them. Log shipping is nothing more than doing a backup on Server A,
copying that backup to Server B, then restoring it on Server B.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||I believe file sharing in over
TCP 139
TCP 445
UDP 137
UDP 138
Make sure you can see the shared folders.
As our log shipping is based on exec'ing remote stored procs I need port
1433 for Sql Server.
Paul
<csajid@.gmail.com> wrote in message
news:1162549383.086499.183990@.h48g2000cwc.googlegroups.com...
> Hi All,
> Thanks for your reply.
> One of my concern is that, there is any need to open specific
> port to do the Log Shipping.
>
> Thanks & Regards,
> Sajid C.
> Tracy McKibben wrote:
>|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:[vbcol=seagreen]
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegroups.com...|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:[vbcol=seagreen]
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegroups.com...
I have two servers with MS SQL Server 2000 Enterprise Edition
installed on it. These two servers are on different networks, means you
can say that these two servers are having two different network
segments.
Now, i want to configure Log Shipping on these two servers. Here
my doubt is can we setup Log Shipping on these servers.
Thanks & Regards,
MS SQL DBA.I believe so, as it's all based on tcp/ip and filesharing.
We log ship over a wan to a 3rd party data centre. We are using custom
scripts are we are using SqlLiteSpeed to compress the logs.
We have a BDC at the remote site to handle authentication.
Paul
<csajid@.gmail.com> wrote in message
news:1162464539.029111.215840@.h54g2000cwb.googlegroups.com...
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>|||csajid@.gmail.com wrote:
> Hi,
> I have two servers with MS SQL Server 2000 Enterprise Edition
> installed on it. These two servers are on different networks, means you
> can say that these two servers are having two different network
> segments.
> Now, i want to configure Log Shipping on these two servers. Here
> my doubt is can we setup Log Shipping on these servers.
>
> Thanks & Regards,
> MS SQL DBA.
>
If you can copy files between the two servers, you can log ship between
them. Log shipping is nothing more than doing a backup on Server A,
copying that backup to Server B, then restoring it on Server B.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Hi All,
Thanks for your reply.
One of my concern is that, there is any need to open specific
port to do the Log Shipping.
Thanks & Regards,
Sajid C.
Tracy McKibben wrote:
> csajid@.gmail.com wrote:
> If you can copy files between the two servers, you can log ship between
> them. Log shipping is nothing more than doing a backup on Server A,
> copying that backup to Server B, then restoring it on Server B.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||I believe file sharing in over
TCP 139
TCP 445
UDP 137
UDP 138
Make sure you can see the shared folders.
As our log shipping is based on exec'ing remote stored procs I need port
1433 for Sql Server.
Paul
<csajid@.gmail.com> wrote in message
news:1162549383.086499.183990@.h48g2000cwc.googlegroups.com...
> Hi All,
> Thanks for your reply.
> One of my concern is that, there is any need to open specific
> port to do the Log Shipping.
>
> Thanks & Regards,
> Sajid C.
> Tracy McKibben wrote:
>|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:[vbcol=seagreen]
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegroups.com...|||Hi Paul,
Thanks for your reply.
Thanks & Regards,
Sajid C.
Paul Cahill wrote:[vbcol=seagreen]
> I believe file sharing in over
> TCP 139
> TCP 445
> UDP 137
> UDP 138
> Make sure you can see the shared folders.
> As our log shipping is based on exec'ing remote stored procs I need port
> 1433 for Sql Server.
> Paul
>
> <csajid@.gmail.com> wrote in message
> news:1162549383.086499.183990@.h48g2000cwc.googlegroups.com...
Friday, February 24, 2012
Log shipping and database corruption
Hi,
Could anyone please explain to me how the corruption of a primary database
can be carried to the secondary database by means of the log shipping? Can
these corruptions be spotted at the secondary server? Will any error message
s
be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
-- Many thanks, OskarLog shipping will carry whatever that can be backed and restored. This may
include certain physical corruptions and all logical corruptions (i.e. with
respect to the app logic).
I don't have the exact breakdown of what corruptions do or do not lead to a
backup/restore failure or error. But it may help to DBCC the restored copy.
But in practice, I have to admit that I have not seen, for at least several
years now, a case where a corruption is caught by DBCC'ing the restored
database but not already shown up in the primary.
Linchi
"Oskar" wrote:
> Hi,
> Could anyone please explain to me how the corruption of a primary database
> can be carried to the secondary database by means of the log shipping? Can
> these corruptions be spotted at the secondary server? Will any error messa
ges
> be generated? Both the primary and the secondary are MS SQL Server 2000 SP
3.
> -- Many thanks, Oskar|||Do you also know whether every corruption that leads to data loss is logged
into the primary errorlog as soon as it happens? That would be just sensible
,
wouldn't it?
-- Oskar
"Linchi Shea" wrote:
[vbcol=seagreen]
> Log shipping will carry whatever that can be backed and restored. This may
> include certain physical corruptions and all logical corruptions (i.e. wit
h
> respect to the app logic).
> I don't have the exact breakdown of what corruptions do or do not lead to
a
> backup/restore failure or error. But it may help to DBCC the restored copy
.
> But in practice, I have to admit that I have not seen, for at least severa
l
> years now, a case where a corruption is caught by DBCC'ing the restored
> database but not already shown up in the primary.
> Linchi
> "Oskar" wrote:
>|||No, it isn't. It is logged when it is detected which is normally when the
data needs to be read back off of disk for some reason.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:37E006FF-F6B0-41E9-9FE9-C54F905940F1@.microsoft.com...[vbcol=seagreen]
> Do you also know whether every corruption that leads to data loss is
> logged
> into the primary errorlog as soon as it happens? That would be just
> sensible,
> wouldn't it?
> -- Oskar
> "Linchi Shea" wrote:
>
Could anyone please explain to me how the corruption of a primary database
can be carried to the secondary database by means of the log shipping? Can
these corruptions be spotted at the secondary server? Will any error message
s
be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
-- Many thanks, OskarLog shipping will carry whatever that can be backed and restored. This may
include certain physical corruptions and all logical corruptions (i.e. with
respect to the app logic).
I don't have the exact breakdown of what corruptions do or do not lead to a
backup/restore failure or error. But it may help to DBCC the restored copy.
But in practice, I have to admit that I have not seen, for at least several
years now, a case where a corruption is caught by DBCC'ing the restored
database but not already shown up in the primary.
Linchi
"Oskar" wrote:
> Hi,
> Could anyone please explain to me how the corruption of a primary database
> can be carried to the secondary database by means of the log shipping? Can
> these corruptions be spotted at the secondary server? Will any error messa
ges
> be generated? Both the primary and the secondary are MS SQL Server 2000 SP
3.
> -- Many thanks, Oskar|||Do you also know whether every corruption that leads to data loss is logged
into the primary errorlog as soon as it happens? That would be just sensible
,
wouldn't it?
-- Oskar
"Linchi Shea" wrote:
[vbcol=seagreen]
> Log shipping will carry whatever that can be backed and restored. This may
> include certain physical corruptions and all logical corruptions (i.e. wit
h
> respect to the app logic).
> I don't have the exact breakdown of what corruptions do or do not lead to
a
> backup/restore failure or error. But it may help to DBCC the restored copy
.
> But in practice, I have to admit that I have not seen, for at least severa
l
> years now, a case where a corruption is caught by DBCC'ing the restored
> database but not already shown up in the primary.
> Linchi
> "Oskar" wrote:
>|||No, it isn't. It is logged when it is detected which is normally when the
data needs to be read back off of disk for some reason.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:37E006FF-F6B0-41E9-9FE9-C54F905940F1@.microsoft.com...[vbcol=seagreen]
> Do you also know whether every corruption that leads to data loss is
> logged
> into the primary errorlog as soon as it happens? That would be just
> sensible,
> wouldn't it?
> -- Oskar
> "Linchi Shea" wrote:
>
Log shipping and database corruption
Hi,
Could anyone please explain to me how the corruption of a primary database
can be carried to the secondary database by means of the log shipping? Can
these corruptions be spotted at the secondary server? Will any error messages
be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
-- Many thanks, Oskar
Log shipping will carry whatever that can be backed and restored. This may
include certain physical corruptions and all logical corruptions (i.e. with
respect to the app logic).
I don't have the exact breakdown of what corruptions do or do not lead to a
backup/restore failure or error. But it may help to DBCC the restored copy.
But in practice, I have to admit that I have not seen, for at least several
years now, a case where a corruption is caught by DBCC'ing the restored
database but not already shown up in the primary.
Linchi
"Oskar" wrote:
> Hi,
> Could anyone please explain to me how the corruption of a primary database
> can be carried to the secondary database by means of the log shipping? Can
> these corruptions be spotted at the secondary server? Will any error messages
> be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
> -- Many thanks, Oskar
|||Do you also know whether every corruption that leads to data loss is logged
into the primary errorlog as soon as it happens? That would be just sensible,
wouldn't it?
-- Oskar
"Linchi Shea" wrote:
[vbcol=seagreen]
> Log shipping will carry whatever that can be backed and restored. This may
> include certain physical corruptions and all logical corruptions (i.e. with
> respect to the app logic).
> I don't have the exact breakdown of what corruptions do or do not lead to a
> backup/restore failure or error. But it may help to DBCC the restored copy.
> But in practice, I have to admit that I have not seen, for at least several
> years now, a case where a corruption is caught by DBCC'ing the restored
> database but not already shown up in the primary.
> Linchi
> "Oskar" wrote:
|||No, it isn't. It is logged when it is detected which is normally when the
data needs to be read back off of disk for some reason.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:37E006FF-F6B0-41E9-9FE9-C54F905940F1@.microsoft.com...[vbcol=seagreen]
> Do you also know whether every corruption that leads to data loss is
> logged
> into the primary errorlog as soon as it happens? That would be just
> sensible,
> wouldn't it?
> -- Oskar
> "Linchi Shea" wrote:
Could anyone please explain to me how the corruption of a primary database
can be carried to the secondary database by means of the log shipping? Can
these corruptions be spotted at the secondary server? Will any error messages
be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
-- Many thanks, Oskar
Log shipping will carry whatever that can be backed and restored. This may
include certain physical corruptions and all logical corruptions (i.e. with
respect to the app logic).
I don't have the exact breakdown of what corruptions do or do not lead to a
backup/restore failure or error. But it may help to DBCC the restored copy.
But in practice, I have to admit that I have not seen, for at least several
years now, a case where a corruption is caught by DBCC'ing the restored
database but not already shown up in the primary.
Linchi
"Oskar" wrote:
> Hi,
> Could anyone please explain to me how the corruption of a primary database
> can be carried to the secondary database by means of the log shipping? Can
> these corruptions be spotted at the secondary server? Will any error messages
> be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
> -- Many thanks, Oskar
|||Do you also know whether every corruption that leads to data loss is logged
into the primary errorlog as soon as it happens? That would be just sensible,
wouldn't it?
-- Oskar
"Linchi Shea" wrote:
[vbcol=seagreen]
> Log shipping will carry whatever that can be backed and restored. This may
> include certain physical corruptions and all logical corruptions (i.e. with
> respect to the app logic).
> I don't have the exact breakdown of what corruptions do or do not lead to a
> backup/restore failure or error. But it may help to DBCC the restored copy.
> But in practice, I have to admit that I have not seen, for at least several
> years now, a case where a corruption is caught by DBCC'ing the restored
> database but not already shown up in the primary.
> Linchi
> "Oskar" wrote:
|||No, it isn't. It is logged when it is detected which is normally when the
data needs to be read back off of disk for some reason.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:37E006FF-F6B0-41E9-9FE9-C54F905940F1@.microsoft.com...[vbcol=seagreen]
> Do you also know whether every corruption that leads to data loss is
> logged
> into the primary errorlog as soon as it happens? That would be just
> sensible,
> wouldn't it?
> -- Oskar
> "Linchi Shea" wrote:
Log shipping and database corruption
Hi,
Could anyone please explain to me how the corruption of a primary database
can be carried to the secondary database by means of the log shipping? Can
these corruptions be spotted at the secondary server? Will any error messages
be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
-- Many thanks, OskarLog shipping will carry whatever that can be backed and restored. This may
include certain physical corruptions and all logical corruptions (i.e. with
respect to the app logic).
I don't have the exact breakdown of what corruptions do or do not lead to a
backup/restore failure or error. But it may help to DBCC the restored copy.
But in practice, I have to admit that I have not seen, for at least several
years now, a case where a corruption is caught by DBCC'ing the restored
database but not already shown up in the primary.
Linchi
"Oskar" wrote:
> Hi,
> Could anyone please explain to me how the corruption of a primary database
> can be carried to the secondary database by means of the log shipping? Can
> these corruptions be spotted at the secondary server? Will any error messages
> be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
> -- Many thanks, Oskar|||Do you also know whether every corruption that leads to data loss is logged
into the primary errorlog as soon as it happens? That would be just sensible,
wouldn't it?
-- Oskar
"Linchi Shea" wrote:
> Log shipping will carry whatever that can be backed and restored. This may
> include certain physical corruptions and all logical corruptions (i.e. with
> respect to the app logic).
> I don't have the exact breakdown of what corruptions do or do not lead to a
> backup/restore failure or error. But it may help to DBCC the restored copy.
> But in practice, I have to admit that I have not seen, for at least several
> years now, a case where a corruption is caught by DBCC'ing the restored
> database but not already shown up in the primary.
> Linchi
> "Oskar" wrote:
> > Hi,
> > Could anyone please explain to me how the corruption of a primary database
> > can be carried to the secondary database by means of the log shipping? Can
> > these corruptions be spotted at the secondary server? Will any error messages
> > be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
> >
> > -- Many thanks, Oskar|||No, it isn't. It is logged when it is detected which is normally when the
data needs to be read back off of disk for some reason.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:37E006FF-F6B0-41E9-9FE9-C54F905940F1@.microsoft.com...
> Do you also know whether every corruption that leads to data loss is
> logged
> into the primary errorlog as soon as it happens? That would be just
> sensible,
> wouldn't it?
> -- Oskar
> "Linchi Shea" wrote:
>> Log shipping will carry whatever that can be backed and restored. This
>> may
>> include certain physical corruptions and all logical corruptions (i.e.
>> with
>> respect to the app logic).
>> I don't have the exact breakdown of what corruptions do or do not lead to
>> a
>> backup/restore failure or error. But it may help to DBCC the restored
>> copy.
>> But in practice, I have to admit that I have not seen, for at least
>> several
>> years now, a case where a corruption is caught by DBCC'ing the restored
>> database but not already shown up in the primary.
>> Linchi
>> "Oskar" wrote:
>> > Hi,
>> > Could anyone please explain to me how the corruption of a primary
>> > database
>> > can be carried to the secondary database by means of the log shipping?
>> > Can
>> > these corruptions be spotted at the secondary server? Will any error
>> > messages
>> > be generated? Both the primary and the secondary are MS SQL Server 2000
>> > SP3.
>> >
>> > -- Many thanks, Oskar
Could anyone please explain to me how the corruption of a primary database
can be carried to the secondary database by means of the log shipping? Can
these corruptions be spotted at the secondary server? Will any error messages
be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
-- Many thanks, OskarLog shipping will carry whatever that can be backed and restored. This may
include certain physical corruptions and all logical corruptions (i.e. with
respect to the app logic).
I don't have the exact breakdown of what corruptions do or do not lead to a
backup/restore failure or error. But it may help to DBCC the restored copy.
But in practice, I have to admit that I have not seen, for at least several
years now, a case where a corruption is caught by DBCC'ing the restored
database but not already shown up in the primary.
Linchi
"Oskar" wrote:
> Hi,
> Could anyone please explain to me how the corruption of a primary database
> can be carried to the secondary database by means of the log shipping? Can
> these corruptions be spotted at the secondary server? Will any error messages
> be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
> -- Many thanks, Oskar|||Do you also know whether every corruption that leads to data loss is logged
into the primary errorlog as soon as it happens? That would be just sensible,
wouldn't it?
-- Oskar
"Linchi Shea" wrote:
> Log shipping will carry whatever that can be backed and restored. This may
> include certain physical corruptions and all logical corruptions (i.e. with
> respect to the app logic).
> I don't have the exact breakdown of what corruptions do or do not lead to a
> backup/restore failure or error. But it may help to DBCC the restored copy.
> But in practice, I have to admit that I have not seen, for at least several
> years now, a case where a corruption is caught by DBCC'ing the restored
> database but not already shown up in the primary.
> Linchi
> "Oskar" wrote:
> > Hi,
> > Could anyone please explain to me how the corruption of a primary database
> > can be carried to the secondary database by means of the log shipping? Can
> > these corruptions be spotted at the secondary server? Will any error messages
> > be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
> >
> > -- Many thanks, Oskar|||No, it isn't. It is logged when it is detected which is normally when the
data needs to be read back off of disk for some reason.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:37E006FF-F6B0-41E9-9FE9-C54F905940F1@.microsoft.com...
> Do you also know whether every corruption that leads to data loss is
> logged
> into the primary errorlog as soon as it happens? That would be just
> sensible,
> wouldn't it?
> -- Oskar
> "Linchi Shea" wrote:
>> Log shipping will carry whatever that can be backed and restored. This
>> may
>> include certain physical corruptions and all logical corruptions (i.e.
>> with
>> respect to the app logic).
>> I don't have the exact breakdown of what corruptions do or do not lead to
>> a
>> backup/restore failure or error. But it may help to DBCC the restored
>> copy.
>> But in practice, I have to admit that I have not seen, for at least
>> several
>> years now, a case where a corruption is caught by DBCC'ing the restored
>> database but not already shown up in the primary.
>> Linchi
>> "Oskar" wrote:
>> > Hi,
>> > Could anyone please explain to me how the corruption of a primary
>> > database
>> > can be carried to the secondary database by means of the log shipping?
>> > Can
>> > these corruptions be spotted at the secondary server? Will any error
>> > messages
>> > be generated? Both the primary and the secondary are MS SQL Server 2000
>> > SP3.
>> >
>> > -- Many thanks, Oskar
Subscribe to:
Posts (Atom)