Hi,
We have specific problem here. We have very large database (1TB) on one
server, and we need to set up log shipping to another server. Problem is that
we don't make regular sql server backups on the source server because of
obvious reason (it would take too long). Therefore we cannot restore database
in standby mode on the standby server. The only way to do database restore in
our case is to use BCV software (disk subsystem on both servers is EMC), and
that software doesn't have option od leaving database in standby mode. My
question is "is there any way to put database into standby mode, regardless
that is hasn't been restored using sql server native restore procedure?".
Servers are sql server 2000, service pack 3.
ThanksEven if you could put it into Standby mode, you wouldnt be able to apply
additional changes without TLog backups. I dont know if there is an option of
new software or not? If so, I wrote my own Log Shipping using SQL Lite Speed.
"Pedja" wrote:
> Hi,
> We have specific problem here. We have very large database (1TB) on one
> server, and we need to set up log shipping to another server. Problem is that
> we don't make regular sql server backups on the source server because of
> obvious reason (it would take too long). Therefore we cannot restore database
> in standby mode on the standby server. The only way to do database restore in
> our case is to use BCV software (disk subsystem on both servers is EMC), and
> that software doesn't have option od leaving database in standby mode. My
> question is "is there any way to put database into standby mode, regardless
> that is hasn't been restored using sql server native restore procedure?".
> Servers are sql server 2000, service pack 3.
> Thanks|||Transaction log backups are OK for this scenario. I would be able to backup
transaction log i.e. every 2 hours, copy tl backup to the new sever, and
restore it there. It is full database backup that I cannot apply in this
scenario, because it would take too long. So if I could set secondary
database which is restored using BCV (not native backup), to standby mode,
I'd be able to apply log shipping scenario.
Even LiteSpeed wouldn't help. This database doesn't have much text fields,
so I don't think that compression would be that good. Even if I'd get 50%
compression in database backup file and time needed to restore, it is still
500GB... BTW, BCV restore of 1TB database takes 2-3 hours. Using litespeed,
it would take hours to backup, hours to copy, and hours to restore...
"ChrisR" wrote:
> Even if you could put it into Standby mode, you wouldnt be able to apply
> additional changes without TLog backups. I dont know if there is an option of
> new software or not? If so, I wrote my own Log Shipping using SQL Lite Speed.
> "Pedja" wrote:
> > Hi,
> > We have specific problem here. We have very large database (1TB) on one
> > server, and we need to set up log shipping to another server. Problem is that
> > we don't make regular sql server backups on the source server because of
> > obvious reason (it would take too long). Therefore we cannot restore database
> > in standby mode on the standby server. The only way to do database restore in
> > our case is to use BCV software (disk subsystem on both servers is EMC), and
> > that software doesn't have option od leaving database in standby mode. My
> > question is "is there any way to put database into standby mode, regardless
> > that is hasn't been restored using sql server native restore procedure?".
> > Servers are sql server 2000, service pack 3.
> > Thanks|||We have a large database that we ship from a remote location as well. What I
did in this was to take a back up(Lite Speed) restore on stand by one time,
then continue with the logs. You do not have to do a full restore daily. When
you restore your transaction logs could you restore on stand by. (We use Lite
Speed Tranasction log as well). What we do is take a nightly backup, and copy
it over so that we have full back up for an emergency, but we never restore
them. It is harmless that backup takes long(you can schedule it for night
time). I have not noticed and significant performance trouble due to back up
in production.
> Transaction log backups are OK for this scenario. I would be able to backup
> transaction log i.e. every 2 hours, copy tl backup to the new sever, and
> restore it there. It is full database backup that I cannot apply in this
> scenario, because it would take too long. So if I could set secondary
> database which is restored using BCV (not native backup), to standby mode,
> I'd be able to apply log shipping scenario.
> Even LiteSpeed wouldn't help. This database doesn't have much text fields,
> so I don't think that compression would be that good. Even if I'd get 50%
> compression in database backup file and time needed to restore, it is still
> 500GB... BTW, BCV restore of 1TB database takes 2-3 hours. Using litespeed,
> it would take hours to backup, hours to copy, and hours to restore...
> "ChrisR" wrote:
> > Even if you could put it into Standby mode, you wouldnt be able to apply
> > additional changes without TLog backups. I dont know if there is an option of
> > new software or not? If so, I wrote my own Log Shipping using SQL Lite Speed.
> >
> > "Pedja" wrote:
> >
> > > Hi,
> > > We have specific problem here. We have very large database (1TB) on one
> > > server, and we need to set up log shipping to another server. Problem is that
> > > we don't make regular sql server backups on the source server because of
> > > obvious reason (it would take too long). Therefore we cannot restore database
> > > in standby mode on the standby server. The only way to do database restore in
> > > our case is to use BCV software (disk subsystem on both servers is EMC), and
> > > that software doesn't have option od leaving database in standby mode. My
> > > question is "is there any way to put database into standby mode, regardless
> > > that is hasn't been restored using sql server native restore procedure?".
> > > Servers are sql server 2000, service pack 3.
> > > Thanks
Friday, March 30, 2012
log shipping without backing up and restoring the whole database
Hi,
We have specific problem here. We have very large database (1TB) on one
server, and we need to set up log shipping to another server. Problem is tha
t
we don't make regular sql server backups on the source server because of
obvious reason (it would take too long). Therefore we cannot restore databas
e
in standby mode on the standby server. The only way to do database restore i
n
our case is to use BCV software (disk subsystem on both servers is EMC), and
that software doesn't have option od leaving database in standby mode. My
question is "is there any way to put database into standby mode, regardless
that is hasn't been restored using sql server native restore procedure?".
Servers are sql server 2000, service pack 3.
ThanksEven if you could put it into Standby mode, you wouldnt be able to apply
additional changes without TLog backups. I dont know if there is an option o
f
new software or not? If so, I wrote my own Log Shipping using SQL Lite Speed
.
"Pedja" wrote:
> Hi,
> We have specific problem here. We have very large database (1TB) on one
> server, and we need to set up log shipping to another server. Problem is t
hat
> we don't make regular sql server backups on the source server because of
> obvious reason (it would take too long). Therefore we cannot restore datab
ase
> in standby mode on the standby server. The only way to do database restore
in
> our case is to use BCV software (disk subsystem on both servers is EMC), a
nd
> that software doesn't have option od leaving database in standby mode. My
> question is "is there any way to put database into standby mode, regardles
s
> that is hasn't been restored using sql server native restore procedure?".
> Servers are sql server 2000, service pack 3.
> Thankssql
We have specific problem here. We have very large database (1TB) on one
server, and we need to set up log shipping to another server. Problem is tha
t
we don't make regular sql server backups on the source server because of
obvious reason (it would take too long). Therefore we cannot restore databas
e
in standby mode on the standby server. The only way to do database restore i
n
our case is to use BCV software (disk subsystem on both servers is EMC), and
that software doesn't have option od leaving database in standby mode. My
question is "is there any way to put database into standby mode, regardless
that is hasn't been restored using sql server native restore procedure?".
Servers are sql server 2000, service pack 3.
ThanksEven if you could put it into Standby mode, you wouldnt be able to apply
additional changes without TLog backups. I dont know if there is an option o
f
new software or not? If so, I wrote my own Log Shipping using SQL Lite Speed
.
"Pedja" wrote:
> Hi,
> We have specific problem here. We have very large database (1TB) on one
> server, and we need to set up log shipping to another server. Problem is t
hat
> we don't make regular sql server backups on the source server because of
> obvious reason (it would take too long). Therefore we cannot restore datab
ase
> in standby mode on the standby server. The only way to do database restore
in
> our case is to use BCV software (disk subsystem on both servers is EMC), a
nd
> that software doesn't have option od leaving database in standby mode. My
> question is "is there any way to put database into standby mode, regardles
s
> that is hasn't been restored using sql server native restore procedure?".
> Servers are sql server 2000, service pack 3.
> Thankssql
log shipping without backing up and restoring the whole database
Hi,
We have specific problem here. We have very large database (1TB) on one
server, and we need to set up log shipping to another server. Problem is that
we don't make regular sql server backups on the source server because of
obvious reason (it would take too long). Therefore we cannot restore database
in standby mode on the standby server. The only way to do database restore in
our case is to use BCV software (disk subsystem on both servers is EMC), and
that software doesn't have option od leaving database in standby mode. My
question is "is there any way to put database into standby mode, regardless
that is hasn't been restored using sql server native restore procedure?".
Servers are sql server 2000, service pack 3.
Thanks
Even if you could put it into Standby mode, you wouldnt be able to apply
additional changes without TLog backups. I dont know if there is an option of
new software or not? If so, I wrote my own Log Shipping using SQL Lite Speed.
"Pedja" wrote:
> Hi,
> We have specific problem here. We have very large database (1TB) on one
> server, and we need to set up log shipping to another server. Problem is that
> we don't make regular sql server backups on the source server because of
> obvious reason (it would take too long). Therefore we cannot restore database
> in standby mode on the standby server. The only way to do database restore in
> our case is to use BCV software (disk subsystem on both servers is EMC), and
> that software doesn't have option od leaving database in standby mode. My
> question is "is there any way to put database into standby mode, regardless
> that is hasn't been restored using sql server native restore procedure?".
> Servers are sql server 2000, service pack 3.
> Thanks
We have specific problem here. We have very large database (1TB) on one
server, and we need to set up log shipping to another server. Problem is that
we don't make regular sql server backups on the source server because of
obvious reason (it would take too long). Therefore we cannot restore database
in standby mode on the standby server. The only way to do database restore in
our case is to use BCV software (disk subsystem on both servers is EMC), and
that software doesn't have option od leaving database in standby mode. My
question is "is there any way to put database into standby mode, regardless
that is hasn't been restored using sql server native restore procedure?".
Servers are sql server 2000, service pack 3.
Thanks
Even if you could put it into Standby mode, you wouldnt be able to apply
additional changes without TLog backups. I dont know if there is an option of
new software or not? If so, I wrote my own Log Shipping using SQL Lite Speed.
"Pedja" wrote:
> Hi,
> We have specific problem here. We have very large database (1TB) on one
> server, and we need to set up log shipping to another server. Problem is that
> we don't make regular sql server backups on the source server because of
> obvious reason (it would take too long). Therefore we cannot restore database
> in standby mode on the standby server. The only way to do database restore in
> our case is to use BCV software (disk subsystem on both servers is EMC), and
> that software doesn't have option od leaving database in standby mode. My
> question is "is there any way to put database into standby mode, regardless
> that is hasn't been restored using sql server native restore procedure?".
> Servers are sql server 2000, service pack 3.
> Thanks
Log Shipping with two production servers
I have two SQL Server databases, each with their own server. Is it suitable
to implement log shipping from each server to the other i.e. rather than
having the standard set up with a production server and a standby server, I
will set it up with two production servers 'swapping' logs...?
Hi,
Instead of "swapping logs" you might want to implement merge
replication, however you don't give a case for why you want to
implement log shipping. Is it for a hot standby (you could setup
clustering) or do you plan to utilise one server for reporting
purposes?
Also the official line from MS is that to implement log shipping both
SQL Server Editions should be Enterprise Version, however if you can
get hold of the SQL Server 2000 Resource Kit there is a Simple Log
Shipper Tool (basically two stored procs) on there. However with the
Enterprise methond it does monitor the log shipping for you. The only
disclaimer is that I could get SLS to work in a dev environment but not
in our production setup, so we went with snapshot replication.
Good Luck
Scott
|||Hi
You can't use log shipping for Scale Out as the destination DB can not be
used for write activities.
If you need to impliment something like scale out, look at replication, but
replication could use more resources than what you might gain by off loading
a server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike" wrote:
> I have two SQL Server databases, each with their own server. Is it suitable
> to implement log shipping from each server to the other i.e. rather than
> having the standard set up with a production server and a standby server, I
> will set it up with two production servers 'swapping' logs...?
>
>
to implement log shipping from each server to the other i.e. rather than
having the standard set up with a production server and a standby server, I
will set it up with two production servers 'swapping' logs...?
Hi,
Instead of "swapping logs" you might want to implement merge
replication, however you don't give a case for why you want to
implement log shipping. Is it for a hot standby (you could setup
clustering) or do you plan to utilise one server for reporting
purposes?
Also the official line from MS is that to implement log shipping both
SQL Server Editions should be Enterprise Version, however if you can
get hold of the SQL Server 2000 Resource Kit there is a Simple Log
Shipper Tool (basically two stored procs) on there. However with the
Enterprise methond it does monitor the log shipping for you. The only
disclaimer is that I could get SLS to work in a dev environment but not
in our production setup, so we went with snapshot replication.
Good Luck
Scott
|||Hi
You can't use log shipping for Scale Out as the destination DB can not be
used for write activities.
If you need to impliment something like scale out, look at replication, but
replication could use more resources than what you might gain by off loading
a server.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike" wrote:
> I have two SQL Server databases, each with their own server. Is it suitable
> to implement log shipping from each server to the other i.e. rather than
> having the standard set up with a production server and a standby server, I
> will set it up with two production servers 'swapping' logs...?
>
>
Log Shipping with two production servers
I have two SQL Server databases, each with their own server. Is it suitable
to implement log shipping from each server to the other i.e. rather than
having the standard set up with a production server and a standby server, I
will set it up with two production servers 'swapping' logs...?Hi,
Instead of "swapping logs" you might want to implement merge
replication, however you don't give a case for why you want to
implement log shipping. Is it for a hot standby (you could setup
clustering) or do you plan to utilise one server for reporting
purposes?
Also the official line from MS is that to implement log shipping both
SQL Server Editions should be Enterprise Version, however if you can
get hold of the SQL Server 2000 Resource Kit there is a Simple Log
Shipper Tool (basically two stored procs) on there. However with the
Enterprise methond it does monitor the log shipping for you. The only
disclaimer is that I could get SLS to work in a dev environment but not
in our production setup, so we went with snapshot replication.
Good Luck
Scott|||Hi
You can't use log shipping for Scale Out as the destination DB can not be
used for write activities.
If you need to impliment something like scale out, look at replication, but
replication could use more resources than what you might gain by off loading
a server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike" wrote:
> I have two SQL Server databases, each with their own server. Is it suitabl
e
> to implement log shipping from each server to the other i.e. rather than
> having the standard set up with a production server and a standby server,
I
> will set it up with two production servers 'swapping' logs...?
>
>
to implement log shipping from each server to the other i.e. rather than
having the standard set up with a production server and a standby server, I
will set it up with two production servers 'swapping' logs...?Hi,
Instead of "swapping logs" you might want to implement merge
replication, however you don't give a case for why you want to
implement log shipping. Is it for a hot standby (you could setup
clustering) or do you plan to utilise one server for reporting
purposes?
Also the official line from MS is that to implement log shipping both
SQL Server Editions should be Enterprise Version, however if you can
get hold of the SQL Server 2000 Resource Kit there is a Simple Log
Shipper Tool (basically two stored procs) on there. However with the
Enterprise methond it does monitor the log shipping for you. The only
disclaimer is that I could get SLS to work in a dev environment but not
in our production setup, so we went with snapshot replication.
Good Luck
Scott|||Hi
You can't use log shipping for Scale Out as the destination DB can not be
used for write activities.
If you need to impliment something like scale out, look at replication, but
replication could use more resources than what you might gain by off loading
a server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike" wrote:
> I have two SQL Server databases, each with their own server. Is it suitabl
e
> to implement log shipping from each server to the other i.e. rather than
> having the standard set up with a production server and a standby server,
I
> will set it up with two production servers 'swapping' logs...?
>
>
Log Shipping with two production servers
I have two SQL Server databases, each with their own server. Is it suitable
to implement log shipping from each server to the other i.e. rather than
having the standard set up with a production server and a standby server, I
will set it up with two production servers 'swapping' logs...?Hi,
Instead of "swapping logs" you might want to implement merge
replication, however you don't give a case for why you want to
implement log shipping. Is it for a hot standby (you could setup
clustering) or do you plan to utilise one server for reporting
purposes?
Also the official line from MS is that to implement log shipping both
SQL Server Editions should be Enterprise Version, however if you can
get hold of the SQL Server 2000 Resource Kit there is a Simple Log
Shipper Tool (basically two stored procs) on there. However with the
Enterprise methond it does monitor the log shipping for you. The only
disclaimer is that I could get SLS to work in a dev environment but not
in our production setup, so we went with snapshot replication.
Good Luck
Scott|||Hi
You can't use log shipping for Scale Out as the destination DB can not be
used for write activities.
If you need to impliment something like scale out, look at replication, but
replication could use more resources than what you might gain by off loading
a server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike" wrote:
> I have two SQL Server databases, each with their own server. Is it suitable
> to implement log shipping from each server to the other i.e. rather than
> having the standard set up with a production server and a standby server, I
> will set it up with two production servers 'swapping' logs...?
>
>
to implement log shipping from each server to the other i.e. rather than
having the standard set up with a production server and a standby server, I
will set it up with two production servers 'swapping' logs...?Hi,
Instead of "swapping logs" you might want to implement merge
replication, however you don't give a case for why you want to
implement log shipping. Is it for a hot standby (you could setup
clustering) or do you plan to utilise one server for reporting
purposes?
Also the official line from MS is that to implement log shipping both
SQL Server Editions should be Enterprise Version, however if you can
get hold of the SQL Server 2000 Resource Kit there is a Simple Log
Shipper Tool (basically two stored procs) on there. However with the
Enterprise methond it does monitor the log shipping for you. The only
disclaimer is that I could get SLS to work in a dev environment but not
in our production setup, so we went with snapshot replication.
Good Luck
Scott|||Hi
You can't use log shipping for Scale Out as the destination DB can not be
used for write activities.
If you need to impliment something like scale out, look at replication, but
replication could use more resources than what you might gain by off loading
a server.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mike" wrote:
> I have two SQL Server databases, each with their own server. Is it suitable
> to implement log shipping from each server to the other i.e. rather than
> having the standard set up with a production server and a standby server, I
> will set it up with two production servers 'swapping' logs...?
>
>
Log Shipping with SQL Server 2000 STD Edition?
Hi SQL Server MVPs,
I just get into a sql server 2000 (std edition) environment, and they will
stay with the std edition for a while. Here are some questions about the Log
shipping:
1. Does SQL server 2000 STD version support Log Shipping?
(I know EE Edition and Developer Edition do.)
2. If tasks like the Transaction Log backup, transfering log from primary
server to secondary server, restore the log from the standby server were all
handled by scheduled scripts, and the syslogins was transfered by DTS, will
this approach work in a SQL server 2k std environment? Will the logins
resolving process work?
3. How can we setup the Log shipping monitor in SQL 2000 STD server?
Your expertise confirming information and any possible instruction documents
will be appreciated.
FD
Hi,
(a) Log-shipping is not supported in standard version of SQL server. However
I have read that basic log-shipping is supported in the standard version,
didn't get chance to get to know more about this.
(b) IMO, this approach should work, as long as the database is in the
NORECOVERY mode in the standby server.
HTH
Yogish
|||The Enterprise Edition (and dev) just have a wizard to set
it all up for you. It doesn't mean you can't write your own
version on any edition. You can find sample scripts in the
SQL Server Resource Kit - I think it's called Simple Log
Shipper. You can also find examples of implementations of
custom log shipping routines on various web sites.
You'll need to create your own method for monitoring log
shipping.
-Sue
On Wed, 16 Mar 2005 14:43:07 -0800, "Frank"
<Frank@.discussions.microsoft.com> wrote:
>Hi SQL Server MVPs,
>I just get into a sql server 2000 (std edition) environment, and they will
>stay with the std edition for a while. Here are some questions about the Log
>shipping:
>1. Does SQL server 2000 STD version support Log Shipping?
> (I know EE Edition and Developer Edition do.)
>2. If tasks like the Transaction Log backup, transfering log from primary
>server to secondary server, restore the log from the standby server were all
>handled by scheduled scripts, and the syslogins was transfered by DTS, will
>this approach work in a SQL server 2k std environment? Will the logins
>resolving process work?
>3. How can we setup the Log shipping monitor in SQL 2000 STD server?
>Your expertise confirming information and any possible instruction documents
>will be appreciated.
>FD
|||1) Yes. You have to set it up yourself, however.
2) Yes and Yes. By the way, you can move the logins using this method:
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
3) To monitor the process you could use the jobs that perform the log
backups and restores. Have them email you if there is a failure. This is a
great way to email from SQL Server: XPSMTP --
http://sqldev.net/xp/xpsmtp.htm
You may find these KB articles helpful:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
Keith
"Frank" <Frank@.discussions.microsoft.com> wrote in message
news:BBB0D86B-D4C9-4FFA-A496-C60FE8DEE0D3@.microsoft.com...
> Hi SQL Server MVPs,
> I just get into a sql server 2000 (std edition) environment, and they will
> stay with the std edition for a while. Here are some questions about the
Log
> shipping:
> 1. Does SQL server 2000 STD version support Log Shipping?
> (I know EE Edition and Developer Edition do.)
> 2. If tasks like the Transaction Log backup, transfering log from primary
> server to secondary server, restore the log from the standby server were
all
> handled by scheduled scripts, and the syslogins was transfered by DTS,
will
> this approach work in a SQL server 2k std environment? Will the logins
> resolving process work?
> 3. How can we setup the Log shipping monitor in SQL 2000 STD server?
> Your expertise confirming information and any possible instruction
documents
> will be appreciated.
> FD
|||All,
Thanks for the confirming information. I will start working in our testing
environment.
Frank
"Frank" wrote:
> Hi SQL Server MVPs,
> I just get into a sql server 2000 (std edition) environment, and they will
> stay with the std edition for a while. Here are some questions about the Log
> shipping:
> 1. Does SQL server 2000 STD version support Log Shipping?
> (I know EE Edition and Developer Edition do.)
> 2. If tasks like the Transaction Log backup, transfering log from primary
> server to secondary server, restore the log from the standby server were all
> handled by scheduled scripts, and the syslogins was transfered by DTS, will
> this approach work in a SQL server 2k std environment? Will the logins
> resolving process work?
> 3. How can we setup the Log shipping monitor in SQL 2000 STD server?
> Your expertise confirming information and any possible instruction documents
> will be appreciated.
> FD
sql
I just get into a sql server 2000 (std edition) environment, and they will
stay with the std edition for a while. Here are some questions about the Log
shipping:
1. Does SQL server 2000 STD version support Log Shipping?
(I know EE Edition and Developer Edition do.)
2. If tasks like the Transaction Log backup, transfering log from primary
server to secondary server, restore the log from the standby server were all
handled by scheduled scripts, and the syslogins was transfered by DTS, will
this approach work in a SQL server 2k std environment? Will the logins
resolving process work?
3. How can we setup the Log shipping monitor in SQL 2000 STD server?
Your expertise confirming information and any possible instruction documents
will be appreciated.
FD
Hi,
(a) Log-shipping is not supported in standard version of SQL server. However
I have read that basic log-shipping is supported in the standard version,
didn't get chance to get to know more about this.
(b) IMO, this approach should work, as long as the database is in the
NORECOVERY mode in the standby server.
HTH
Yogish
|||The Enterprise Edition (and dev) just have a wizard to set
it all up for you. It doesn't mean you can't write your own
version on any edition. You can find sample scripts in the
SQL Server Resource Kit - I think it's called Simple Log
Shipper. You can also find examples of implementations of
custom log shipping routines on various web sites.
You'll need to create your own method for monitoring log
shipping.
-Sue
On Wed, 16 Mar 2005 14:43:07 -0800, "Frank"
<Frank@.discussions.microsoft.com> wrote:
>Hi SQL Server MVPs,
>I just get into a sql server 2000 (std edition) environment, and they will
>stay with the std edition for a while. Here are some questions about the Log
>shipping:
>1. Does SQL server 2000 STD version support Log Shipping?
> (I know EE Edition and Developer Edition do.)
>2. If tasks like the Transaction Log backup, transfering log from primary
>server to secondary server, restore the log from the standby server were all
>handled by scheduled scripts, and the syslogins was transfered by DTS, will
>this approach work in a SQL server 2k std environment? Will the logins
>resolving process work?
>3. How can we setup the Log shipping monitor in SQL 2000 STD server?
>Your expertise confirming information and any possible instruction documents
>will be appreciated.
>FD
|||1) Yes. You have to set it up yourself, however.
2) Yes and Yes. By the way, you can move the logins using this method:
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
3) To monitor the process you could use the jobs that perform the log
backups and restores. Have them email you if there is a failure. This is a
great way to email from SQL Server: XPSMTP --
http://sqldev.net/xp/xpsmtp.htm
You may find these KB articles helpful:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
Keith
"Frank" <Frank@.discussions.microsoft.com> wrote in message
news:BBB0D86B-D4C9-4FFA-A496-C60FE8DEE0D3@.microsoft.com...
> Hi SQL Server MVPs,
> I just get into a sql server 2000 (std edition) environment, and they will
> stay with the std edition for a while. Here are some questions about the
Log
> shipping:
> 1. Does SQL server 2000 STD version support Log Shipping?
> (I know EE Edition and Developer Edition do.)
> 2. If tasks like the Transaction Log backup, transfering log from primary
> server to secondary server, restore the log from the standby server were
all
> handled by scheduled scripts, and the syslogins was transfered by DTS,
will
> this approach work in a SQL server 2k std environment? Will the logins
> resolving process work?
> 3. How can we setup the Log shipping monitor in SQL 2000 STD server?
> Your expertise confirming information and any possible instruction
documents
> will be appreciated.
> FD
|||All,
Thanks for the confirming information. I will start working in our testing
environment.
Frank
"Frank" wrote:
> Hi SQL Server MVPs,
> I just get into a sql server 2000 (std edition) environment, and they will
> stay with the std edition for a while. Here are some questions about the Log
> shipping:
> 1. Does SQL server 2000 STD version support Log Shipping?
> (I know EE Edition and Developer Edition do.)
> 2. If tasks like the Transaction Log backup, transfering log from primary
> server to secondary server, restore the log from the standby server were all
> handled by scheduled scripts, and the syslogins was transfered by DTS, will
> this approach work in a SQL server 2k std environment? Will the logins
> resolving process work?
> 3. How can we setup the Log shipping monitor in SQL 2000 STD server?
> Your expertise confirming information and any possible instruction documents
> will be appreciated.
> FD
sql
Subscribe to:
Posts (Atom)