Log shipping reconciliation

I have a database reconciliation script that runs between two databases and
reconciles object counts and table counts etc between the two.
Is there a way to run such a script across a primary and secondary in log
shipping configuration. As the secondary is in RESTORING state it's not
accessible. Therefore is it possible to do something like bring it briefly up
to standby state, run the reconciliation and then take it back to restoring
again? Would this work and are there any gotchas?
Cheers.
Here is an example of how to do it:
there are two databases logshippingtestbak and logshippingtest.
I backup loshippingtest and restore this backup into the database
logshippingtestback with no recovery
backup log logshippingtest to disk='c:\logshippingtestlog.bak'
GO
--restoring my first log
restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
norecovery
GO
select * from logshippingtestbak.dbo.sysobjects
Server: Msg 927, Level 14, State 2, Line 1
Database 'logshippingtestbak' cannot be opened. It is in the middle of a
restore.
--i backup another log
backup log logshippingtest to disk='c:\logshippingtestlog.bak'
--i restore it with the standby option
restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
standby ='c:\standby.bak'
--i read this database
select * from logshippingtestbak.dbo.sysobjects
--I restore the same log this time with norecovery
restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
norecovery
--I verify this database is inaccessible again.
select * from logshippingtestbak.dbo.sysobjects
Server: Msg 927, Level 14, State 2, Line 1
Database 'logshippingtestbak' cannot be opened. It is in the middle of a
restore.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kev" <Kev@.discussions.microsoft.com> wrote in message
news:5722A586-57E3-41AA-B6DF-021F50F7F2CB@.microsoft.com...
>I have a database reconciliation script that runs between two databases and
> reconciles object counts and table counts etc between the two.
> Is there a way to run such a script across a primary and secondary in log
> shipping configuration. As the secondary is in RESTORING state it's not
> accessible. Therefore is it possible to do something like bring it briefly
> up
> to standby state, run the reconciliation and then take it back to
> restoring
> again? Would this work and are there any gotchas?
> Cheers.
|||Is it possible to do something like:
restore database [logshippingtestbak] with
standby=''c:\logshippingtestlog.bak'
<do the reconciliation>
restore database [logshippingtestbak] with norecovery
or do you always need to restore the last transaction log to switch modes.
Cheers
Kev.
"Hilary Cotter" wrote:

> Here is an example of how to do it:
> there are two databases logshippingtestbak and logshippingtest.
> I backup loshippingtest and restore this backup into the database
> logshippingtestback with no recovery
> backup log logshippingtest to disk='c:\logshippingtestlog.bak'
> GO
> --restoring my first log
> restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
> norecovery
> GO
> select * from logshippingtestbak.dbo.sysobjects
> Server: Msg 927, Level 14, State 2, Line 1
> Database 'logshippingtestbak' cannot be opened. It is in the middle of a
> restore.
> --i backup another log
> backup log logshippingtest to disk='c:\logshippingtestlog.bak'
> --i restore it with the standby option
> restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
> standby ='c:\standby.bak'
> --i read this database
> select * from logshippingtestbak.dbo.sysobjects
> --I restore the same log this time with norecovery
> restore log logshippingtestbak from disk='c:\logshippingtestlog.bak' with
> norecovery
> --I verify this database is inaccessible again.
> select * from logshippingtestbak.dbo.sysobjects
> Server: Msg 927, Level 14, State 2, Line 1
> Database 'logshippingtestbak' cannot be opened. It is in the middle of a
> restore.
>
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kev" <Kev@.discussions.microsoft.com> wrote in message
> news:5722A586-57E3-41AA-B6DF-021F50F7F2CB@.microsoft.com...
>
>
|||It doesn't have to be the last transaction log, but it would have to be the
next one in the chain. Consider if you dump each hour, you might not have
another log for 1 hour or so.
Also you don't need to put it back into norecovery, the next log applied
will. I prefer to put it back into norecovery so my users can't access it
and then interfer with the next tlog restore.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kev" <Kev@.discussions.microsoft.com> wrote in message
news:629337E7-A409-49C3-9C99-7510FC802069@.microsoft.com...[vbcol=seagreen]
> Is it possible to do something like:
> restore database [logshippingtestbak] with
> standby=''c:\logshippingtestlog.bak'
> <do the reconciliation>
> restore database [logshippingtestbak] with norecovery
> or do you always need to restore the last transaction log to switch modes.
> Cheers
> Kev.
>
> "Hilary Cotter" wrote:
|||Would my bit of sql work?
"Hilary Cotter" wrote:

