Is it possible to set up log shipping via scripts instead
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!
Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!
|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping=20
http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =
(White Paper)=20
http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping=20
http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping=20
http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping=20
http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =
Errors=20
http://support.microsoft.com/?id=3D329133
--=20
Keith
"Tom Horner" <thorner@.s1.com> wrote in message =
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead=20
> of GUI? We have over 50 databases being log shipped, and=20
> occasional (almost random) failures for various reasons=20
> cause us to have to "reset" (redo) the log shipping. =20
> Doing this via the GUI is a time-consuming process. I=20
> found 5/23/03 webcast with PPT slide saying this is "not=20
> supported". Does this mean not POSSIBLE? We are using=20
> SQL server 2000 on Windows 2000 boxes, two separate=20
> servers with primary and secondary (log shipped-to)=20
> databases.
>=20
> Thanks in advance!
|||yes.
this is exactly what we are doing here.
Here is an example script to apply logs to the standby.
Cheers,
Greg Jackson
PDX, Oregon
begin 666 RETORE LOG SCRIPT FOR ALL TRAN BAKS IN A DIR.SQL
M__XO`"H`*@.`J`"H`*@.`J`" `3P!B`&H`90!C`'0`.@.`@.`" `4P!T`&\`<@.!E
M`&0`( !0`'(`;P!C`&4`9 !U`'(`90`@.`'4`<P!P`%\`4@.!A`'0`:0!N`&<`
M<P!?`%0`<@.!A`&X`<P!A`&,`= !I`&\`;@.!,`&\`9P!?`%(`90!S`'0`;P!R
M`&4`( `@.`" `( !3`&,`<@.!I`' `= `@.`$0`80!T`&4`.@.`@.`# `-0`O`#$`
M,@.`O`#(`, `P`# `( `X`#H`-0`W`#H`,@.`U`" `4 !-`" `*@.`J`"H`*@.`J
M`"H`+P`-``H`+P`J`"H`*@.`J`"H`*@.`@.`$\`8@.!J`&4`8P!T`#H`( `@.`%,`
M= !O`'(`90!D`" `4 !R`&\`8P!E`&0`=0!R`&4`( !U`',`< !?`%(`80!T
M`&D`;@.!G`',`7P!4`'(`80!N`',`80!C`'0`:0!O`&X`3 !O`&<`7P!2`&4`
M<P!T`&\`<@.!E`" `( `J`"H`*@.`J`"H`*@.`O``T`"@.`O`"H`"0!7`'(`:0!T
M`'0`90!N`" `0@.!Y`#H`( !!`&P`90!X`" `5P!E`'(`9P!E`&P`90!S``T`
M"@.`J`" `"0!#`'(`90!A`'0`90!D`#H`( `@.`# `-0`O`# `,0`O`#(`, `P
M`#$`#0`*`"H`"0!.`&\`= !E`',`.@.`-``H`*@.`-``H`*@.`@.`" `( `@.`" `
M( `@.`" `( !!`&P`= !E`'(`90!D`" `0@.!Y`#H`( `@.`$$`; !E`'@.`( !7
M`&4`<@.!G`&4`; !E`',`#0`*`"H`( `@.`" `( `@.`" `( `@.`" `1 !A`'0`
M90`Z`" `( `P`#8`+P`P`#$`+P`R`# `, `Q``T`"@.`J`" `( `@.`" `( `@.
M`" `( `@.`$X`;P!T`&4`<P`Z`" `( !#`&\`;0!M`&4`;@.!T`&4`9 `-``H`
M*@.`-``H`*@.`@.`" `( `@.`" `( `@.`" `( !!`&P`= !E`'(`90!D`" `0@.!Y
M`#H`( `-``H`*@.`@.`" `( `@.`" `( `@.`" `( !$`&$`= !E`#H`#0`*`"H`
M( `@.`" `( `@.`" `( `@.`" `3@.!O`'0`90!S`#H`( `@.`$D`1@.`@.`%D`3P!5
M`" `00!,`%0`10!2`" `5 !(`$D`4P`@.`% `4@.!/`$,`10!$`%4`4@.!%`"P`
M( !#`$\`4 !9`" `00!.`$0`( !0`$$`4P!4`$4`( !4`$@.`10`@.`"<`00!,
M`%0`10!2`$4`1 `@.`$(`60`G``T`"@.`J`" `( `@.`" `( `@.`" `( `@.`%,`
M10!#`%0`20!/`$X`( !4`$\`( !$`%4`4 !,`$D`0P!!`%0`10`@.`$D`5 `[
M`" `5 !(`$4`3@.`@.`$4`1 !)`%0`( !4`$@.`10`@.`$8`20!2`%,`5 `@.`$(`
M3 !!`$X`2P`@.`$,`3P!0`%D`+ `@.`$P`10!!`%8`20!.`$<`#0`*`"H`( `@.
M`" `( `@.`" `( `@.`" `00`@.`$0`50!0`$P`20!#`$$`5 !%`" `20!.`" `
M4 !,`$$`0P!%`" `1@.!/`%(`( !4`$@.`10`@.`$X`10!8`%0`( !0`$4`4@.!3
M`$\`3@.`@.`%0`3P`@.`$4`1 !)`%0`( !4`$@.`20!3`" `4 !2`$\`0P`N``T`
M"@.`J``T`"@.`J`"\`#0`*``T`"@.`M`"T`9 !R`&\`< `@.`' `<@.!O`&,`90!D
M`'4`<@.!E`" `=0!S`' `7P!2`&$`= !I`&X`9P!S`%\`5 !R`&$`;@.!S`&$`
M8P!T`&D`;P!N`$P`;P!G`%\`4@.!E`',`= !O`'(`90`-``H`#0`*``T`"@.`M
M`"T`80!S``T`"@.`-``H`<P!E`'0`( !N`&\`8P!O`'4`;@.!T`" `;P!N``T`
M"@.`-``H`9 !E`&,`; !A`'(`90`@.`$ `<P!T`'(`:0!N`&<`( !V`&$`<@.!C
M`&@.`80!R`"@.`,0`P`# `, `I`"P`#0`*``D`0 !,`&\`9P!&`&D`; !E`" `
M=@.!A`'(`8P!H`&$`<@.`H`#$`, `P`# `*0`-``H`#0`*`&D`9@.`@.`&4`> !I
M`',`= !S`"@.`<P!E`&P`90!C`'0`( `J`" `9@.!R`&\`;0`@.`'0`90!M`' `
M9 !B`"X`+@.!S`'D`<P!O`&(`:@.!E`&,`= !S`" `=P!H`&4`<@.!E`" `:0!D
M`" `/0`@.`&\`8@.!J`&4`8P!T`%\`:0!D`"@.`)P!T`&4`;0!P`&0`8@.` N`"X`
M(P!,`&\`9P!3`&@.`:0!P`"<`*0`I``T`"@.!D`'(`;P!P`" `= !A`&(`; !E
M`" `(P!,`&\`9P!3`&@.`:0!P``T`"@.`-``H`8P!R`&4`80!T`&4`( !T`&$`
M8@.!L`&4`#0`*``D`(P!,`&\`9P!3`&@.`:0!P``T`"@.`)``D`* `-``H`"0`)
M``D`3 !O`&<`1@.!I`&P`90`@.`'8`80!R`&,`: !A`'(`* `Q`# `, `P`"D`
M#0`*``D`"0`I``T`"@.`-``H`:0!N`',`90!R`'0`( `C`$P`;P!G`%,`: !I
M`' `#0`*`&4`> !E`&,`( !M`&$`<P!T`&4`<@.`N`&0`8@.!O`"X`> !P`%\`
M8P!M`&0`<P!H`&4`; !L`" `)P!D`&D`<@.`@.`%P`7 !D`&$`= !A`'<`: !S
M`&4`, `Q`%P`4P!1`$P`0@.!!`$,`2P!5`% `7 !0`%(`3P!$`%,`40!,`# `
M,P!<`&0`8@.!(`$$`50!<`%0`4@.!.`%,`7 `J`" `+P!"`" `+P!/`$0`)P`-
M``H`#0`*``T`"@.`M`"T`<P!E`'0`( ! `$P`;P!G`$8`:0!L`&4`( `]`" `
M* !S`&4`; !E`&,`= `@.`"H`( `@.`&8`<@.!O`&T`( `C`$P`;P!G`%,`: !I
M`' `( !O`'(`9 !E`'(`( !B`'D`( !,`&\`9P!&`&D`; !E`" `9 !E`',`
M8P`I``T`"@.!D`&4`8P!L`&$`<@.!E`" `8P!U`'(`,0`@.`&,`=0!R`',`;P!R
M`" `9@.!O`'(`#0`*`',`90!L`&4`8P!T`" `; !O`&<`9@.!I`&P`90`-``H`
M9@.!R`&\`;0`@.`",`3 !O`&<`4P!H`&D`< `-``H`#0`*`&\`< !E`&X`( !C
M`'4`<@.`Q``T`"@.`-``H`9@.!E`'0`8P!H`" `;@.!E`'@.`= `@.`&8`<@.!O`&T`
M( !C`'4`<@.`Q`" `:0!N`'0`;P`@.`$ `3 !O`&<`1@.!I`&P`90`-``H`#0`*
M`'<`: !I`&P`90`@.`$ `0 !F`&4`= !C`&@.`7P!S`'0`80!T`'4`<P`@.`#T`
M( `P``T`"@.!B`&4`9P!I`&X`#0`*``T`"@.`-``H`<P!E`'0`( ! `',`= !R
M`&D`;@.!G`" `/0`@.`"<`4@.!%`%,`5 !/`%(`10`@.`$P`3P!'``T`"@.`)``D`
M"0!D`&(`2 !!`%4`#0`*``D`"0!&`%(`3P!-`" `1 !)`%,`2P`@.`#T`( `@.
M``T`"@.`)``D`"0!.`"<`( `K`" `)P`G`"<`)P`@.`"L`( `G`%P`7 !D`&$`
M= !A`'<`: !S`&4`, `Q`%P`4P!1`$P`0@.!!`$,`2P!5`% `7 !0`%(`3P!$
M`%,`40!,`# `,P!<`&0`8@.!(`$$`50!<`%0`4@.!.`%,`7 `G`" `*P`@.`$ `
M3 !O`&<`1@.!I`&P`90`@.`"L`( `G`"<`)P`G`" `*P`-``H`"0`)`"<`( !7
M`$D`5 !(``T`"@.`)``D`( `)`%,`5 !!`$X`1 !"`%D`( `]`" `)P`@.`"L`
M( `G`"<`)P`G`" `*P`@.`"<`7 !<`&0`80!T`&$`=P!H`',`90`P`#$`7 !3
M`%$`3 !"`$$`0P!+`%4`4 !<`% `4@.!/`$0`4P!1`$P`, `S`%P`9 !B`$@.`
M00!5`%P`5 !2`$X`4P!<`&0`8@.!(`$$`50!?`&P`;P!G`',`: !I`' `7P!5
M`&X`9 !O`$8`:0!L`&4`+@.!L`&0`9@.`G`"L`( `G`"<`)P`G``T`"@.`-``H`
M< !R`&D`;@.!T`" `* ! `',`= !R`&D`;@.!G`"D`#0`*`"T`+0!U`',`90`@.
M`' `<@.!I`&X`= `@.`'0`;P`@.`&,`<@.!E`&$`= !E`" `<P!C`'(`:0!P`'0`
M<P`-``H`+0`M`&,`80!N`" `8P!H`&$`;@.!G`&4`( !A`&(`;P!V`&4`( !T
M`&\`( !E`'@.`90!C`" `= !O`" `<@.!U`&X`( !I`&X`; !I`&X`90`-``H`
M9@.!E`'0`8P!H`" `;@.!E`'@.`= `@.`&8`<@.!O`&T`( !C`'4`<@.`Q`" `:0!N
M`'0`;P`@.`$ `3 !O`&<`1@.!I`&P`90`-``H`90!N`&0`#0`*``T`"@.!D`&4`
J80!L`&P`;P!C`&$`= !E`" `8P!U`'(`,0`-``H`#0`*`$<`3P`-``H`
`
end
Showing posts with label scripts. Show all posts
Showing posts with label scripts. Show all posts
Wednesday, March 28, 2012
log shipping set up via scripts instead of GUI
Is it possible to set up log shipping via scripts instead
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping=20
http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =
(White Paper)=20
http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping=20
http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping=20
http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping=20
http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =
Errors=20
http://support.microsoft.com/?id=3D329133
--=20
Keith
"Tom Horner" <thorner@.s1.com> wrote in message =
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead=20
> of GUI? We have over 50 databases being log shipped, and=20
> occasional (almost random) failures for various reasons=20
> cause us to have to "reset" (redo) the log shipping. =20
> Doing this via the GUI is a time-consuming process. I=20
> found 5/23/03 webcast with PPT slide saying this is "not=20
> supported". Does this mean not POSSIBLE? We are using=20
> SQL server 2000 on Windows 2000 boxes, two separate=20
> servers with primary and secondary (log shipped-to)=20
> databases.
>=20
> Thanks in advance!sql
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping=20
http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =
(White Paper)=20
http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping=20
http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping=20
http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping=20
http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =
Errors=20
http://support.microsoft.com/?id=3D329133
--=20
Keith
"Tom Horner" <thorner@.s1.com> wrote in message =
news:1c0c601c45214$85a56890$a501280a@.phx
.gbl...
> Is it possible to set up log shipping via scripts instead=20
> of GUI? We have over 50 databases being log shipped, and=20
> occasional (almost random) failures for various reasons=20
> cause us to have to "reset" (redo) the log shipping. =20
> Doing this via the GUI is a time-consuming process. I=20
> found 5/23/03 webcast with PPT slide saying this is "not=20
> supported". Does this mean not POSSIBLE? We are using=20
> SQL server 2000 on Windows 2000 boxes, two separate=20
> servers with primary and secondary (log shipped-to)=20
> databases.
>=20
> Thanks in advance!sql
log shipping set up via scripts instead of GUI
Is it possible to set up log shipping via scripts instead
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =(White Paper) http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =Errors http://support.microsoft.com/?id=3D329133
-- Keith
"Tom Horner" <thorner@.s1.com> wrote in message =news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead > of GUI? We have over 50 databases being log shipped, and > occasional (almost random) failures for various reasons > cause us to have to "reset" (redo) the log shipping. > Doing this via the GUI is a time-consuming process. I > found 5/23/03 webcast with PPT slide saying this is "not > supported". Does this mean not POSSIBLE? We are using > SQL server 2000 on Windows 2000 boxes, two separate > servers with primary and secondary (log shipped-to) > databases.
> > Thanks in advance!|||Tom,
the sql server resource kit has some scripts to do this,
which are particularly useful if you only have standard
edition or lower. Similar scripts are available for free
from various sites (eg http://www.sql-server-
performance.com/sql_server_log_shipping.asp). In both
cases you won't get access to a monitoring GUI, but
alerts/reports can be set up to perform this work.
Regards,
Paul Ibison
of GUI? We have over 50 databases being log shipped, and
occasional (almost random) failures for various reasons
cause us to have to "reset" (redo) the log shipping.
Doing this via the GUI is a time-consuming process. I
found 5/23/03 webcast with PPT slide saying this is "not
supported". Does this mean not POSSIBLE? We are using
SQL server 2000 on Windows 2000 boxes, two separate
servers with primary and secondary (log shipped-to)
databases.
Thanks in advance!Hi Tom
It certainly is possible. All that log shipping does under the covers is
basically back up the database log, ftp the file to the target server then
restore it with sandby. That can easily be achieved in scripts - just BACKUP
LOG [dbname] to disk='c:\backupname.lbak', then perform an ftp using
xp_cmdshell, then run the restore command on the target server.. Many people
do this & if you search the newsgroup archive on google, you'll see lots of
sample scripts etc.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Tom Horner" <thorner@.s1.com> wrote in message
news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead
> of GUI? We have over 50 databases being log shipped, and
> occasional (almost random) failures for various reasons
> cause us to have to "reset" (redo) the log shipping.
> Doing this via the GUI is a time-consuming process. I
> found 5/23/03 webcast with PPT slide saying this is "not
> supported". Does this mean not POSSIBLE? We are using
> SQL server 2000 on Windows 2000 boxes, two separate
> servers with primary and secondary (log shipped-to)
> databases.
> Thanks in advance!|||Some good information:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping http://support.microsoft.com/?id=3D314515=20
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping =(White Paper) http://support.microsoft.com/?id=3D323135=20
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping http://support.microsoft.com/?id=3D325220=20
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping http://support.microsoft.com/?id=3D821786=20
321247 HOW TO: Configure Security for Log Shipping http://support.microsoft.com/?id=3D321247=20
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync" =Errors http://support.microsoft.com/?id=3D329133
-- Keith
"Tom Horner" <thorner@.s1.com> wrote in message =news:1c0c601c45214$85a56890$a501280a@.phx.gbl...
> Is it possible to set up log shipping via scripts instead > of GUI? We have over 50 databases being log shipped, and > occasional (almost random) failures for various reasons > cause us to have to "reset" (redo) the log shipping. > Doing this via the GUI is a time-consuming process. I > found 5/23/03 webcast with PPT slide saying this is "not > supported". Does this mean not POSSIBLE? We are using > SQL server 2000 on Windows 2000 boxes, two separate > servers with primary and secondary (log shipped-to) > databases.
> > Thanks in advance!|||Tom,
the sql server resource kit has some scripts to do this,
which are particularly useful if you only have standard
edition or lower. Similar scripts are available for free
from various sites (eg http://www.sql-server-
performance.com/sql_server_log_shipping.asp). In both
cases you won't get access to a monitoring GUI, but
alerts/reports can be set up to perform this work.
Regards,
Paul Ibison
Friday, March 23, 2012
log shipping problem
So...
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
Willie
All the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>
|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>
|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>
|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>
|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>
sql
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
Willie
All the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>
|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>
|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>
|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>
|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>
sql
log shipping problem
So...
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
WillieAll the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
WillieAll the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>
log shipping problem
So...
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
WillieAll the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
>> anyone out there help me out with the table generation scripts so that I
>> don't have to re-install SQL 2000?
>> Willie
>|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should be
>> in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support for
>> help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
>> anyone out there help me out with the table generation scripts so that I
>> don't have to re-install SQL 2000?
>> Willie
>>
>|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>> Actually, this got me on the right path, but it was the instls.sql file
>> in the /install directory that creates the log shipping pieces.
>> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
>> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should be
>> in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support for
>> help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables,
>> could anyone out there help me out with the table generation scripts so
>> that I don't have to re-install SQL 2000?
>> Willie
>>
>>
>|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
>> about locations.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>> Actually, this got me on the right path, but it was the instls.sql file
>> in the /install directory that creates the log shipping pieces.
>> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
>> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should
>> be in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support
>> for help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables,
>> could anyone out there help me out with the table generation scripts
>> so that I don't have to re-install SQL 2000?
>> Willie
>>
>>
>
I *accidentally* deleted some of the msdb.dbo log shipping tables, could
anyone out there help me out with the table generation scripts so that I
don't have to re-install SQL 2000?
WillieAll the MSDB stuff is in the instmsdb.sql script which I think should be in
the INSTALL directory for your instance. It's unlikely that you understand
log shipping well enough to get everything back to a useable state if only
some of the tables were dropped so your number one option is to restore an
old backup and number to is to ask customer support for help.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
> So...
> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
> anyone out there help me out with the table generation scripts so that I
> don't have to re-install SQL 2000?
> Willie
>|||Actually, this got me on the right path, but it was the instls.sql file in
the /install directory that creates the log shipping pieces.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
> All the MSDB stuff is in the instmsdb.sql script which I think should be
> in the INSTALL directory for your instance. It's unlikely that you
> understand log shipping well enough to get everything back to a useable
> state if only some of the tables were dropped so your number one option is
> to restore an old backup and number to is to ask customer support for
> help.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
>> anyone out there help me out with the table generation scripts so that I
>> don't have to re-install SQL 2000?
>> Willie
>|||Sorry, I just have SQL 2005 on my box. That's why I was a little vague
about locations.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Actually, this got me on the right path, but it was the instls.sql file in
> the /install directory that creates the log shipping pieces.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should be
>> in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support for
>> help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables, could
>> anyone out there help me out with the table generation scripts so that I
>> don't have to re-install SQL 2000?
>> Willie
>>
>|||Once you recover your tables , make sure that you add MSDB and MASTER
databases in your regular backup procedure
Thanks
Hari
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
> about locations.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>> Actually, this got me on the right path, but it was the instls.sql file
>> in the /install directory that creates the log shipping pieces.
>> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
>> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should be
>> in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support for
>> help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables,
>> could anyone out there help me out with the table generation scripts so
>> that I don't have to re-install SQL 2000?
>> Willie
>>
>>
>|||Thank you for the help you have already given me, and now I have another
problem with the log shipping. I have 7 databases that I have setup Log
Shipping on and 6 of them work great. The one with issues is a much larger
database (exponentially larger). On the other 6 I have log shipping done at
longer intervals to spread the load out and because they don't see much
activity. On the main database, it seems to work along fine for a while and
then suddenly it can no longer restore the log files. What I have is the SQL
Server installed on the C drive (33.5 GB free), the data is on the D drive
(38.9 GB free) and the log files are on the F drive (262 GB free). The log
files are generally between 2 and 4 MB and the log file that it choked on
was 2,493 kb, with the last one before it being 2,237 kb. I have tried it
with 15 minute intervals between transaction log backups and an hour between
backups, both ending in the same thing: Everything works fine for a while
and then all of a sudden the restore fails and the database is left in the
loading state where it has been for 26 hours now. Does anybody out there
have any suggestions for me? Is there some limit on how many databases you
can setup log shipping on any one machine? Or perhaps any other suggestions
for where I could like for the cause of this problem? Thanks again for any
help you can give me.
Willie
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23tR%23c5LeHHA.928@.TK2MSFTNGP02.phx.gbl...
> Once you recover your tables , make sure that you add MSDB and MASTER
> databases in your regular backup procedure
> Thanks
> Hari
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:E0C391EC-AD75-48EC-A5B7-29DAF4D13510@.microsoft.com...
>> Sorry, I just have SQL 2005 on my box. That's why I was a little vague
>> about locations.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OrDV8XJeHHA.2188@.TK2MSFTNGP04.phx.gbl...
>> Actually, this got me on the right path, but it was the instls.sql file
>> in the /install directory that creates the log shipping pieces.
>> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
>> news:910467DF-E344-4246-96E0-EF31FF583BEA@.microsoft.com...
>> All the MSDB stuff is in the instmsdb.sql script which I think should
>> be in the INSTALL directory for your instance. It's unlikely that you
>> understand log shipping well enough to get everything back to a useable
>> state if only some of the tables were dropped so your number one option
>> is to restore an old backup and number to is to ask customer support
>> for help.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> "Willie Bodger" <williebnospam@.lap_ink.c_m> wrote in message
>> news:OTOVdZHeHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> So...
>> I *accidentally* deleted some of the msdb.dbo log shipping tables,
>> could anyone out there help me out with the table generation scripts
>> so that I don't have to re-install SQL 2000?
>> Willie
>>
>>
>
Subscribe to:
Posts (Atom)