I'm trying to implement Log Shipping to my database but I
am running SQL Server Standard. I understand that SQL
Enterprise edition has this built into it, but we
currently can't perform an upgrade. How can I do this in
the standard edition, or how can I get access to the jobs
and store procedures or any other objects that get
created using the enterprise edtion so that I can
implement log shipping using the standard edition?
Thanks in advanced,
Vichttp://www.sql-server-performance.com/sql_server_log_shipping.asp
"Vic" <vduran@.specpro-inc.com> wrote in message
news:025b01c3d496$d9112bf0$a401280a@.phx.gbl...
> I'm trying to implement Log Shipping to my database but I
> am running SQL Server Standard. I understand that SQL
> Enterprise edition has this built into it, but we
> currently can't perform an upgrade. How can I do this in
> the standard edition, or how can I get access to the jobs
> and store procedures or any other objects that get
> created using the enterprise edtion so that I can
> implement log shipping using the standard edition?
> Thanks in advanced,
> Vic|||Hi Vic.
A couple of more alternatives for you are:
(a) http://sqlguy.home.comcast.net/logship.htm
(b) There's also a log shipping utility in the SQL Server Resource Kit which
you can downlaod from msdn if you're got a subscription.
These can be used with SQL Standard edition. You may even find others if you
spent some time searching the web..
HTH
Regards,
Greg Linwood
SQL Server MVP
"Vic" <vduran@.specpro-inc.com> wrote in message
news:025b01c3d496$d9112bf0$a401280a@.phx.gbl...
> I'm trying to implement Log Shipping to my database but I
> am running SQL Server Standard. I understand that SQL
> Enterprise edition has this built into it, but we
> currently can't perform an upgrade. How can I do this in
> the standard edition, or how can I get access to the jobs
> and store procedures or any other objects that get
> created using the enterprise edtion so that I can
> implement log shipping using the standard edition?
> Thanks in advanced,
> Vic
Showing posts with label standard. Show all posts
Showing posts with label standard. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
Log Shipping to old box?
My primary SQL Server box is 2005 Standard x64 running on 2 quad-core processors. I'm licensed for 2 processors.
I'd like to set up some kind of redundancy. The hardware I have available is about 4 years old and is currently running SQL Server 2000. Let's assume I upgrade the old box to SQL Server 2005 Standard. A couple of questions:
1) It seems the hardware gap between the 2 will make little difference in a log shipping. Please confirm this. Any other things that might be an issue?
2) Do I need lots of CALs on the backup box for Log Shipping? Or can I get by with 5?
3) I'd like to schedule log shipping pretty often--maybe every 5 or 10 minutes. Will this be an issue?
Thanks!
1. No
2. No, Yes, as long as it is not accessed by users that are not covered with CALs. A SQL Server CAL is good for all SQL Servers in the domain.
3. 5-10 minutes 'should' not be an issue. As long as the performance/load differential is not so great that the log cannot be applied in the time alloted.
Another option with SQL 2005 is Database Mirroring. Have you explored the benefits of Database Mirroring?
|||>Another option with SQL 2005 is Database Mirroring. Have you explored the benefits of Database Mirroring?I've read a little about Database Mirroring. How will my old hardware affect the mirroring process? Will I have trouble with the slower server keeping up with the transactions?
Brian
|||The same issue occurs with Log Shipping.
Will, in fact, the old box have enough 'power' to keep up with the data flow. That is something you will have to test.
|||I guess I made this assumption (that could be very wrong):
Log Shipping moves data in batches. Database mirroring moves data by record or transaction. (Not sure what method is used). A batch append should be less stressful on a backup server than a bunch of individual appends.
Even if these are true, maybe the difference in stress is much less than I think.
Brian
|||It could go either way.
I would set up a test environment and test both if they seemed equally valid solution candidates. You're trying to balance the trade-offs of cost of solution vs. speed of recovery.
sqlFriday, March 23, 2012
Log Shipping question
I have SQL 2000 Enterprise edition on my production server, and SQL 2000
Standard on another server that will be used for my standby server. Can I
use Log Shipping in this case? I read I must have enterprise edition, but
do I need it on both servers?
MikeYes you can use log shipping.
Log shipping is a feature that is built in to the Enterprise Edition but it
is easy to set this up on your own.
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
"Mike" <mrfaber@.att.net> wrote in message
news:unR3RDIsEHA.3520@.TK2MSFTNGP11.phx.gbl...
> I have SQL 2000 Enterprise edition on my production server, and SQL 2000
> Standard on another server that will be used for my standby server. Can I
> use Log Shipping in this case? I read I must have enterprise edition, but
> do I need it on both servers?
> Mike
>|||I know that log shipping is built in to Enterprise edition, and also that
you can configure it manully on standard edition, but can I use the builtin
log shipping on my production server(Enterprise Edition) to my standby
server(standard Edition) Or do they both have to be enterprise edition to
use the builtin feature.
Mike
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:%231ZNUhIsEHA.324@.TK2MSFTNGP11.phx.gbl...
> Yes you can use log shipping.
> Log shipping is a feature that is built in to the Enterprise Edition but
> it
> is easy to set this up on your own.
>
> 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
>
> "Mike" <mrfaber@.att.net> wrote in message
> news:unR3RDIsEHA.3520@.TK2MSFTNGP11.phx.gbl...
>> I have SQL 2000 Enterprise edition on my production server, and SQL 2000
>> Standard on another server that will be used for my standby server. Can
>> I
>> use Log Shipping in this case? I read I must have enterprise edition,
>> but
>> do I need it on both servers?
>> Mike
>>
>|||I don't know. I have never used the built in method -- I have always
created the log shipping routines myself. Call me old fashioned or call me
a control freak. Heck, I was doing this back in the SQL Server 6.5 days.
It is easy enough to set up the appropriate jobs so I always went that
route.
--
Keith
"Mike" <mrfaber@.att.net> wrote in message
news:%23Oa1NqJsEHA.3936@.TK2MSFTNGP09.phx.gbl...
> I know that log shipping is built in to Enterprise edition, and also that
> you can configure it manully on standard edition, but can I use the
builtin
> log shipping on my production server(Enterprise Edition) to my standby
> server(standard Edition) Or do they both have to be enterprise edition to
> use the builtin feature.
> Mike
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:%231ZNUhIsEHA.324@.TK2MSFTNGP11.phx.gbl...
> > Yes you can use log shipping.
> > Log shipping is a feature that is built in to the Enterprise Edition but
> > it
> > is easy to set this up on your own.
> >
> >
> > 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
> >
> >
> > "Mike" <mrfaber@.att.net> wrote in message
> > news:unR3RDIsEHA.3520@.TK2MSFTNGP11.phx.gbl...
> >> I have SQL 2000 Enterprise edition on my production server, and SQL
2000
> >> Standard on another server that will be used for my standby server.
Can
> >> I
> >> use Log Shipping in this case? I read I must have enterprise edition,
> >> but
> >> do I need it on both servers?
> >>
> >> Mike
> >>
> >>
> >
>
Standard on another server that will be used for my standby server. Can I
use Log Shipping in this case? I read I must have enterprise edition, but
do I need it on both servers?
MikeYes you can use log shipping.
Log shipping is a feature that is built in to the Enterprise Edition but it
is easy to set this up on your own.
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
"Mike" <mrfaber@.att.net> wrote in message
news:unR3RDIsEHA.3520@.TK2MSFTNGP11.phx.gbl...
> I have SQL 2000 Enterprise edition on my production server, and SQL 2000
> Standard on another server that will be used for my standby server. Can I
> use Log Shipping in this case? I read I must have enterprise edition, but
> do I need it on both servers?
> Mike
>|||I know that log shipping is built in to Enterprise edition, and also that
you can configure it manully on standard edition, but can I use the builtin
log shipping on my production server(Enterprise Edition) to my standby
server(standard Edition) Or do they both have to be enterprise edition to
use the builtin feature.
Mike
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:%231ZNUhIsEHA.324@.TK2MSFTNGP11.phx.gbl...
> Yes you can use log shipping.
> Log shipping is a feature that is built in to the Enterprise Edition but
> it
> is easy to set this up on your own.
>
> 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
>
> "Mike" <mrfaber@.att.net> wrote in message
> news:unR3RDIsEHA.3520@.TK2MSFTNGP11.phx.gbl...
>> I have SQL 2000 Enterprise edition on my production server, and SQL 2000
>> Standard on another server that will be used for my standby server. Can
>> I
>> use Log Shipping in this case? I read I must have enterprise edition,
>> but
>> do I need it on both servers?
>> Mike
>>
>|||I don't know. I have never used the built in method -- I have always
created the log shipping routines myself. Call me old fashioned or call me
a control freak. Heck, I was doing this back in the SQL Server 6.5 days.
It is easy enough to set up the appropriate jobs so I always went that
route.
--
Keith
"Mike" <mrfaber@.att.net> wrote in message
news:%23Oa1NqJsEHA.3936@.TK2MSFTNGP09.phx.gbl...
> I know that log shipping is built in to Enterprise edition, and also that
> you can configure it manully on standard edition, but can I use the
builtin
> log shipping on my production server(Enterprise Edition) to my standby
> server(standard Edition) Or do they both have to be enterprise edition to
> use the builtin feature.
> Mike
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:%231ZNUhIsEHA.324@.TK2MSFTNGP11.phx.gbl...
> > Yes you can use log shipping.
> > Log shipping is a feature that is built in to the Enterprise Edition but
> > it
> > is easy to set this up on your own.
> >
> >
> > 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
> >
> >
> > "Mike" <mrfaber@.att.net> wrote in message
> > news:unR3RDIsEHA.3520@.TK2MSFTNGP11.phx.gbl...
> >> I have SQL 2000 Enterprise edition on my production server, and SQL
2000
> >> Standard on another server that will be used for my standby server.
Can
> >> I
> >> use Log Shipping in this case? I read I must have enterprise edition,
> >> but
> >> do I need it on both servers?
> >>
> >> Mike
> >>
> >>
> >
>
Log Shipping problem
Dear Friends
I have a SQL Standard version and due to same i am not
able to do the log shipping for the database i want to
create a backup server which is only for analysis and the
same need to update only once. I can not set the
replication between the server as the Database is not
compatible for the same it is having 1024 column in many
tables.
Now What i have done is created a maintaince plan for the
backup and transactional backup in a 24 hours.
The same are replicated to the other server hard drive
with Data Replication service.
I want to create a job which will automatically restore
the transaction log on the analysis server.
Please suggest how can i achive the same. Your earlier
reply would help me a lot.
Best regards
Sharad
Take a look at the walkthrough and make sure you have only ONE database
selected at a time in the DB Maint Planner and it's in Full Recovery mode
when you have decided which one to select.
http://www.microsoft.com/technet/pro.../logship1.mspx
Hope this helps
Paul.
I have a SQL Standard version and due to same i am not
able to do the log shipping for the database i want to
create a backup server which is only for analysis and the
same need to update only once. I can not set the
replication between the server as the Database is not
compatible for the same it is having 1024 column in many
tables.
Now What i have done is created a maintaince plan for the
backup and transactional backup in a 24 hours.
The same are replicated to the other server hard drive
with Data Replication service.
I want to create a job which will automatically restore
the transaction log on the analysis server.
Please suggest how can i achive the same. Your earlier
reply would help me a lot.
Best regards
Sharad
Take a look at the walkthrough and make sure you have only ONE database
selected at a time in the DB Maint Planner and it's in Full Recovery mode
when you have decided which one to select.
http://www.microsoft.com/technet/pro.../logship1.mspx
Hope this helps
Paul.
Wednesday, March 21, 2012
Log shipping not work, but jobs say successful
I have a pretty standard log shipping arrangement created with the Log
Shipping wizard against an existing database on the standby server. All the
jobs were created successfully and run on the correct schedule. However,
the copy job on the standby server doesn't work. It shows that it ran
successfully, but the files just aren't copied to the standby server's
directory, and so are not restored. After manually copying the transaction
log files to the standby server, the restore job will work. However, the
next log in sequence will not copy over.
The maintenance plan history shows no errors.
Both servers are running Windows 2000 servers and SQL Server 2000 Enterprise
SP3a. The link is a 45 Mbit leased line.
What could be the problem?
Thanks,
RS
RS,
usually this is a problem with the paths - the wizard is not very intuitive
and it's quite easy to set them incorrectly. On the screen that says
'Specify the Transaction Log Share', you must identify the file share on the
primary server and when setting up the destination, the name is a local
pathname, not a file share. If this is incorrect, there will be no errors
and the monitor will show continually the first setup file as being
transferred. So, initially check that you have a share on the primary server
and the logs are getting there.
HTH,
Paul Ibison
sql
Shipping wizard against an existing database on the standby server. All the
jobs were created successfully and run on the correct schedule. However,
the copy job on the standby server doesn't work. It shows that it ran
successfully, but the files just aren't copied to the standby server's
directory, and so are not restored. After manually copying the transaction
log files to the standby server, the restore job will work. However, the
next log in sequence will not copy over.
The maintenance plan history shows no errors.
Both servers are running Windows 2000 servers and SQL Server 2000 Enterprise
SP3a. The link is a 45 Mbit leased line.
What could be the problem?
Thanks,
RS
RS,
usually this is a problem with the paths - the wizard is not very intuitive
and it's quite easy to set them incorrectly. On the screen that says
'Specify the Transaction Log Share', you must identify the file share on the
primary server and when setting up the destination, the name is a local
pathname, not a file share. If this is incorrect, there will be no errors
and the monitor will show continually the first setup file as being
transferred. So, initially check that you have a share on the primary server
and the logs are getting there.
HTH,
Paul Ibison
sql
Log shipping Monitor server
Hi,
Can separate monitor server for SQL 2000 Log Shipping
high-availability configuration be SQL 2000 Standard
Edtion?
Or must be SQL 2000 Server Enterprise Edition?
Thanks for answers
MilanYou cant have log shipping for SQL Standard, not quite sure what ur
question is?
Regards
J
"Milan Ojstersek" <milan.ojstersek@.hermes-plus.si> wrote in message
news:083101c34c5d$25531fe0$a601280a@.phx.gbl...
> Hi,
> Can separate monitor server for SQL 2000 Log Shipping
> high-availability configuration be SQL 2000 Standard
> Edtion?
> Or must be SQL 2000 Server Enterprise Edition?
> Thanks for answers
> Milan
Can separate monitor server for SQL 2000 Log Shipping
high-availability configuration be SQL 2000 Standard
Edtion?
Or must be SQL 2000 Server Enterprise Edition?
Thanks for answers
MilanYou cant have log shipping for SQL Standard, not quite sure what ur
question is?
Regards
J
"Milan Ojstersek" <milan.ojstersek@.hermes-plus.si> wrote in message
news:083101c34c5d$25531fe0$a601280a@.phx.gbl...
> Hi,
> Can separate monitor server for SQL 2000 Log Shipping
> high-availability configuration be SQL 2000 Standard
> Edtion?
> Or must be SQL 2000 Server Enterprise Edition?
> Thanks for answers
> Milan
Log Shipping Monitor Reqs
Greetings:
Does anyone know if I can install/run the Log Shipping Monitor Utility on
SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
Enterprise Edition in order to configure Log Shipping?
I realize the recommendation is to NOT install the monitor utility on the
source server, but can it be installed on the Destination server?
Thanks!
Keith C. Jakobs, MCP
Hello mate,
You DON'T need to have Enterprise Edition to host the log shipping monitor -
I have and use exactly the model your trying to work towards in my
organisation.
Regards
Paul.
"Keith Jakobs, MCP" wrote:
> Greetings:
> Does anyone know if I can install/run the Log Shipping Monitor Utility on
> SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
> Enterprise Edition in order to configure Log Shipping?
> I realize the recommendation is to NOT install the monitor utility on the
> source server, but can it be installed on the Destination server?
> Thanks!
> Keith C. Jakobs, MCP
>
>
Does anyone know if I can install/run the Log Shipping Monitor Utility on
SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
Enterprise Edition in order to configure Log Shipping?
I realize the recommendation is to NOT install the monitor utility on the
source server, but can it be installed on the Destination server?
Thanks!
Keith C. Jakobs, MCP
Hello mate,
You DON'T need to have Enterprise Edition to host the log shipping monitor -
I have and use exactly the model your trying to work towards in my
organisation.
Regards
Paul.
"Keith Jakobs, MCP" wrote:
> Greetings:
> Does anyone know if I can install/run the Log Shipping Monitor Utility on
> SQL 2000 Standard Edition, or do I need to actually have THREE copies of SQL
> Enterprise Edition in order to configure Log Shipping?
> I realize the recommendation is to NOT install the monitor utility on the
> source server, but can it be installed on the Destination server?
> Thanks!
> Keith C. Jakobs, MCP
>
>
Monday, March 19, 2012
Log shipping in SQL STD
I'm looking for some docs to instruct me how to setup log shipping in a SQL
2000 Standard environment.
Thanks
Here's one example:
http://www.sqlservercentral.com/colu...ogshipping.asp
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
2000 Standard environment.
Thanks
Here's one example:
http://www.sqlservercentral.com/colu...ogshipping.asp
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
Log shipping in SQL STD
I'm looking for some docs to instruct me how to setup log shipping in a SQL
2000 Standard environment.
Thanks
Here's one example:
http://www.sqlservercentral.com/colu...ogshipping.asp
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
2000 Standard environment.
Thanks
Here's one example:
http://www.sqlservercentral.com/colu...ogshipping.asp
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
Log shipping in SQL STD
I'm looking for some docs to instruct me how to setup log shipping in a SQL
2000 Standard environment.
ThanksHere's one example:
http://www.sqlservercentral.com/columnists/ckempster/customlogshipping.asp
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
2000 Standard environment.
ThanksHere's one example:
http://www.sqlservercentral.com/columnists/ckempster/customlogshipping.asp
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
Log shipping in SQL STD
I'm looking for some docs to instruct me how to setup log shipping in a SQL
2000 Standard environment.
Thanks
Here's one example:
http://www.sqlservercentral.com/colu...ogshipping.asp
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
2000 Standard environment.
Thanks
Here's one example:
http://www.sqlservercentral.com/colu...ogshipping.asp
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
Log shipping in SQL STD
I'm looking for some docs to instruct me how to setup log shipping in a SQL
2000 Standard environment.
ThanksHere's one example:
http://www.sqlservercentral.com/col...logshipping.asp
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
2000 Standard environment.
ThanksHere's one example:
http://www.sqlservercentral.com/col...logshipping.asp
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Peretz Stern" <peretzstern@.optonline.net> wrote in message
news:O58NIYWnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> I'm looking for some docs to instruct me how to setup log shipping in a
> SQL 2000 Standard environment.
>
> Thanks
>
Monday, March 12, 2012
Log Shipping from SQL Server 2000 Enterprise to SQL Server 2005 Standard
Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
to 2000 standard. Thanks for any suggestions.
RBollinger
Hi Rob
"robboll" wrote:
> Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> to 2000 standard. Thanks for any suggestions.
> RBollinger
>
I am not a log shipping expert, but reading between the lines of
http://msdn2.microsoft.com/en-us/library/ms188297.aspx it seems you can log
ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
there is no going back, and SQL 2005 can not ship back to SQL 2000.
John
|||On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Rob
> "robboll" wrote:
>
> I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> there is no going back, and SQL 2005 can not ship back to SQL 2000.
> John
Good answer -- thanks
|||On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Rob
> "robboll" wrote:
>
> I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> there is no going back, and SQL 2005 can not ship back to SQL 2000.
> John
As a follow-up question. If the secondary server is SQL Server
Standard (Personal Edition) will that work? The primary server is SQL
Server 2000 Enterprise Edition with the log shipping functionality.
|||Hi Rob
"robboll" wrote:
> On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> As a follow-up question. If the secondary server is SQL Server
> Standard (Personal Edition) will that work? The primary server is SQL
> Server 2000 Enterprise Edition with the log shipping functionality.
>
I would expect there are licencing issues if you used personal edition for
this, expecially if you failed over to it. In general if your failover
hardware/software is not the same specification as the primary system you may
have issues that negates the reason for trying to maintain high availabilty
i.e. you can not continue with a suitable level of service.
John
to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
to 2000 standard. Thanks for any suggestions.
RBollinger
Hi Rob
"robboll" wrote:
> Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> to 2000 standard. Thanks for any suggestions.
> RBollinger
>
I am not a log shipping expert, but reading between the lines of
http://msdn2.microsoft.com/en-us/library/ms188297.aspx it seems you can log
ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
there is no going back, and SQL 2005 can not ship back to SQL 2000.
John
|||On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Rob
> "robboll" wrote:
>
> I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> there is no going back, and SQL 2005 can not ship back to SQL 2000.
> John
Good answer -- thanks
|||On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Rob
> "robboll" wrote:
>
> I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> there is no going back, and SQL 2005 can not ship back to SQL 2000.
> John
As a follow-up question. If the secondary server is SQL Server
Standard (Personal Edition) will that work? The primary server is SQL
Server 2000 Enterprise Edition with the log shipping functionality.
|||Hi Rob
"robboll" wrote:
> On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> As a follow-up question. If the secondary server is SQL Server
> Standard (Personal Edition) will that work? The primary server is SQL
> Server 2000 Enterprise Edition with the log shipping functionality.
>
I would expect there are licencing issues if you used personal edition for
this, expecially if you failed over to it. In general if your failover
hardware/software is not the same specification as the primary system you may
have issues that negates the reason for trying to maintain high availabilty
i.e. you can not continue with a suitable level of service.
John
Log Shipping from SQL Server 2000 Enterprise to SQL Server 2005 Standard
Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
to 2000 standard. Thanks for any suggestions.
RBollingerHi Rob
"robboll" wrote:
> Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> to 2000 standard. Thanks for any suggestions.
> RBollinger
>
I am not a log shipping expert, but reading between the lines of
http://msdn2.microsoft.com/en-us/library/ms188297.aspx it seems you can log
ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
there is no going back, and SQL 2005 can not ship back to SQL 2000.
John|||On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Rob
> "robboll" wrote:
> > Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> > to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> > to 2000 standard. Thanks for any suggestions.
> > RBollinger
> I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> there is no going back, and SQL 2005 can not ship back to SQL 2000.
> John
Good answer -- thanks|||On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Rob
> "robboll" wrote:
> > Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> > to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> > to 2000 standard. Thanks for any suggestions.
> > RBollinger
> I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> there is no going back, and SQL 2005 can not ship back to SQL 2000.
> John
As a follow-up question. If the secondary server is SQL Server
Standard (Personal Edition) will that work? The primary server is SQL
Server 2000 Enterprise Edition with the log shipping functionality.|||Hi Rob
"robboll" wrote:
> On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > Hi Rob
> >
> > "robboll" wrote:
> > > Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> > > to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> > > to 2000 standard. Thanks for any suggestions.
> >
> > > RBollinger
> >
> > I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> > ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> > there is no going back, and SQL 2005 can not ship back to SQL 2000.
> >
> > John
> As a follow-up question. If the secondary server is SQL Server
> Standard (Personal Edition) will that work? The primary server is SQL
> Server 2000 Enterprise Edition with the log shipping functionality.
>
I would expect there are licencing issues if you used personal edition for
this, expecially if you failed over to it. In general if your failover
hardware/software is not the same specification as the primary system you may
have issues that negates the reason for trying to maintain high availabilty
i.e. you can not continue with a suitable level of service.
John
to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
to 2000 standard. Thanks for any suggestions.
RBollingerHi Rob
"robboll" wrote:
> Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> to 2000 standard. Thanks for any suggestions.
> RBollinger
>
I am not a log shipping expert, but reading between the lines of
http://msdn2.microsoft.com/en-us/library/ms188297.aspx it seems you can log
ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
there is no going back, and SQL 2005 can not ship back to SQL 2000.
John|||On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Rob
> "robboll" wrote:
> > Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> > to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> > to 2000 standard. Thanks for any suggestions.
> > RBollinger
> I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> there is no going back, and SQL 2005 can not ship back to SQL 2000.
> John
Good answer -- thanks|||On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Rob
> "robboll" wrote:
> > Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> > to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> > to 2000 standard. Thanks for any suggestions.
> > RBollinger
> I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> there is no going back, and SQL 2005 can not ship back to SQL 2000.
> John
As a follow-up question. If the secondary server is SQL Server
Standard (Personal Edition) will that work? The primary server is SQL
Server 2000 Enterprise Edition with the log shipping functionality.|||Hi Rob
"robboll" wrote:
> On Apr 4, 1:00 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> > Hi Rob
> >
> > "robboll" wrote:
> > > Is it possible to set up Log Shipping from SQL Server 2000 Enterprise
> > > to SQL Server 2005 Standard? If not I am ready to downgrade the 2005
> > > to 2000 standard. Thanks for any suggestions.
> >
> > > RBollinger
> >
> > I am not a log shipping expert, but reading between the lines ofhttp://msdn2.microsoft.com/en-us/library/ms188297.aspxit seems you can log
> > ship from SQL 2000 to SQL 2005, but once you have failed over to SQL 2005
> > there is no going back, and SQL 2005 can not ship back to SQL 2000.
> >
> > John
> As a follow-up question. If the secondary server is SQL Server
> Standard (Personal Edition) will that work? The primary server is SQL
> Server 2000 Enterprise Edition with the log shipping functionality.
>
I would expect there are licencing issues if you used personal edition for
this, expecially if you failed over to it. In general if your failover
hardware/software is not the same specification as the primary system you may
have issues that negates the reason for trying to maintain high availabilty
i.e. you can not continue with a suitable level of service.
John
Monday, February 20, 2012
Log Shipping (sort of) with Standard Edition
I have about 30 Databases on a Production SQL Server STANDARD Edition 2000k Instance.
All Backups are performed using SQL Server Maintenance plans (Full Nightly backups and periodic Xaction log backups during business hours)
I would like the ability to copy the FULL Backups to another Server - perhaps on a nightly basis - and then restore them to this other Server as a means of having some sort of Disaster Recovery.
I know with Enterprise Edition, you can set up linked servers and do log shipping or replication, but I don't have that luxury here. I also don't have access to the MS Backoffice Resource Kit - which I understand has some canned scripts to do what I want to do here.
My problem really is that because I don't have control over the backup filenames, how to I automate the restore process on the second Server?
any help would be much appreciated.You could try using the Scripting.FileSystemObject to perform a directory listing of the files in a particular directory. Then use a DO...LOOP to scroll through the list, copying the file and then restoring it to a remote server.
Alternatively, SQL keeps track of the file names used for backups in the msdb database. Look at the following tables:
backupfile
backupmediafamily
backupmediaset
backupset
Finally, you might just consider having the backups run out over the network to a remote server. In the event the primary node fails, you could restore the backups to an alternate server pretty quickly. Just remember that you also need to script off logins, jobs and save DTS packages (as binary files). You then also need to "exercise" your disaster recovery plan on a periodic basis to validate/verify your processes.
Regards,
hmscott|||Thank you for your reply!
I am actually already doing backups locally as well as to another Server on the Network - My problem was how to 'programatically' restore these backups on the remote server.
I found this script - posted by someone else on another forum...
It is SWEET!!!! As long as my backups are in a certain format and all in the same directory, this store procedure will check the folder for the newest .bak file for a specific database and restore it!!!!
So now what I have done is set up a maintenance plan on my prod server to do a full set of backups to this 'network' server - then I just schedule this stored procedure to run on the 'network' server and my databases are automatically refreshed..
Thanks again for your help|||Hi,
Can you let me know where you got that script...
Looking to do something similar.
Thanks,
-jmr|||I would also like to see that script.
All Backups are performed using SQL Server Maintenance plans (Full Nightly backups and periodic Xaction log backups during business hours)
I would like the ability to copy the FULL Backups to another Server - perhaps on a nightly basis - and then restore them to this other Server as a means of having some sort of Disaster Recovery.
I know with Enterprise Edition, you can set up linked servers and do log shipping or replication, but I don't have that luxury here. I also don't have access to the MS Backoffice Resource Kit - which I understand has some canned scripts to do what I want to do here.
My problem really is that because I don't have control over the backup filenames, how to I automate the restore process on the second Server?
any help would be much appreciated.You could try using the Scripting.FileSystemObject to perform a directory listing of the files in a particular directory. Then use a DO...LOOP to scroll through the list, copying the file and then restoring it to a remote server.
Alternatively, SQL keeps track of the file names used for backups in the msdb database. Look at the following tables:
backupfile
backupmediafamily
backupmediaset
backupset
Finally, you might just consider having the backups run out over the network to a remote server. In the event the primary node fails, you could restore the backups to an alternate server pretty quickly. Just remember that you also need to script off logins, jobs and save DTS packages (as binary files). You then also need to "exercise" your disaster recovery plan on a periodic basis to validate/verify your processes.
Regards,
hmscott|||Thank you for your reply!
I am actually already doing backups locally as well as to another Server on the Network - My problem was how to 'programatically' restore these backups on the remote server.
I found this script - posted by someone else on another forum...
It is SWEET!!!! As long as my backups are in a certain format and all in the same directory, this store procedure will check the folder for the newest .bak file for a specific database and restore it!!!!
So now what I have done is set up a maintenance plan on my prod server to do a full set of backups to this 'network' server - then I just schedule this stored procedure to run on the 'network' server and my databases are automatically refreshed..
Thanks again for your help|||Hi,
Can you let me know where you got that script...
Looking to do something similar.
Thanks,
-jmr|||I would also like to see that script.
Subscribe to:
Posts (Atom)