> It doesn't have to be the last transaction log, but it would have to be the
> next one in the chain. Consider if you dump each hour, you might not have
> another log for 1 hour or so.
> Also you don't need to put it back into norecovery, the next log applied
> will. I prefer to put it back into norecovery so my users can't access it
> and then interfer with the next tlog restore.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kev" <Kev@.discussions.microsoft.com> wrote in message
> news:629337E7-A409-49C3-9C99-7510FC802069@.microsoft.com...
>
>
|||No, you would have to restore the log, like this
restore log [logshippingtestbak] from disk='c:\mylog' with
standby=''c:\logshippingtestlog.bak'
<do the reconciliation>
restore log [logshippingtestbak] from disk='c:\mylog1.bak' with norecovery
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kev" <Kev@.discussions.microsoft.com> wrote in message
news:10217BE0-4F01-44D0-B7F6-6E6661B385F9@.microsoft.com...[vbcol=seagreen]
> Would my bit of sql work?
> "Hilary Cotter" wrote:
|||Are there any disadvantages to keeping it in standby mode all the time?
Presumably you can still restore in the same way - you just have to be
careful that nobody tries to access it at the wrong time.
Kev.
"Hilary Cotter" wrote:

> No, you would have to restore the log, like this
> restore log [logshippingtestbak] from disk='c:\mylog' with
> standby=''c:\logshippingtestlog.bak'
> <do the reconciliation>
> restore log [logshippingtestbak] from disk='c:\mylog1.bak' with norecovery
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kev" <Kev@.discussions.microsoft.com> wrote in message
> news:10217BE0-4F01-44D0-B7F6-6E6661B385F9@.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?
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...
>

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
>>
>>
>

Log shipping impact

Can any one tell me like if the table is not normalized and if there is no
relationtionship in the database then what would be the impact on log
shipping like it will generate extra log. Can any one let me know the
disadvantages.
Thanks
John
Log shipping just ships the data within the transaction log from one server
to the next. It does not care about your database setup or configuration.
You are looking for disadvantages to log shipping? None, really.
You may find this information helpful:
314515 INF: Frequently Asked Questions - SQL Server 2000 - Log Shipping
http://support.microsoft.com/?id=314515
323135 INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping (White
Paper)
http://support.microsoft.com/?id=323135
325220 Support WebCast: Microsoft SQL Server 2000 Log Shipping
http://support.microsoft.com/?id=325220
821786 Support WebCast: Microsoft SQL Server 2000: Using Log Shipping
http://support.microsoft.com/?id=821786
321247 HOW TO: Configure Security for Log Shipping
http://support.microsoft.com/?id=321247
329133 INF: Troubleshooting SQL Server 2000 Log Shipping "Out of Sync"
Errors
http://support.microsoft.com/?id=329133
Keith
"John" <naissani@.hotmail.com> wrote in message
news:%23YTkqg9BFHA.4004@.tk2msftngp13.phx.gbl...
> Can any one tell me like if the table is not normalized and if there is no
> relationtionship in the database then what would be the impact on log
> shipping like it will generate extra log. Can any one let me know the
> disadvantages.
> Thanks
> John
>

log shipping and truncate table

As a noob, I'm wondering, how does sql server 2005 react to a truncate table
on a table within a database which is subject to log shipping?
Thanks.
CRCR wrote:
> As a noob, I'm wondering, how does sql server 2005 react to a truncate tab
le
> on a table within a database which is subject to log shipping?
> Thanks.
> CR
>
http://support.microsoft.com/kb/272093
Tracy McKibben
MCDBA
http://www.realsqlguy.com

log shipping and truncate table

As a noob, I'm wondering, how does sql server 2005 react to a truncate table
on a table within a database which is subject to log shipping?
Thanks.
CR
CR wrote:
> As a noob, I'm wondering, how does sql server 2005 react to a truncate table
> on a table within a database which is subject to log shipping?
> Thanks.
> CR
>
http://support.microsoft.com/kb/272093
Tracy McKibben
MCDBA
http://www.realsqlguy.com

log shipping and truncate table

As a noob, I'm wondering, how does sql server 2005 react to a truncate table
on a table within a database which is subject to log shipping?
Thanks.
CRCR wrote:
> As a noob, I'm wondering, how does sql server 2005 react to a truncate table
> on a table within a database which is subject to log shipping?
> Thanks.
> CR
>
http://support.microsoft.com/kb/272093
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Log Shipping - Move DB Changes?

I am in a 2 Database shop (DB2 and SQL Server) in which one of our
larger clients use Log Shipping.

We have need to tune a table on the primary server and ADDED a simple
index to a table.

Will that index be replicated down to the secondary server via log
shipping. Or do I need to stop log shipping and apply the index to the
secondary server?

Thanks in advance for the help.

Sincerely,
MikeMike:

Yes. Log shipping will move the indexes over as well.

-Dave

madzambonis@.yahoo.com wrote:

Quote:

Originally Posted by

I am in a 2 Database shop (DB2 and SQL Server) in which one of our
larger clients use Log Shipping.
>
We have need to tune a table on the primary server and ADDED a simple
index to a table.
>
Will that index be replicated down to the secondary server via log
shipping. Or do I need to stop log shipping and apply the index to the
secondary server?
>
Thanks in advance for the help.
>
Sincerely,
Mike